Sprint Capacity Calculator
Sprint capacity planning prevents the most common agile anti-pattern: committing to more work than the team can realistically complete in a sprint. Accurate capacity calculation accounts for the number of developers, their working hours, availability percentage (time not consumed by meetings and other non-development activities), planned leave, and the hours consumed by sprint ceremonies such as planning, reviews, and retrospectives. This calculator outputs net available development hours for the sprint, from which you can commit story points based on your team's established velocity.
Sprint capacity formula
gross_hours = devs * (sprint_days - leave_days) * hours_per_day
available_hours = gross_hours * (avail_pct/100)
net_capacity = available_hours - (devs * ceremony_hours)
Sprint capacity planning tips
- Use 3-sprint rolling average velocity to set commitment level, not single-sprint estimates.
- Account for public holidays in the sprint calendar before calculating gross hours.
- New team members have lower availability (40-50%) for their first 2-3 sprints due to onboarding.
- Leave a 10-15% buffer below calculated capacity for unplanned work and urgent bug fixes.
- Re-run capacity calculation at the start of every sprint as team availability changes each sprint.
Frequently asked questions
What is sprint capacity?
Sprint capacity is the total amount of work a development team can complete in a sprint, measured in hours or story points. It is always less than the theoretical maximum because team members are not available 100% of the time due to meetings, leave, interruptions, and other non-development activities.
How do I calculate sprint capacity in hours?
Sprint capacity = team_members * sprint_days * hours_per_day * availability_factor. If 5 developers work 10 days at 8 hours per day but are only 70% available (accounting for meetings and overhead), capacity = 5 * 10 * 8 * 0.70 = 280 hours. Then subtract time for sprint ceremonies (planning, retrospective, reviews).
What is an availability factor?
The availability factor (also called focus factor) is the percentage of time a team member can spend on focused development work vs. meetings, interruptions, code reviews, and administrative tasks. A realistic figure for most software developers is 60-80%. Scrum Masters and Tech Leads often have lower availability (40-60%) due to coordination responsibilities.
How do sprint ceremonies affect capacity?
Agile ceremonies consume a fixed amount of sprint time: sprint planning (2-4 hours per sprint), daily standups (15 min * sprint_days), sprint review (1-2 hours), and retrospective (1-2 hours). For a 2-week sprint, ceremonies consume approximately 8-12 hours per person, reducing net development capacity by 10-15%.
What happens if the team is over-committed in a sprint?
Over-commitment leads to incomplete stories at sprint end, forced carry-over into the next sprint, technical shortcuts that create debt, and team stress. Under-committing slightly is better than over-committing. Track velocity over 3-5 sprints to calibrate commitment levels. A team consistently finishing early can increase commitment; a team consistently carrying over should reduce it.
Official sources
- PMI: PMBOK Guide - Project Management Body of Knowledge.
- IEEE: IEEE 1490 - Guide for Adoption of PMI Standard.
Reviewed by the CalculatorHub team, edited by James Graham, 14 June 2026. See our methodology.