Sprint Capacity Calculator
Calculate your team's realistic sprint capacity accounting for meetings, PTO, holidays, and historical velocity. Plan sprints accurately with data-driven estimates.
Why use Sprint Capacity Calculator?
Planning sprints without understanding your team's actual capacity leads to overcommitment, burnout, and missed deadlines. This calculator helps you account for real-world factors like meetings, holidays, and PTO to set realistic sprint goals that your team can actually achieve.
Frequently Asked Questions
How is sprint capacity calculated?
We start with raw hours (team members × hours/day × working days), then subtract meeting overhead percentage, holidays, and individual PTO. This gives you the true available hours for development work.
What's a good hours-per-story-point ratio?
Industry averages range from 4-8 hours per story point. Start with 6 hours/point and adjust based on your team's historical velocity. Track actual completion to refine your estimate.
Should I include all meetings in the overhead?
Include recurring meetings like standups, sprint planning, reviews, and retrospectives. For a typical 2-week sprint, 15-25% meeting overhead is common. Don't include one-off meetings in the percentage.
How do I account for part-time team members?
Set their hours/day to their actual availability. For example, a half-time developer would have 4 hours/day instead of 8.