PSM-I · Question #148
Marian is the Product Owner envisioning a project for a new release of her product. She made a projection of a release date based upon a sustained velocity of 17 completed units of work per Sprint…
The correct answer is A. The Development Team makes sure that all of the selected scope per Sprint is as "Done" as. The core issue here is that work estimated as '90% done' is not Done - in Scrum, partially completed work has no value and creates hidden technical debt. The team's velocity of 13 with only 90% completion means they are not meeting the Definition of Done, which undermines…
Question
Marian is the Product Owner envisioning a project for a new release of her product. She made a projection of a release date based upon a sustained velocity of 17 completed units of work per Sprint. Over the first 3 Sprints, the average velocity was 13 for work that the Development Team estimated as 90% done. The Development Teams, feeling the need to meet the plan, figured that a velocity of 17 was within their reach. A good way to continue is:
Options
- AThe Development Team makes sure that all of the selected scope per Sprint is as "Done" as
- BAdd enough people to the Development Team for the deadline to be made.
- CThe opportunity to inspect and adapt is lost. Opaqueness has replaced transparency.
- DThe Development Team should remind Marian to find funding for enough Release Sprints in
How the community answered
(40 responses)- A73% (29)
- B3% (1)
- C8% (3)
- D18% (7)
Explanation
The core issue here is that work estimated as '90% done' is not Done - in Scrum, partially completed work has no value and creates hidden technical debt. The team's velocity of 13 with only 90% completion means they are not meeting the Definition of Done, which undermines transparency and the ability to inspect and adapt. The correct path forward is option A: the Development Team must ensure that every item selected for a Sprint is fully 'Done' by the end of the Sprint, meeting the agreed Definition of Done. This restores an honest, transparent velocity baseline that Marian can actually use for planning. Option B (adding people) violates Brooks' Law and does not address the root problem. Option C is a statement describing the current problem, not an action. Option D misunderstands how Scrum works - 'Release Sprints' are an anti-pattern in Scrum.
Topics
Community Discussion
No community discussion yet for this question.