May 19, 2026
6 min read
Capacity and sprint planning
How Time Off Affects Sprint Capacity
A practical explanation of how time off affects sprint capacity, why planned absences should be counted before sprint commitment, and how teams can avoid overloading a sprint that looks available only on paper.
Start with the simple truth
Time off directly reduces sprint capacity. A sprint does not become smaller on the calendar, but the team's usable delivery time does.
That is why vacation, public holidays, training days, sick leave, and partial availability need to be counted before the team commits to sprint scope.
Time off and capacity
Time off changes the sprint before planning starts, so it has to come out of capacity early.
Time off
Absences reduce sprint room before any estimate enters the conversation.
Absences first
Subtract planned time off before talking about commitment.
Shared impact
One absence can change handoffs, reviews, and support load for others.
Late adjustment
If it is handled late, the sprint only looked realistic on paper.
Cleaner commitment
Early visibility keeps capacity and scope aligned before overload starts.
Why time off gets missed
Time off is easy to miss when planning starts from headcount instead of actual availability.
A team may look fully staffed, but if several people are away during the sprint, the available delivery time is much lower than the headcount suggests.
Count full days and partial availability
Capacity planning should include both full-day absences and partial availability. A person who is present for only half the sprint should not be counted as if they were available for the whole sprint.
This matters especially for shared specialists, onboarding, part-time contributors, and people carrying support or release duties.
Remember that one absence can affect more than one person
Time off can reduce capacity directly, but it can also create secondary effects. If one person is away, others may need to cover reviews, support, handoffs, or specialized knowledge.
That means a single absence can create more planning impact than the missing hours alone suggest.
Why ignoring time off causes overcommitment
When time off is not counted up front, the sprint looks realistic during planning and overloaded during execution.
The team then discovers too late that the plan depended on capacity that never actually existed.
- The team commits to work it cannot realistically finish.
- Unfinished work rolls into the next sprint.
- Quality pressure increases near the end.
- Retrospectives repeat the same capacity complaint.
A better planning habit
A healthier habit is to check time off before sizing the sprint commitment. The team should know who is available, who is partially available, and what known absences affect the sprint.
That does not make the sprint perfectly predictable, but it removes one of the easiest sources of avoidable overcommitment.
What to do when capacity drops
If time off reduces capacity, the sprint plan should change. That may mean taking fewer stories, choosing smaller slices, moving lower priority work out, or leaving more buffer for uncertainty.
The important part is that the capacity signal is allowed to affect the commitment instead of being treated as a note everyone ignores.
Where to go next
If time off keeps surprising your sprint plan, the capacity tool is the best next step.
That is where the team can turn vacations, holidays, and partial availability into a clearer capacity view before sprint planning turns into wishful thinking.
TL;DR
- Time off directly reduces usable sprint capacity.
- Headcount is not the same thing as actual availability.
- Absences should be counted before the team commits to sprint scope.
- Capacity gets more honest when time off is removed early instead of explained away later.