Key Takeaways
- A sprint planning checklist converts recurring, avoidable sprint failures, like a vague goal or a hidden dependency, into a few seconds of verification before you commit.
- Before planning, confirm the backlog is ordered and refined with acceptance criteria, candidate stories are estimated, and PTO, holidays, and support duty are recorded.
- During planning, confirm one stateable sprint goal, capacity drawn from real availability rather than last sprint’s velocity, scope that fits with room to spare, and an owner plus a rough approach for each item.
- Before committing, the team should say out loud that they believe the plan, and the sprint backlog should be the smallest set of work that achieves the goal.
- The two most-skipped checks, capacity and dependencies, cause the most damage; Sprint Planning, Capacity & Resource Planning for Jira does the capacity math automatically so the check becomes a quick confirmation.
Even experienced teams miss sprints for avoidable reasons: a vague goal, an unchecked calendar, a hidden dependency. A short sprint planning checklist turns those recurring failures into a few seconds of verification. Run through this before you commit each sprint. It pairs with our sprint planning meeting agenda and the full sprint planning guide.
Before planning
- The backlog is ordered and the top items are refined with clear acceptance criteria.
- Candidate stories have estimates the team agrees on.
- Known PTO, holidays, and support duty for the sprint are recorded.
During planning
- There is one clear sprint goal everyone can state.
- Capacity is calculated from real availability, not last sprint’s velocity.
- Committed scope fits inside that capacity with a little room to spare.
- Each committed item has a rough “how” and an owner.
- Dependencies and blockers are identified and have a plan.
Before you commit
- The team has said out loud that they believe the plan.
- The sprint backlog is the smallest set of work that achieves the goal.
The two items teams skip most are the capacity check and the dependency check — and they’re the two that cause the most damage. Sprint Planning, Capacity & Resource Planning for Jira handles the capacity math automatically, so the checklist becomes a quick confirmation rather than a manual calculation. For the failure patterns this checklist prevents, see common sprint planning mistakes.
