Professional Scrum Master I (PSM I)Scrum FrameworkMedium
A Scrum Master observes that during Sprint Planning, the Developers are reluctant to commit to a Sprint Goal because they feel they lack sufficient information about the Product Backlog Items. They argue that the items are too vague and not well-understood. Which characteristic of a healthy Product Backlog is missing in this scenario?
- AEstimated
- BOrdered
- CRefined
- DTransparent
Show answer & explanationAnswer & explanation
Correct answer: C. Refined
A healthy Product Backlog has items that are understood and detailed enough for the Developers to work on. This is achieved through ongoing Product Backlog refinement, which involves adding detail, estimates, and order to items, making them 'ready' for a Sprint.
Why the other options are wrong
- A. While estimation is part of refinement, the core issue is the lack of *understanding* and *detail*, which is addressed by refinement, not just having an estimate.
- B. Ordering implies priority, but even ordered items can be vague if not properly refined.
- D. Transparency means the Product Backlog is visible and understood by all, but 'vague' and 'not well-understood' points more specifically to a lack of refinement rather than just visibility.
Product Backlog Attributes (DEEP)
A mnemonic for characteristics of a healthy Product Backlog: Detailed appropriately, Estimated, Emergent, Prioritized (Ordered).
- Detailed Appropriately: Higher priority items are more detailed.
- Estimated: Items have a relative size estimate.
- Emergent: Constantly evolving and changing.
- Prioritized (Ordered): Items are ordered by value, risk, need.
Memory trick: DEEP is the way to keep.