In my daily life as a Scrum Master, I witness many crazy situations. I want to share my discoveries via this comic series featuring Koos Coach, the silly Scrum Master struggling to understand and master Scrum.
Failing the Sprint
Sometimes or many times teams "the sprint fails". What does it mean to fail the Sprint? Is all failing to be considered a bad thing?
What does “failing the Sprint” mean to you?
- Not finishing all PBI’s?
- Having missed opportunities for collaboration?
- Delivering software that is not valued by the customer?
The team works on turning requirements into working software. The software development work is complex. During the Sprint, new work can be discovered and in some cases, they require decisions to be taken by the Product Owner. The Product Owner "owns the product" and should have the full mandate and authority to take product decisions.
Things to think about:
- Which decisions can be taken without consulting the Product Owner?
- What does it tell you if your Product Owner often needs a stakeholder to approve a decision?
- Who is "the impediement" in this story?