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 Developers estimated as 90% done. The Developers, feeling the need to meet the plan, figured that a velocity of 17 was within their reach.
A good way to continue is:
(choose the best answer)
A. The opportunity to inspect and adapt is lost. Opaqueness has replaced transparency. Predictability has dropped below zero. The produced software is not usable. As the rules of Scrum have not been respected. It is the Scrum Master’s duty to assess whether repair is possible. or a restart with a more reliable team. If not, the Scrum Master should cancel the project.
B. The Developers make sure that all of the selected scope per Sprint is as “Done” as possible. The undone work is estimated and added to the Sprint Backlog of the next Sprint, so it doesn’t mess up the Product Backlog.
C. Replace the Scrum Master with a project manager, who takes control of the project.
D. The Developers should remind Marian to find funding for enough Release Sprints in which the remaining work can be done.
E. The Developers inform Marian that the progress she has perceived to date is not correct. The Increment is not releasable. They give Marian their estimate of the effort it would take to get the past work “Done,” and suggest doing that work first before proceeding with new features. In the end, it is Marian’s call to continue the project or to cancel.
F. Add enough people to the Scrum Team for the deadline to be made.