Sprint planning is the meeting where a backlog of ideas becomes a concrete, achievable commitment for the next one to two weeks. Done well, it's the single biggest lever for whether a project stays on track. Done badly, it's where over-promising quietly begins.
What goes into the room
Three things need to be ready before planning starts: a prioritized backlog (what matters most right now), a rough estimate of team capacity for the sprint (accounting for holidays, other commitments, and realistic focus time — not just headcount times hours), and enough detail on the top backlog items that the team can actually reason about them.
The actual process
- Review priorities — confirm the top of the backlog still reflects what matters most.
- Break down the work — large items get split into pieces small enough to finish within the sprint.
- Estimate — the team sizes each piece, usually in relative terms (story points) rather than exact hours, since relative sizing is more honest about uncertainty.
- Commit — the team pulls in as much as realistically fits their capacity, not as much as looks impressive on a spreadsheet.
Why "realistic" beats "ambitious"
It's tempting to pack a sprint tight to look productive. It backfires: unfinished work rolls over, estimates for future sprints become unreliable, and trust erodes when "done by Friday" quietly becomes "done whenever." A team that consistently finishes what it commits to is more valuable than one that consistently overcommits and slips.
A sprint plan you can trust is worth more than a sprint plan that looks impressive.
What this means if you're the client
You don't need to sit through every planning meeting, but you should see — and agree with — the priority order before the sprint starts. If something urgent comes up mid-sprint, say so immediately rather than waiting for the review; a good team will tell you honestly what trading it in costs, instead of just quietly falling behind.
A quick sanity check
If your project's sprints routinely finish everything with time to spare, capacity estimates are too conservative — you're leaving progress on the table. If sprints routinely miss half their commitments, something in the estimation or scoping process needs fixing before the next one. Either extreme is worth raising with your team.