Guide
How to Calculate Sprint Capacity: A Practical Guide
Sprint capacity is the amount of real delivery time your team has in a sprint. It is a practical estimate of team availability after leave, meetings and other planned work are taken into account.
In sprint planning, the goal is not to fill every hour. The goal is to make a realistic call on what the team can reasonably deliver.
How to calculate sprint capacity
The sprint capacity calculation is simple:
Sprint capacity = available team time after planned time away from delivery
Capacity flow
Relationship
A team may look like it has 50 person-days available in a 10-day sprint. After time off and meetings, the actual delivery capacity can be much lower.
Start with team availability
Begin with the people who are expected to contribute in the sprint. Do not assume everyone has the same availability.
- Developer 1: 10 working days
- Developer 2: 8 working days after 2 days of leave
- Developer 3: 9 working days after 1 day of leave
- QA 1: 10 working days
- QA 2: 9 working days after 1 day of leave
That gives a starting point of 46 person-days:
10 + 8 + 9 + 10 + 9 = 46 person-days
Adjust for meetings and planned work
Team members are not available for delivery work for every hour of the sprint. Common drains on capacity include:
- Daily Scrum
- Sprint Planning
- Sprint Review
- Sprint Retrospective
- Refinement
- 1:1 meetings
- Support work
- Training or other planned work
This is where capacity planning becomes more realistic. The question is not whether work exists. The question is how much of the team's time is genuinely available for delivery.
Worked example
Imagine a team of five people in a 10-day sprint.
5 team members × 10 working days = 50 person-days
Then the team loses:
- 4 person-days to leave
- 5 person-days to meetings and planned work
Estimated delivery capacity:
50 - 4 - 5 = 41 person-days
That is the number to use as a starting point in sprint planning. It is not a promise that the team will fill every available hour.
Team capacity is an input, not a target
Capacity tells you what is realistically available. It does not tell you that a sprint should be fully loaded.
In practice, good sprint planning also considers priorities, dependencies, complexity, uncertainty and known risks. A team can have healthy team capacity and still need to limit work in a sprint.
Capacity and velocity are related but different. Capacity is about team availability. Velocity is about how much work the team has historically completed.
Common mistakes
- Assuming every team member has the same working days and focus time.
- Ignoring leave, meetings, support work and training.
- Treating sprint capacity like a target to fill with work.
- Using historical velocity without checking current team availability.
- Forgetting that dependencies and uncertainty can reduce what is realistic.