Sprint Planning Estimation
Sprint planning is where estimates become a commitment. This guide connects story points to velocity and capacity, and shows how to decide what actually fits in the next sprint.
Estimation and sprint planning are often confused, but they answer different questions. Estimation asks how big is this? Sprint planning asks how much of it can we finish next sprint, and which parts? Planning poker sizes the work; planning turns those sizes into a realistic, achievable commitment.
Two questions every sprint planning answers
Scrum splits sprint planning into two topics, and estimation feeds both:
- What can be done? Using estimates and velocity, the team selects backlog items that fit the sprint.
- How will it get done? The team sketches the approach for each selected item — often surfacing complexity the estimate missed.
If step two keeps revealing that step one's estimates were wrong, the problem is refinement: the stories were not understood well enough before planning. Do more refinement and less live estimating.
Velocity vs capacity — do not confuse them
| Concept | What it measures | How you use it |
|---|---|---|
| Velocity | Points the team usually completes per sprint. | A baseline forecast from past sprints. |
| Capacity | How much time the team actually has this sprint. | Adjust the forecast for holidays, leave, and events. |
Velocity is your long-run average; capacity is this sprint's reality. A team with a velocity of 24 but two people on vacation should plan for noticeably less. Blindly committing to your average velocity when half the team is out is the classic overload.
A worked planning example
A team's velocity is ~24 points. Next sprint, one developer is out for three days, so they trim their target to about 20. They pull from the top of the refined backlog:
| Story | Points | Running total |
|---|---|---|
| Password reset by email | 8 | 8 |
| Search filters on results page | 5 | 13 |
| Export report to CSV | 3 | 16 |
| Fix pagination bug | 3 | 19 |
At 19 points they stop — close to the adjusted target, with a little slack for the unexpected. The next 8-point story waits. Leaving a small buffer is not sandbagging; it is how teams actually hit their commitments.
Commit to a sprint goal, not just a point total. Points size the work, but a one-sentence goal (“users can recover their account without support”) tells the team what to protect when trade-offs appear mid-sprint.
A timeboxed sprint planning agenda
- Recap velocity and this sprint's capacity (5 min).
- Product Owner proposes a sprint goal (5 min).
- Pull and confirm estimates for candidate stories (bulk of the time).
- Discuss the “how” for the top items and adjust if needed.
- Confirm the commitment and the sprint goal together.
Keep the whole meeting to about two hours for a two-week sprint. If it runs long, the backlog was not ready.
Mistakes that overload sprints
- Planning to peak velocity. Use a rolling average, not your single best sprint.
- Ignoring capacity. Vacations and holidays are real points off the top.
- Committing to unsplit 13s. Large stories are the ones that spill over. Split them first — see Fibonacci estimation.
- No slack. Filling 100% of capacity leaves no room for the bug that always appears.
Frequently asked questions
Should we estimate during sprint planning or before?
Before, in refinement. Sprint planning should confirm estimates and make decisions, not discover sizes from scratch.
What if we finish everything early?
Pull the next refined item from the backlog. Consistently finishing early is a sign to raise your planned load slightly.
How many sprints before velocity is reliable?
Usually three to four. Before that, plan conservatively and expect the number to move.
Estimate your next sprint together
PlanITPoker gives your team a free real-time room to confirm estimates during planning, with vote analytics that make disagreement obvious. Combine it with strong facilitation to keep planning on time.
Ready to estimate with your team?
Start a free planning poker session in seconds — no signup required.
Create a Room