Professional Scrum Master I (PSM I)Scrum FrameworkHard
During a Sprint Retrospective, the Scrum Team identifies that their Sprint Planning sessions are consistently ineffective, leading to unclear Sprint Goals and frequently missed commitments. What is the most impactful action the Scrum Master should encourage the team to take?
- ASuggest that the Developers commit to fewer Product Backlog Items to ensure completion.
- BIncrease the timebox for Sprint Planning to allow for more detailed discussions.
- CFocus on improving the clarity and readiness of Product Backlog Items before Sprint Planning.
- DAsk the Product Owner to provide a more detailed Sprint Goal before the event.
Show answer & explanationAnswer & explanation
Correct answer: C. Focus on improving the clarity and readiness of Product Backlog Items before Sprint Planning.
Ineffective Sprint Planning often stems from an unprepared Product Backlog. If PBIs are not clear, well-understood, and appropriately sized (ready), the team will struggle to forecast work accurately and create a meaningful Sprint Goal. Improving Product Backlog Refinement (an ongoing activity, not an event) is key to better Sprint Planning.
Why the other options are wrong
- A. Committing to fewer items is a symptom treatment, not a cure for the underlying cause of unclear goals and missed commitments due to poor PBI readiness.
- B. While more time might seem helpful, without ready PBIs, it just means more time spent on unclear items.
- D. The Sprint Goal is collaboratively created by the entire Scrum Team during Sprint Planning, not dictated by the Product Owner beforehand.
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 details, estimates, and order to items.
- Not a formal Scrum Event, but an ongoing activity.
- Done by the Developers, usually with the Product Owner.
- Ensures Product Backlog Items are 'ready' for future Sprints.
- Typically consumes no more than 10% of the Developers' time.
Memory trick: Good planning needs good ingredients; refine the backlog first.