Measure team capacity from hours, availability, and interruptions. Compare scenarios before locking sprint commitments safely. Use simple inputs to forecast realistic story point output.
| Scenario | Team Members | Sprint Days | Hours/Day | Focus Factor | Support Load | Baseline Velocity | Likely Capacity | Safe Commitment |
|---|---|---|---|---|---|---|---|---|
| Team A | 6 | 10 | 6.5 | 85% | 10% | 54 | 30.24 | 27 |
| Team B | 8 | 10 | 6 | 82% | 15% | 68 | 34.89 | 31 |
| Team C | 5 | 9 | 6.5 | 88% | 8% | 41 | 23.76 | 21 |
1. Gross Team Hours = Team Members × Sprint Days × Hours per Day
2. Holiday Hours = Team Members × Holiday Days × Hours per Day
3. PTO Hours = PTO Person-Days × Hours per Day
4. Meeting Hours = Team Members × Sprint Days × Meeting Hours per Day
5. Net Available Hours = Gross Team Hours − Holiday Hours − PTO Hours − Meeting Hours − Planned Overhead Hours
6. Focused Hours = Net Available Hours × Focus Factor
7. Delivery Hours = Focused Hours × (1 − Support Load) × (1 − Risk Buffer)
8. Points per Effective Hour = Baseline Velocity ÷ Baseline Effective Hours
9. Raw Capacity = Delivery Hours × Points per Effective Hour
10. Commitment Capacity = Raw Capacity − Carryover Points
11. Conservative Capacity = Commitment Capacity × 0.90
12. Stretch Capacity = Commitment Capacity × 1.10
Story point capacity planning helps engineering teams commit with control. Many teams overpromise because they skip availability math. A good calculator fixes that. It converts time, interruptions, and historical delivery into a realistic sprint target.
Story points estimate effort, complexity, and uncertainty. Capacity measures how much the team can truly finish. Both numbers must connect. This tool connects them with hours, focus factor, support load, and carryover work. That gives a stronger planning baseline for agile sprint forecasting.
Start with engineer count, sprint length, and daily work hours. Then subtract holidays, leave, meetings, and known overhead. Add focus factor to reflect real maker time. Add support load for tickets, production fixes, and urgent requests. Add a risk buffer when the sprint includes uncertainty. Finally, map effective hours to story points using past velocity and effective baseline hours.
Many teams use headcount as capacity. That is too simple. Two engineers with heavy support duty are not equal to two focused engineers. Leave, incident response, reviews, and onboarding all change delivery. Another mistake is copying last sprint velocity without checking current availability. A holiday sprint should not inherit a full sprint target. This calculator reduces both errors before commitments are made.
Use the likely capacity as the planning anchor. Use the conservative value when the sprint looks risky. Use the stretch value only for optional work. This keeps commitments honest. It also improves trust across engineering, product, and delivery teams. Leaders can test scenarios fast and explain the final target with evidence.
Review actual completed points after each sprint. Compare them with the calculated forecast. Then update baseline velocity, focus factor, support assumptions, and buffer rules. The calculator becomes smarter with real team data. That creates better sprint forecasts, steadier throughput, lower rollover, and healthier delivery rhythm across the engineering organization.
Engineering managers can use this tool before sprint planning meetings. Scrum leads can align scope with real delivery bandwidth. Team members can see why commitments rise or fall. The result is clearer planning, lower overload, and more predictable releases.
It is the amount of story point work a team can realistically complete in one sprint after accounting for time, interruptions, support duty, and delivery risk.
Baseline effective hours connect your past velocity to real working time. That creates a point-per-hour ratio based on evidence instead of guesswork.
Focus factor estimates how much available time becomes true maker time. It accounts for context switching, routine communication, and small disruptions.
Yes. Carryover work still consumes delivery bandwidth. Subtracting it gives a cleaner commitment number for new stories and reduces rollover risk.
Safe commitment is a rounded conservative target. It helps teams avoid overcommitting when support load, meetings, or sprint uncertainty may increase.
Use the stretch number only for optional work. It is useful when the sprint goes smoothly, but it should not be treated as the promised commitment.
Yes. Change team size, leave, focus factor, or support load to compare best-case, expected, and constrained sprint planning scenarios quickly.
Review them every sprint. Update velocity, effective hours, support load, and focus factor using recent delivery data for better forecasting accuracy.
Important Note: All the Calculators listed in this site are for educational purpose only and we do not guarentee the accuracy of results. Please do consult with other sources as well.