Key Takeaways
- A sprint planning meeting fails most often because it has no agenda; a fixed sequence and a timebox turn it from story-dragging into an actual plan.
- Run the meeting in five steps: confirm the sprint goal, confirm capacity, walk the top of the backlog, plan the approach for each item, then commit out loud.
- Refine the backlog before the meeting in about 15 minutes async, so the session is spent planning instead of refining, with candidate items already ordered and roughly estimated.
- Set capacity by subtracting PTO, holidays, meetings, and support duty from nominal availability, then plan against that number rather than last sprint’s velocity.
- Keep a two-week sprint’s planning session to about an hour; routine overruns usually signal an unrefined backlog or a missing capacity number, which Sprint Planning, Capacity & Resource Planning for Jira surfaces by putting capacity and scope on one screen.
A sprint planning meeting goes sideways for one reason more than any other: there’s no agenda. People arrive, someone starts dragging stories onto the board, and an hour later the team has a list but no plan. A clear sprint planning meeting agenda fixes that by giving the session a shape, a sequence, and a timebox. Here’s a format that works for most teams, and how to run each part. It’s the operational companion to our complete guide to sprint planning.
Before the meeting (15 minutes, async)
Planning is faster when the backlog is already refined. The product owner should have the top items ordered, and the team should have rough estimates on the candidates. If you walk in cold, you’ll spend the meeting refining instead of planning.
The agenda
- 1. Confirm the sprint goal (5 min). Start with why this sprint matters. Everything that follows is judged against it. If you can’t state a goal, that’s the first problem to solve — see how to write a sprint goal.
- 2. Confirm capacity (5 min). Subtract PTO, holidays, meetings, and support duty from the team’s nominal availability. Plan against that number, not last sprint’s velocity.
- 3. Walk the top of the backlog (15–20 min). Take the highest-priority items that serve the goal. Confirm acceptance criteria and estimates as you go.
- 4. Plan the “how” (15–20 min). For each committed item, talk briefly about approach, dependencies, and who’s involved. This is the step teams skip — and the step that prevents mid-sprint surprises.
- 5. Commit (5 min). Read back the goal and the sprint backlog. Ask the team directly: do we believe this? If not, cut scope now.
Keep it timeboxed
For a two-week sprint, the whole session should fit in about an hour. If it routinely runs long, the cause is almost always unrefined backlog or a missing capacity number — fix those upstream rather than extending the meeting. Sprint Planning, Capacity & Resource Planning for Jira puts capacity and scope on one screen so steps 2–5 move quickly. Pair this agenda with our sprint planning checklist so nothing gets missed.
