Professional Scrum Master I (PSM I)Scrum FrameworkHard
A Scrum Master is coaching a new Scrum Team. During the Sprint Retrospective, the Developers identify that they consistently struggle to understand the scope and technical requirements of Product Backlog Items (PBIs) during Sprint Planning, leading to frequent re-work. What artifact's state is primarily responsible for this issue, and how can it be improved?
- AThe Product Backlog; by engaging in more frequent and effective Product Backlog refinement.
- BThe Increment; by ensuring the Definition of Done is more comprehensive.
- CThe Sprint Backlog; by breaking down tasks into smaller, more manageable units during Sprint Planning.
- DThe Sprint Goal; by making it more specific and measurable.
Show answer & explanationAnswer & explanation
Correct answer: A. The Product Backlog; by engaging in more frequent and effective Product Backlog refinement.
The Product Backlog is an ordered list of everything that might be needed in the product. If Developers struggle with understanding PBIs, it indicates insufficient Product Backlog refinement, which is the act of breaking down and further defining Product Backlog items into smaller, more precise items.
Why the other options are wrong
- B. The Definition of Done ensures quality and completeness of the Increment, but it doesn't directly address the clarity of PBIs *before* development begins.
- C. While breaking down tasks in the Sprint Backlog is good practice, it's a reactive measure during Sprint Planning. The issue stems from the clarity of the PBIs *before* they even enter the Sprint Backlog.
- D. A specific Sprint Goal is important for focus, but it doesn't resolve issues with the clarity of individual Product Backlog Items themselves.
Product Backlog Refinement
Product Backlog refinement is the act of breaking down and further defining Product Backlog Items into smaller, more precise items. It is an ongoing activity to add detail, estimates, and order to items in the Product Backlog.
- Ongoing activity, not a formal event.
- Typically consumes no more than 10% of Developers' time.
- Ensures items are ready for future Sprints.
Memory trick: Refine the Backlog, clarify the path.