What this Sprint Capacity Calculator does
The Sprint Capacity Calculator estimates how many person-hours a team has available for planned sprint work. It starts with the scheduled hours across the team and sprint, subtracts time off, then reduces the remainder by the share reserved for non-project work. The result is a planning estimate in person-hours.
Capacity describes time that may be available. It does not say how much work the team will finish, and it does not convert hours into story points. Actual delivery depends on task size, uncertainty, dependencies, interruptions, and the way a team works together. Treat the result as one input to a planning conversation, rather than a commitment or performance measure.
The model assumes everyone has the same number of scheduled hours per workday. It also applies one overhead percentage to the remaining team hours. These assumptions keep the calculation understandable, but they may not fit a team with varied schedules or roles. In those cases, calculate smaller groups separately and add their results.
How to use the Sprint Capacity Calculator
Enter the team size, number of working days in the sprint, and scheduled hours per person per day. Count only working days for the people included. Then enter expected time off as total person-days across the whole team. One person away for two days is two person-days. Two people away for two days each is four person-days.
Finally, estimate the percentage of the remaining schedule reserved for activities outside planned project work. This could include recurring meetings, support rotation, administration, or other duties that regularly take time during the sprint. Use a percentage that reflects the team's expected schedule, not an idealized week.
- Team members: Count people whose time is included in the plan.
- Sprint workdays: Exclude weekends or other days when the team is not scheduled to work.
- Scheduled hours: Use work hours per person per day, not elapsed clock hours.
- Time off: Add the group's planned absence in person-days.
- Non-project time: Enter a percentage of the remaining scheduled hours.
Review the result with the team. If the estimate looks high, discuss missing duties, holidays, or partial availability. If team members have different work patterns, run separate estimates for each group instead of forcing an average that hides meaningful differences.
How the Sprint Capacity Calculator formula works
The formula is (team members × sprint workdays − total time-off person-days) × hours per person per day × (1 − non-project percentage ÷ 100). It first calculates scheduled person-days for the full team, removes days when people are unavailable, converts the balance into person-hours, and then reserves the selected share for non-project work.
For example, a five-person team working a ten-day sprint has 50 scheduled person-days. If the team expects two person-days of leave, 48 remain. At eight scheduled hours per person per day, that is 384 hours before the overhead adjustment. With 20% planned non-project time, the estimate is 384 × (1 − 20 ÷ 100), or 307.20 person-hours.
The units matter. Team size multiplied by workdays gives person-days. Subtracting time off leaves available person-days. Multiplying by hours per day gives person-hours. The final percentage factor is a proportion, so it reduces hours without changing their unit. This result can support a discussion of available time, but the formula does not estimate velocity or guarantee a particular quantity of completed work.
Use cases for the Sprint Capacity Calculator
A capacity estimate can help a project group prepare for sprint planning when vacations, onboarding, or recurring responsibilities affect availability. It gives the team a consistent starting point and makes assumptions visible. That can be useful when comparing a typical sprint with one that contains a holiday or a period of heavier support work.
Project leads can also use the estimate to explain why a sprint plan may need to account for reduced availability. For instance, a team can compare the result before and after recording planned leave. The difference makes the effect of those absences clear in hours, even when the team later plans work using another sizing method.
For a team with distinct schedules, calculate capacity by group. A three-person group working six hours daily can be estimated separately from a two-person group working eight hours. Use each group's relevant workdays, time off, and overhead assumption, then add the results. This approach is more transparent than treating every person as interchangeable.
Keep the estimate connected to current conditions. If support demand or meeting load changes, revisit the overhead assumption. The calculator is most useful when its inputs come from the people doing the work and when the team is comfortable revising them as new information appears.
Other factors to consider when calculating sprint capacity
Scheduled hours are only one view of availability. Part-time schedules, public holidays, training, onboarding, and rotating responsibilities can affect individuals differently. The simple model handles time off as person-days and other work as a shared percentage. It does not model the timing of an absence or distinguish types of work.
Coordination also affects how time can be used. Two people may have the same number of available hours while working on tasks with different dependencies. A blocked task or a needed review can delay progress even when total capacity appears ample. Use the estimate alongside discussion of dependencies, risks, and the work's definition of completion.
Historical delivery can provide context, but avoid treating a single capacity figure as a productivity target. Teams change, work varies, and estimates contain uncertainty. Record what assumptions were used, compare them with what happened, and adjust future planning estimates based on evidence from the team's own experience.
Most importantly, invite team members to check the inputs. The people closest to the work can identify recurring duties or schedule limits that a high-level plan misses. A shared estimate is more useful when everyone understands what it includes and what it leaves out.
Frequently asked questions
Does capacity mean the team will complete that many hours of work?
No. The result estimates available person-hours after the entered adjustments. Meetings, interruptions, task dependencies, and unexpected work can change how much planned work is completed. Use it as a planning aid, not a delivery promise.
Should I enter story points instead of hours?
No. This formula calculates person-hours. Story points are a separate estimation convention and do not have a universal conversion to hours. Keep the units clear and use the team's established approach to sizing work.
How should I count partial days off?
Enter the absence as a fraction of a person-day when the schedule makes that reasonable. For example, a half-day away counts as 0.5 person-days. Apply the same convention consistently across the team's inputs.
What if team members have different schedules?
Estimate each schedule group separately using its own team size and hours per day. Add the resulting person-hours. This keeps differences in availability visible and avoids implying that every person follows the same schedule.
What does the non-project time percentage include?
It represents the share of remaining scheduled time reserved for duties outside the planned project work, based on the team's assumption. Decide what belongs in that category before entering a value, and avoid counting the same time again as time off.