May 19, 2026
6 min read
Capacity and sprint planning
How to Calculate Sprint Capacity
A practical guide to calculating sprint capacity so the team can make a more realistic commitment before the sprint starts instead of discovering overload too late.
Start with actual availability, not ideal capacity
The most common mistake in sprint capacity planning is starting from theoretical full availability instead of the time the team can actually use for delivery.
A sprint may be two weeks long on the calendar, but that does not mean every person has ten clean days available for sprint work.
Calculating capacity
Good sprint capacity starts with real availability and subtracts the load that already exists.
Real availability
Capacity starts with who is actually available in this sprint.
Who is available
Count the people who will really contribute during the sprint.
Time off
Subtract known absences before planning gets optimistic.
Recurring load
Meetings, support, and other obligations reduce usable time.
Focus time
Use the time the team can sustain, not just hours on the clock.
Honest commitment
A useful capacity view is allowed to shrink the sprint before overload happens.
Count who is really available
Begin with the people who will actually contribute during the sprint and note any partial availability up front.
New joiners, part-time contributors, shared specialists, and rotating support responsibilities all change the real capacity picture before any estimate even enters the conversation.
Subtract time off and known absences
Planned vacation, public holidays, training days, and other known absences should come out before the team starts talking about commitment.
If time off gets treated as an afterthought, the sprint often looks realistic only on paper.
Account for meetings and other recurring load
Sprint planning, standups, reviews, retrospectives, recurring syncs, support obligations, and operational interruptions all reduce the time available for focused work.
These do not make the team less productive. They are simply part of the real delivery environment and need to be reflected honestly.
Think in focus time, not just hours on the clock
Two teams can have the same headcount and the same sprint length but very different usable capacity because their focus time is different.
Capacity gets more realistic when the team asks how much sustained delivery time is actually available after the normal interruptions of work are counted.
Use capacity to challenge the commitment, not decorate it
Capacity planning only helps if it is allowed to change what the team commits to. If the sprint scope is already fixed politically, the capacity calculation becomes a ritual instead of a decision tool.
A useful capacity view should be able to force a smaller, more honest commitment when the numbers say the team is overloaded.
Watch for the common failure modes
Capacity planning usually breaks when the team assumes full availability, ignores meeting load, or treats last sprint's pain as something that will magically not repeat this time.
- Assuming everyone is fully available.
- Ignoring time off until after planning.
- Forgetting recurring meetings and support work.
- Treating ambition as capacity.
Where to go next
If your team wants sprint commitment to reflect actual availability instead of optimistic guesswork, the capacity tool is the best next step.
That is where the team can turn headcount, time off, and focus time into a more honest capacity view before the sprint starts.
TL;DR
- Sprint capacity should start from actual availability, not ideal headcount.
- Time off, meetings, support load, and focus time all reduce usable capacity.
- Capacity only helps when it can change the sprint commitment.
- Good capacity math is only useful when it can reduce the commitment before overload starts.