Direct answer
Run Sprint Planning around value, a clear Sprint Goal, selected Product Backlog items, and an adaptable plan created by the Scrum Team.
What to know
- Sprint Planning addresses why the Sprint is valuable, what can be done, and how the work will be completed.
- The Sprint Goal provides a coherent objective.
- Developers forecast work using capacity, past performance, and the Definition of Done.
- The plan can evolve as more is learned.
How to apply it
Enter planning with an ordered, refined backlog and a clear product direction. Leave with a shared goal and a realistic Sprint Backlog, not a fixed task contract.
Worked example
When capacity falls mid-Sprint, Developers collaborate with the Product Owner about scope while protecting the Sprint Goal and quality expectations.
Common mistakes
- Treating velocity as a commitment.
- Allowing stakeholders to assign tasks during planning.
- Selecting work without a Sprint Goal.
Exam and practice connection
When a scenario changes capacity or discoveries emerge, preserve transparency and collaborate rather than hiding variance or lowering quality.