Professional Scrum Master I (PSM I)Scrum FrameworkHard
A new Scrum Master is coaching a Scrum Team that often struggles to deliver a 'Done' Increment by the end of the Sprint. The Developers frequently discover critical design flaws or technical dependencies late in the Sprint. Which Scrum Event, if conducted effectively, would best help the team proactively identify and address these issues earlier?
- ASprint Planning
- BProduct Backlog Refinement
- CSprint Retrospective
- DDaily Scrum
Show answer & explanationAnswer & explanation
Correct answer: B. Product Backlog Refinement
Product Backlog Refinement is the ongoing process of adding detail, estimates, and order to Product Backlog items. This activity helps the Developers understand items better, identify dependencies, and uncover technical challenges *before* Sprint Planning, thus preventing late-Sprint surprises.
Why the other options are wrong
- A. Sprint Planning commits to items; refinement should ideally happen before to ensure items are ready for selection.
- C. The Sprint Retrospective looks back at the past Sprint; it doesn't proactively refine future work.
- D. The Daily Scrum is for daily progress inspection, not for deep refinement of future items.
Product Backlog Refinement for Clarity
Product Backlog Refinement is the act of breaking down and further defining Product Backlog items into smaller, more precise items, often identifying dependencies and technical challenges proactively.
- Ongoing activity, not an event.
- Adds detail, estimates, order.
- Helps prepare items for future Sprints.
Memory trick: To avoid late-stage surprises, refine the backlog early and often, like checking your map before the journey.