Professional Scrum Master I (PSM I)Scrum FrameworkMedium
A new Scrum Master observes that during Sprint Planning, the Developers are consistently reluctant to commit to a Sprint Goal because they feel there are too many unknowns and dependencies. The Product Backlog Items are generally described at a high level. What activity, if performed more diligently, would most likely help alleviate this issue?
- AProduct Backlog refinement
- BDaily Scrum
- CRelease Planning
- DSprint Retrospective
Show answer & explanationAnswer & explanation
Correct answer: A. Product Backlog refinement
Product Backlog refinement is the act of breaking down and further defining Product Backlog Items into smaller, more precise items. It helps add detail, estimates, and order, reducing unknowns and dependencies, making it easier for Developers to commit during Sprint Planning.
Why the other options are wrong
- B. The Daily Scrum is for Developers to plan their day, not to refine future work.
- C. Release Planning is not a formal Scrum event and focuses on release strategy, not the detailed refinement of individual PBIs.
- D. The Sprint Retrospective focuses on process improvement, not specifically on refining Product Backlog Items.
Product Backlog Refinement
Product Backlog refinement is the ongoing process of adding detail, estimates, and order to Product Backlog Items.
- An ongoing activity, not an event.
- Typically consumes no more than 10% of the Developers' time.
- Ensures Product Backlog Items are 'ready' for Sprint Planning.
Memory trick: Refining for readiness.