What the Sprint Capacity Calculator does
The Sprint Capacity Calculator estimates how many person-hours a team can plan for during a sprint. It starts with the team's scheduled working time, subtracts hours when team members are unavailable, and applies a reserve for support requests or interruptions. The result, Planned Capacity (person-hours), is a planning estimate expressed as total team hours.
This estimate helps a team discuss the amount of work that may fit into a sprint. It is not a direct measure of story points, completed tasks, or individual performance. Teams can use it as one input to planning, alongside recent delivery history, work dependencies, and the definition of ready for their work.
The model assumes each person has the same entered daily working hours and the same unavailable hours for the sprint. It also applies one reserve percentage to the team's capacity after absences are subtracted. Keep those assumptions in mind when team schedules differ significantly.
How to use the Sprint Capacity Calculator
Enter the team and sprint details using consistent units. Count people who are expected to contribute during the sprint, enter the number of working days in the sprint, and set the average working hours per person per day. Working hours should reflect time available for work rather than simply the length of a workday.
- Team members: Enter the number of people whose capacity you want to include.
- Sprint workdays: Count scheduled working days, excluding weekends or other nonworking days as appropriate for the team.
- Working hours per person per day: Use a reasonable average for the sprint period.
- Unavailable hours per person: Include expected time away, such as planned leave, training, or other commitments that prevent sprint work.
- Support and interruption reserve: Estimate a percentage of remaining capacity to hold for unplanned requests and routine interruptions.
Review the assumptions with the team before using the output to shape a commitment. If only some people have planned absences, a shared average can hide the variation. You can calculate groups separately for a closer estimate, then add the results, while using the same reserve approach consistently.
How the Sprint Capacity Calculator formula works
The formula is (team_size × work_days × hours_per_day − team_size × unavailable_hours) × (1 − reserve_percent ÷ 100). First, team size is multiplied by sprint workdays and working hours per day to estimate scheduled team hours. Next, the unavailable hours per person are multiplied by team size and subtracted. Finally, the reserve percentage is converted to a decimal and removed from the remaining hours.
For example, assume a five-person team has a ten-workday sprint, each person has 7.5 working hours per day, each person expects four unavailable hours, and the team reserves 15 percent for support and interruptions. Scheduled hours are 5 × 10 × 7.5, or 375 person-hours. Unavailable time is 5 × 4, or 20 person-hours. After subtracting that time, 355 person-hours remain. Applying the reserve gives 355 × (1 − 15 ÷ 100), which equals 301.75 person-hours.
This output is a total across the team. It does not mean every person should receive an equal amount of assigned work. Collaboration, reviews, specialized skills, and dependencies can affect how available time translates into a workable plan.
Use cases for the Sprint Capacity Calculator
A capacity estimate can help a team make planning conversations more concrete. It can be useful when comparing sprint plans with different durations, reviewing the effect of known absences, or checking whether enough time has been left for support work. A project lead may also use it to explain why a sprint with fewer available team hours should contain a smaller amount of planned work.
For a team with regular service requests, the reserve gives that work a visible place in the estimate. If the team has historical records, compare the chosen reserve with the actual time spent handling interruptions over several sprints. The calculator itself does not determine the right reserve. That judgment depends on the team's work pattern and should be revisited as conditions change.
Capacity can also support conversations across teams when different groups have different sprint lengths or planned time away. Compare estimates only when the inputs and definitions are similar. A person-hour estimate is not interchangeable with story points, since point scales and estimation practices vary by team.
Other factors to consider when calculating sprint capacity
Working hours are not necessarily all devoted to sprint backlog items. Meetings, planning, code review, mentoring, operational work, and coordination can reduce the time available for focused delivery. Decide whether those activities are already reflected in the daily hours or should be accounted for elsewhere. Avoid subtracting them twice.
Consider whether the team's composition or responsibilities change during the sprint. A new member may need onboarding, while a specialist may be a bottleneck for dependent work. A single average cannot represent every difference. When such variation is material, estimate capacity by person or by group and make the method visible.
Finally, use past outcomes as a reality check. If the calculated capacity repeatedly differs from what the team can complete, inspect the assumptions. Unplanned work, dependencies, estimation uncertainty, or interruptions may have changed. Adjust the inputs based on observed experience rather than treating the output as a target for individual utilization.
FAQ
Does planned capacity tell us how many story points to commit to?
No. The result is in person-hours. Story points are a team-specific estimation measure, so capacity hours do not convert reliably into points without a separate, locally established relationship. Teams can use the estimate alongside prior sprint outcomes when discussing scope.
What should count as unavailable hours?
Include expected hours when a person cannot work on the sprint because of leave, training, or other scheduled commitments. Use the same definition across the team. If absences vary widely, calculate separate groups or person-level estimates rather than relying on one average.
How should the reserve percentage be chosen?
Use the team's experience with support work and interruptions as a starting point. Review actual time spent on those demands over multiple sprints and adjust when the pattern changes. The calculator does not prescribe a universal reserve.
Should meetings be included in working hours?
Choose a consistent interpretation. If the hours-per-day input represents time available after recurring meetings, do not subtract those meetings again. If it represents a broader workday, account for meeting time separately in your planning assumptions.
Can this estimate predict whether a sprint will succeed?
No. It estimates available hours under entered assumptions. Delivery also depends on the work selected, dependencies, changing priorities, quality requirements, and other conditions. Use the number as a planning aid and revisit it as the sprint unfolds.