What this Sprint Capacity Calculator does
The Sprint Capacity Calculator estimates how many focused work hours a team may have available during a sprint. It starts with the number of team members and working days, subtracts planned person-days away, and multiplies the remaining person-days by daily work hours and a focus factor. Its result is Estimated focused work hours.
This measure can support a planning conversation when a team is deciding how much work to consider. It is a simple worksheet-style estimate. It does not determine which backlog items fit, estimate story points, or predict whether the team will meet a delivery date. People-hours describe time, while story points and task estimates describe work according to a team's own methods.
The calculator assumes every team member has the same number of working days and daily available hours. It also assumes time away is entered as person-days, so one person away for two days counts as two person-days. The focus factor represents the share of scheduled capacity expected to remain for planned work after ordinary interruptions and other responsibilities.
How to use the Sprint Capacity Calculator
Enter the team's size, the number of working days in the sprint, and the available work hours per person per day. Then enter the team's total planned person-days away and choose a focus factor as a decimal from 0.1 to 1. A factor of 0.8 means the estimate counts 80 percent of the hours remaining after time away.
- Team members: Count the people whose capacity is part of the planning estimate.
- Sprint working days per person: Count workdays in the sprint, excluding weekends or other nonworking days for the team.
- Available work hours per person per day: Use hours available for work across the day, not automatically the full length of a workday.
- Total person-days away: Add each person's planned days away, such as leave or training days.
- Focus factor: Use a reasonable planning assumption for time likely to remain available for planned work.
Review the inputs together before using the result. If some people work part time, have different calendars, or have substantially different responsibilities, one team-wide average may conceal meaningful differences. You can estimate smaller groups separately and combine their capacity if your planning process supports that approach.
How the Sprint Capacity Calculator formula works
The formula is (Team members × Sprint working days per person − Total person-days away) × Available work hours per person per day × Focus factor. First, team size multiplied by sprint days gives gross person-days. Subtracting time away yields scheduled person-days available. Multiplying by daily hours converts those days into hours. The focus factor then reduces that total to account for time expected to be absorbed by other work and interruptions.
For example, suppose a five-person team has a ten-day sprint, six available work hours per person per day, two total person-days away, and a focus factor of 0.8. The calculation is (5 × 10 − 2) × 6 × 0.8 = 230.4 focused work hours. The intermediate total is 48 person-days after time away, or 288 scheduled hours. Applying 0.8 gives 230.4 estimated focused work hours.
The result is expressed in hours because the formula multiplies days by hours per day. The two decimal places make the arithmetic precise, but they do not make the forecast equally precise. Team availability, dependencies, urgent work, and estimates all involve uncertainty. Treat the output as a consistent planning reference rather than a promise about how much work will be finished.
Use cases for the Sprint Capacity Calculator
A team can use the estimate at the start of a sprint to compare the available time with the work under consideration. It can help surface a mismatch early, especially when planned leave, onboarding, or a shorter work period changes the team's usual availability.
- Planning around leave: Account for known vacations or appointments instead of assuming everyone is present every day.
- Comparing sprint conditions: Apply the same assumptions to a typical sprint and one with training or release responsibilities to see how available hours change.
- Making assumptions visible: Record the focus factor used so the team can discuss whether it reflects recent working conditions.
- Supporting a retrospective: Compare the estimate with actual availability and discuss which assumptions were too high or low.
These uses work best when the team discusses the inputs together. Capacity can inform selection, but the team still needs to inspect the work, its dependencies, its risks, and its definition of done. The calculator does not assign work to individuals or decide the sprint goal.
Other factors to consider when calculating sprint capacity
Capacity changes when responsibilities change. Support rotations, meetings, incident response, mentoring, onboarding, and cross-team coordination may take substantial time. If those duties are predictable, the focus factor can reflect them, or the team can reduce available hours directly. Avoid counting the same constraint twice. For instance, if support time is already removed from daily hours, do not also lower the focus factor for that same support load.
Part-time schedules and staggered working days also matter. A person who works fewer hours or fewer sprint days should not be treated as having the same capacity as a full-time teammate. For a rough estimate, teams may use an average, but the assumptions should be stated. For more detail, calculate the groups separately and add the results.
Historical data can help the team review its assumptions, but past capacity does not guarantee future outcomes. A team may face unusual dependencies, changes in scope, or unplanned work. Keep the estimate connected to current availability and revisit it when circumstances change.
Frequently asked questions
Does the result tell us how many story points to commit to?
No. The result is in focused work hours. Story points are team-specific estimates and cannot be converted reliably from hours by a universal ratio. Use the team's own planning practices and evidence when considering work for a sprint.
What should we enter for time away?
Enter the sum of planned person-days away across everyone included. For example, two people each away for one day equals two person-days. Do not enter the number of people away unless each is away for exactly one day.
How should we choose a focus factor?
Use a transparent assumption informed by the team's recent experience and expected responsibilities. A lower factor reduces estimated focused hours. Review it as conditions change, and avoid treating any single value as a universal standard.
Can we use the estimate for a team with part-time members?
Yes, as a rough estimate if you adjust the inputs to represent their schedules. Because this calculator applies one shared daily-hours value and sprint length to all members, teams with varied schedules may get a clearer estimate by calculating groups separately.
Does higher capacity mean more work will be completed?
Not necessarily. The estimate describes available focused time under stated assumptions. Completion also depends on the size and uncertainty of work, dependencies, defects, interruptions, and team practices. Use it as one planning input and update plans when new information appears.