What the Sprint Capacity Calculator does
The Sprint Capacity Calculator estimates how many work hours a team may have available during a sprint. It combines team size, the number of working days in the sprint, average work hours available to each person per day, and a focus factor. The result is a single estimate in hours that can support planning conversations before a sprint begins.
Capacity is an estimate of available effort. It does not predict how many backlog items the team will finish, because tasks differ in size, uncertainty, coordination needs, and dependencies. It also does not determine how much work the team should accept. Treat the result as one input to a discussion that includes the people doing the work and their recent experience.
The model assumes that each team member has the same average daily hours and that the focus factor applies to the team's total theoretical hours. Those assumptions make the calculation easy to inspect. If schedules vary substantially, calculate smaller groups separately or use a team-agreed average that reflects the actual sprint.
How to use the Sprint Capacity Calculator
Enter the number of people who will contribute, the sprint's working days, average hours per person per day that can be devoted to sprint work, and a focus factor as a percentage. Use the same definition of a working day throughout. For example, exclude weekends if the team does not plan work on weekends.
- Team members: Count the people whose work is represented in the estimate.
- Sprint length: Enter working days, rather than calendar days.
- Available work hours: Estimate hours for sprint work after routine meetings and other regular commitments.
- Focus factor: Choose a percentage based on the team's own planning approach and observed interruptions or coordination demands.
With the default values of five people, ten working days, six available hours per person per day, and a 70 percent focus factor, the calculation is (5 people × 10 days × 6 hours per person per day × 70) ÷ 100. That produces 210 estimated hours. The factor reduces the theoretical 300 hours to account for the portion the team expects to focus on planned sprint work.
Use one consistent time unit when comparing the result with work estimates. If the team estimates in person-days or story points, this hourly result cannot be compared directly without a separate, team-specific method. Avoid converting hours to points using a universal ratio.
How the Sprint Capacity Calculator formula works
The formula is (team members × sprint length × available hours per person per day × focus factor) ÷ 100. Team size multiplied by working days gives person-days. Multiplying by available daily hours gives theoretical sprint work hours. Multiplying by the focus percentage and dividing by 100 applies that percentage to the total.
For instance, a team of four working for eight days, with five hours per person per day and a 75 percent focus factor, gets (4 × 8 × 5 × 75) ÷ 100 = 120 hours. Each input has a clear unit, so a change can be explained: fewer working days or fewer available hours lowers the estimate, while more team members raises it.
The focus factor is an explicit planning assumption, not a universal productivity score. A team might choose it by reviewing what portion of past available hours was spent on planned work, then agreeing whether that history is a useful guide for the coming sprint. Keep the value grounded in the team's context and revise it when conditions change.
Use cases for sprint capacity
A capacity estimate can help a team prepare for sprint planning, compare two staffing or schedule scenarios, or make visible the effect of leave and recurring commitments. It can also help a project lead explain why the number of available hours differs between sprints, especially around holidays, training, or planned project work outside the sprint.
For a team with different schedules, one option is to estimate each subgroup separately. Calculate each subgroup's people, days, available hours, and factor, then add their estimated hours. This is useful only if the assumptions remain clear. A single team-wide average may be simpler when the schedules are similar, while separate estimates can represent materially different availability more accurately.
During planning, compare the estimate with the team's recent delivery patterns and discuss the work's risks and dependencies. Capacity can guide the conversation, but the team still needs to select work based on its understanding of scope, priorities, and likely interruptions. Revisit the estimate when a major change occurs, such as a person becoming unavailable or an urgent operational responsibility appearing.
Other factors to consider when calculating sprint capacity
Availability varies for reasons a simple formula cannot represent individually. Planned leave, onboarding, support rotations, cross-team meetings, incidents, and work that is not tracked in the sprint can all affect the hours a person can devote to planned tasks. Reflect known commitments in the available-hours estimate or adapt the team calculation so those commitments are not counted as focused sprint time.
Team size alone also does not capture how work is shared. Some tasks need specific skills, reviews, or decisions from a small number of people. Adding total hours does not remove those constraints or show whether several contributors can work in parallel. Dependencies and handoffs can affect progress even when the team has enough total hours.
Finally, estimates should be updated with evidence. Compare planned assumptions with what the team learned, while recognizing that one sprint may not represent a stable pattern. The number is most useful when it helps people discuss constraints openly, rather than when it is treated as an individual target or a commitment independent of scope.
Frequently asked questions
What does sprint capacity mean?
It is an estimate of the work time a team can make available during a sprint under stated assumptions. It describes available hours, not guaranteed output or a count of completed tasks.
What focus factor should I use?
Use a value the team can explain from its own experience and expected commitments. There is no single percentage that fits every team or sprint. Review the assumption when schedules or working conditions change.
Should I enter calendar days or working days?
Enter the number of working days the team plans to work during the sprint. Keep that convention consistent when comparing estimates from different sprints.
Can I convert estimated hours to story points?
This calculation does not provide a reliable general conversion to story points. Points are a team-specific relative estimate. Use the team's own planning practices if it chooses to relate capacity to its backlog.
Does higher capacity mean the team should take on more work?
Not automatically. The result is one planning input. Consider task uncertainty, dependencies, skills, priorities, and recent delivery experience before selecting sprint work.