Sprint Capacity Calculator

A Sprint Capacity Calculator helps you estimate how much work your team can realistically commit to in the next sprint after you account for time off, meetings, support work, and normal delivery overhead. That is useful for scrum masters, engineering managers, product managers, and agency leads who want a better planning baseline than gut feel.

Teams often overcommit because they start with calendar days instead of available delivery time. A clearer capacity estimate helps you protect focus time, avoid rollover, and set a sprint goal the team can actually finish.

How to Use the Sprint Capacity Calculator

1. Enter the number of people contributing to the sprint.
2. Add the sprint length in working days or hours.
3. Subtract planned leave, holidays, training time, and known absences.
4. Reduce further for recurring meetings, support duty, and other non-project work.
5. Apply a realistic focus factor if your team rarely gets 100 percent maker time.
6. Review the final available capacity and use it to guide sprint commitment.

If your team plans in story points, use the capacity result as a constraint rather than a replacement for velocity.

What Sprint Capacity Measures

Sprint capacity is the amount of delivery time your team has available for planned work during one sprint.

Capacity input	What it means	Example
Team size	Number of contributors expected to deliver sprint work	6 people
Working time	Total planned workdays or hours in the sprint	10 working days
Planned absences	Leave, holidays, training, interviews	4 person-days
Recurring overhead	Standups, ceremonies, support, admin time	18 team hours
Focus factor	Share of remaining time usable for delivery	85%

This is why two teams with the same headcount can have very different sprint capacity.

Sprint Capacity Formula

Gross team hours = Team size x Sprint working hours
Net available hours = Gross team hours - Leave hours - Meeting hours - Support hours
Sprint capacity = Net available hours x Focus factor

If you plan from historical velocity instead of hours, you can also adjust velocity by the percentage of normal availability in the upcoming sprint.

Example Sprint Capacity Calculation

Suppose a product squad has these assumptions for a two-week sprint:

• Team size: 6
• Working hours per person in the sprint: 80
• Planned leave: 16 hours
• Ceremonies and recurring meetings: 24 hours across the team
• Support and bug triage: 20 hours across the team
• Focus factor: 85%

The estimate would be:

Gross team hours = 6 x 80 = 480
Net available hours = 480 - 16 - 24 - 20 = 420
Sprint capacity = 420 x 0.85 = 357 hours

That gives the team a more realistic planning number than simply saying, "We have six people for two weeks."

Hours vs Story Points in Sprint Planning

• Capacity in hours shows how much delivery time is actually available.
• Story points represent relative effort, complexity, and uncertainty.
• Velocity shows how many points the team usually finishes at a given capacity level.
• A large drop in availability usually means planned points should drop too.

The best teams use capacity to set the boundary and velocity to decide how much point-based work fits inside it.

What Usually Reduces Sprint Capacity

• Public holidays and planned leave
• Support rotations or production incidents
• Backlog grooming, reviews, and cross-team coordination
• Hiring loops, interviews, or internal training
• Excessive context switching across several priorities

If these factors are ignored, the sprint plan often looks efficient on paper and unstable in practice.

Common Sprint Capacity Mistakes

• Planning from headcount without subtracting time off
• Assuming every hour is usable for feature work
• Treating velocity as fixed when availability changes sharply
• Forgetting operational work such as incidents, reviews, or stakeholder requests
• Adding stretch backlog items before the core sprint goal is protected

If you want to connect planning time with estimation quality, pair this result with a Story Points Calculator or a Velocity Calculator.

FAQ

What is a sprint capacity calculator?

It estimates how much working time a team has available for planned sprint work after accounting for absences and overhead.

Is sprint capacity the same as velocity?

No. Capacity is available time, while velocity is the amount of point-based work the team usually completes.

Should meetings be removed from capacity?

Yes. Ceremonies, coordination meetings, and support work reduce the time available for backlog delivery.

What is a good focus factor for sprint planning?

There is no single correct number, but many teams use a discount instead of assuming 100 percent delivery time because interruptions are normal.

Can I use sprint capacity for story-point planning?

Yes. Capacity helps you adjust expected point commitment when the upcoming sprint has less or more availability than usual.