Handling Velocity and Transparency in Scrum

In Scrum, maintaining transparency and accurate tracking of progress is essential. This scenario involves Marian, a Product Owner, facing challenges with velocity and transparency. Understanding the correct approach to address these challenges is crucial for effective Scrum implementation.

Exam 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 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.

Correct Answer

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.

Explanation

Why E is Correct

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:

Transparency is a core principle in Scrum. The Developers must be honest about the state of the Increment. By informing Marian that the progress is not as perceived and providing a realistic estimate of the work required to make it “Done,” they maintain transparency. This approach allows Marian to make an informed decision about the project’s future.

Why A, B, C, D, and F are Incorrect

A. The opportunity to inspect and adapt is lost…: This response is overly drastic. While there are issues, the project doesn’t necessarily need to be canceled. The focus should be on restoring transparency and adapting based on current realities.

B. The Developers make sure that all of the selected scope per Sprint is as “Done” as possible…: Carrying undone work forward without addressing the root cause of the problem perpetuates the lack of transparency and can lead to further issues.

C. Replace the Scrum Master with a project manager…: Scrum Masters play a critical role in facilitating Scrum processes. Replacing them with a project manager who “takes control” is contrary to Scrum principles of self-management and transparency.

D. The Developers should remind Marian to find funding for enough Release Sprints…: This option doesn’t address the immediate need for transparency and the existing issues with the Increment.

F. Add enough people to the Scrum Team for the deadline to be made: Simply adding people to the team without addressing the process and transparency issues will not solve the underlying problems and can lead to further inefficiencies.

Key Points

• Transparency: Maintaining transparency is crucial in Scrum to ensure realistic planning and decision-making.
• Inspect and Adapt: The Scrum Team should inspect the current situation and adapt their approach to ensure the Increment is truly “Done.”

Responsibilities in Scrum

• Product Owner: Ensures the Product Backlog is ordered and refined to maximize value and align with the team’s capacity. Makes informed decisions based on transparent information.
• Scrum Master: Facilitates Scrum events, removes impediments, and helps teams adhere to Scrum principles.
• Developers: Plan, manage, and execute all tasks necessary to deliver a potentially shippable Increment, ensuring quality and adherence to the Definition of Done.

Relevance to the PSM I Exam

Understanding the importance of transparency and realistic planning in Scrum is crucial for the PSM I exam. This knowledge emphasizes the need for honest communication and adherence to Scrum principles.

Conclusion

In situations where velocity and transparency issues arise, it is essential for the Developers to maintain honesty and transparency with the Product Owner. By providing accurate information and realistic estimates, the Product Owner can make informed decisions about the project’s future.

For comprehensive preparation and practice exams, check out PSM I Exam Prep to enhance your understanding and application of Scrum principles.