What this resource covers
Scrum organizes product development into time-boxed sprints with defined accountabilities and events. Sprint planning selects a realistic objective and work based on priority, readiness, dependencies, and team capacity.
- Maintain an ordered product backlog owned through product decisions
- Refine upcoming items before planning without attempting to detail the entire future
- Review actual capacity, leave, support duties, and unfinished work
- Agree a sprint goal that explains the intended outcome
- Select work the team believes can support the goal
- Review completed work and adapt the backlog
- Use retrospective actions to improve how the team works
Information to prepare
Bring an ordered and refined backlog, sprint goal options, team capacity, dependencies, acceptance criteria, quality definition, recent delivery evidence, and known operational interruptions.
- Product goal and ordered backlog
- Refined items with acceptance criteria
- Team capacity and recent delivery evidence
- Dependencies, risks, and Definition of Done
- Upcoming review and release commitments
Expected planning outputs
The planning outcome should be a clear sprint goal, selected backlog, delivery forecast, task or collaboration plan, dependency actions, and shared understanding of completion.
- Sprint goal
- Selected sprint backlog
- Shared understanding of acceptance and dependencies
- Reviewable increment
- Retrospective improvement actions
Practical example
How it can be applied
For an invoice increment, the sprint goal may be to let billing users create and review customer invoices from completed bookings. Selected items include invoice rules, permissions, interface, validation, audit entries, and tests that together support the outcome.
Common mistakes to avoid
- Filling capacity with unrelated items and no sprint goal
- Treating estimates as promises imposed on the team
- Pulling unclear work into the sprint
- Changing sprint work repeatedly without protecting the goal
- Counting partially complete work as done
FAQ
Common questions
Who decides what enters a sprint?
The product owner orders value and the developers forecast what they can complete while collaborating on the sprint goal.
Should every backlog item have task-level detail before planning?
No. Near-term items need sufficient clarity. The team can create implementation tasks during planning as needed.
What happens to unfinished work?
It is not counted as done. Return it for review, reordering, splitting, or future selection based on the product decision.