The sprint planning checklist
A sprint planning meeting is only as good as the preparation that precedes it. Teams that arrive at planning with unclear backlogs, missing estimates, and undefined capacity routinely produce sprint commitments they cannot keep. This checklist covers everything you need to do before, during, and after sprint planning to maximise the quality of every sprint.
Before sprint planning: preparation checklist
Most sprint planning failures begin days before the meeting. These are the inputs that must be in place before the meeting starts.
Backlog readiness
- The Product Backlog is ordered with the highest-priority items at the top.
- The top 1.5× sprint capacity worth of stories have accepted acceptance criteria.
- All candidate stories have story point estimates from a recent planning poker session.
- No candidate story has an unresolved dependency that would block it from starting on day one.
- The Product Owner has reviewed and approved the top stories within the last sprint.
Team capacity
- Every team member's availability for the sprint is confirmed (vacation, conferences, on-call rotation, part-time allocations).
- Sprint capacity has been calculated: available days × focus factor, expressed in story points using recent velocity.
- A capacity buffer has been reserved (plan for 70–80% of theoretical maximum, not 100%).
Sprint Goal preparation
- The Product Owner has a draft Sprint Goal ready to propose — not final, but a starting point.
- The Scrum Master has reviewed the proposed stories and confirmed they support the draft goal.
- Any stories from the previous sprint that were not completed have been assessed: re-added to the backlog, re-estimated if scope changed, or removed if no longer relevant.
During sprint planning: meeting checklist
Sprint planning has a recommended timebox of up to 8 hours for a 4-week sprint, 4 hours for a 2-week sprint. The meeting follows a consistent structure — use this checklist to stay on track.
Sprint Goal agreement
- The Product Owner proposes the Sprint Goal with context: why now, what value it delivers.
- The team asks clarifying questions and negotiates scope if needed.
- The Sprint Goal is written down and agreed by the full team before item selection begins.
Backlog item selection
- The team selects stories from the top of the backlog that support the Sprint Goal.
- Selected stories are checked against sprint capacity. Total story points must not exceed planned capacity.
- The Product Owner confirms that the selected stories represent sufficient value to justify the sprint.
Estimation (if needed)
- Any unestimated stories or stories with significantly changed scope are estimated using planning poker.
- Votes are revealed simultaneously. Outliers explain their reasoning before re-voting.
- Stories that cannot reach consensus in 2–3 rounds are deferred for refinement.
Task breakdown
- The team identifies specific tasks for the first 2–3 days of the sprint.
- Dependencies between tasks are flagged and initial assignments are agreed.
- Potential blockers or risks for the sprint are identified and owners assigned.
After sprint planning: close checklist
The meeting close takes 5–10 minutes but produces critical artefacts and commitments.
- The Sprint Goal is recorded in the project tracking tool and visible to all stakeholders.
- All selected stories are moved to the sprint in the tracking tool.
- Story point values are confirmed and recorded for all selected items.
- The sprint start date, end date, and sprint review/retrospective dates are confirmed.
- Any items that were discussed but not selected are returned to the backlog with any updated notes.
- Action items from the planning session (refinement tasks, dependency resolutions) are recorded with owners.
- The Sprint Goal is shared with relevant stakeholders before the sprint begins.
Sprint planning checklist FAQ
How far in advance should I prepare for sprint planning?
Backlog refinement should happen continuously throughout the previous sprint. The specific preparation for sprint planning (capacity calculation, pre-planning sync with the Product Owner) should happen the day before.
What if a story fails the Definition of Ready during planning?
Return it to the backlog with a note about what is missing. Do not estimate or select stories that are not ready. The short-term pain of removing a story from the sprint is much less than the long-term pain of committing to work you cannot define.
Does every team need the same checklist?
No. This checklist is a starting point. Adapt it to your team's context. A team with a highly stable backlog may skip the capacity buffer reminder; a team new to Scrum may need more steps around Sprint Goal definition.
How do we use this checklist without adding meeting overhead?
Use it as a preparation template, not a meeting agenda item. The Scrum Master reviews the checklist before the meeting to ensure inputs are in place. If any items are missing, address them before starting — not during the meeting.
Make your sprint planning efficient with free online planning poker