Calculators

Sprint Capacity Calculator

Estimate a team's available sprint capacity in person-hours after subtracting planned time away and recurring non-project work. This is a planning estimate, not a guarantee of completed work.

Loading calculator...

What this Sprint Capacity Calculator does

The Sprint Capacity Calculator estimates how many person-hours a team has available for project work during a sprint. It starts with the team's scheduled working time, then subtracts hours associated with planned absences and recurring non-project responsibilities. The result is shown in person-hours, which makes the assumptions visible and gives a team a shared starting point for planning.

Capacity is a planning input. It does not predict how many story points, features, or tasks a team will finish. Work differs in uncertainty, coordination needs, and skill requirements. The estimate also depends on whether the hours entered reflect realistic availability. Use the result to discuss the sprint plan, then review it alongside the team's recent experience and current priorities.

The calculator uses five inputs: team members, working days in the sprint, work hours per person per day, total person-days away, and recurring non-project hours per person per day. Its formula calculates scheduled person-hours and subtracts the two specified deductions. It assumes each team member has the same daily work hours and recurring overhead. A person-day away removes one person's full entered workday.

How to use the Sprint Capacity Calculator

Enter the number of people who contribute to the sprint, the sprint's working days, and the average hours each person is scheduled to work per day. Count working days rather than calendar days. If team schedules differ, use a reasonable average and record that simplification for the planning discussion.

Next, enter the team's total person-days away. Add the days for each person's expected vacation, appointment, training, or other full-day absence. For example, one member away for two days and another away for one day equals three person-days. Partial days can be entered in halves with the supplied step size.

Finally, estimate recurring non-project hours per person per working day. This can include regular support duties, required meetings, administration, or other commitments that take time from the work being planned. Use an average that fits the sprint period. Do not include the same commitment again as time away.

  • Use a consistent definition of project work across the team.
  • Enter planned absences as person-days, not as a team-wide day count.
  • Review the deductions together so that overlapping time is not counted twice.
  • Recalculate if the sprint length or staffing assumptions change.

The output is available capacity in person-hours. Treat it as a ceiling under the stated assumptions, not a target that every person must fill. Teams may choose to leave some capacity unplanned for unexpected work or changing priorities.

How the Sprint Capacity Calculator formula works

The formula is: (team members × working days × work hours per person per day) − (person-days away × work hours per person per day) − (team members × working days × recurring non-project hours per person per day).

The first multiplication estimates scheduled hours for the whole team. The second term converts the total absence days into hours, using the same daily-hours assumption. The final term estimates recurring overhead across each team member and each working day. Subtracting both deductions leaves the available person-hours under this simple model.

For example, suppose a team has 5 members, a 10-working-day sprint, and 6 work hours per person per day. The team has 5 × 10 × 6 = 300 scheduled person-hours. If there are 2 person-days away, subtract 2 × 6 = 12 hours. If recurring non-project work averages 1 hour per person per day, subtract 5 × 10 × 1 = 50 hours. The estimated available capacity is 300 − 12 − 50 = 238 person-hours.

This example shows why the units matter. Team size multiplied by working days and hours per day produces person-hours. Person-days away multiplied by hours per day also produces hours. The overhead term has the same person-hour unit. The formula therefore combines comparable quantities.

Use cases for the Sprint Capacity Calculator

A team can use the estimate when preparing a sprint planning conversation, especially when staffing, leave, or recurring duties differ from the previous sprint. The calculation makes these factors explicit before the team chooses work. It can also help project coordinators explain why the hours available this cycle differ from a typical one.

For a people and project planning discussion, compare the estimate with the work the team expects to undertake and the time needed for collaboration. A capacity figure may prompt useful questions about who is available, where specialist knowledge is needed, and whether the plan leaves room for support requests. It can also establish a baseline for reviewing the assumptions after the sprint.

Use the result alongside historical delivery information when the team has relevant, recent data. Person-hours describe time, while story points and completed items describe work outcomes. The calculator does not convert between them, and such a conversion would depend on the team's own work patterns and definitions.

Other factors to consider when calculating sprint capacity

The estimate simplifies real work. Team members may have different schedules, responsibilities, or availability. A single average can hide those differences. For a small team, calculate individual availability separately in the planning discussion if that gives a clearer view, while keeping this calculator's output as a quick aggregate estimate.

Unexpected incidents, review delays, dependencies, onboarding, and coordination can affect the time available for planned work. Some of these may be covered by the recurring non-project hours input, while others are uncertain. Avoid subtracting a speculative buffer as though it were measured time. Instead, state any planning reserve separately so the team can discuss its purpose.

Keep the inputs current and use the same method across sprints when comparing estimates. After the sprint, reflect on whether absences and recurring duties were represented accurately. Adjust future inputs based on observed schedules, while remembering that capacity is only one part of a plan. Priorities, task size, quality expectations, and external dependencies also shape delivery.

Frequently asked questions

Does available capacity predict completed work?

No. It estimates time under the inputs provided. Work complexity, dependencies, interruptions, and team experience influence what can be completed, so the result should support discussion rather than promise an outcome.

What counts as a person-day away?

It is one team member's full scheduled working day away during the sprint. Two people each away for one day count as two person-days. Enter partial absences as a fraction such as 0.5.

What should recurring non-project hours include?

Include predictable work that takes time from the project each day, such as recurring support or administration. Avoid counting hours already included as full or partial days away.

Can I use this calculator for a team with different schedules?

Yes, as an approximation. Enter an average daily work schedule and understand that individual availability may vary. For precise planning, discuss each person's schedule and responsibilities directly.

Why is the result in person-hours?

The formula combines team size, working days, and daily hours, then subtracts absence and overhead hours. Person-hours make the time assumption clear, but they do not represent story points or a guaranteed amount of delivery.

Written by

ethicsandentrepreneurship.org Editorial Team

Editorial team

ethicsandentrepreneurship.org publishes practical how-to guides and educational articles with clear steps and useful context.