Professional Scrum Master I (PSM I)People & TeamsMedium
During a Sprint Retrospective, the Scrum Team identifies a recurring issue where Product Backlog Items (PBIs) are frequently misunderstood by the Developers, leading to re-work. The Scrum Master facilitates a discussion. Which of the following actions is the MOST appropriate for the Scrum Master to guide the team towards to address this issue?
- AAdvise the team to allocate specific time in the Sprint for PBI clarification and rework.
- BSuggest the Product Owner spend more time detailing PBIs before Sprint Planning.
- CEncourage the Developers to collaborate more frequently with the Product Owner for clarification during the Sprint.
- DRecommend implementing a stricter definition of "ready" for PBIs before they enter the Sprint.
Show answer & explanationAnswer & explanation
Correct answer: D. Recommend implementing a stricter definition of "ready" for PBIs before they enter the Sprint.
Implementing a stricter Definition of Ready ensures that PBIs are sufficiently clear and understood by the Developers before they are committed to a Sprint, directly preventing the identified issue of misunderstanding and rework. This proactively addresses the root cause.
Why the other options are wrong
- A. Allocating time for rework is a reactive solution that accepts the problem rather than preventing it. The aim should be to reduce rework, not plan for it.
- B. While more detail might help, a stricter Definition of Ready is a more structured and team-agreed approach to ensure understanding, rather than just shifting responsibility to the Product Owner.
- C. Frequent clarification during the Sprint is a reactive measure; it doesn't prevent the initial misunderstanding and can disrupt flow. The goal is to prevent the issue from occurring.
Definition of Ready
A shared understanding among the Scrum Team that defines the criteria a Product Backlog Item must meet to be considered ready for selection into a Sprint.
- Ensures clarity and understanding of PBIs before Sprint Planning.
- Helps prevent misunderstandings and rework during the Sprint.
- Agreed upon by the entire Scrum Team, not imposed by one role.
Memory trick: Ready means clear, clear means no tears.