Tools › Agile & sprint planning › Sprint Capacity Calculator
Sprint Capacity Calculator
The Sprint Capacity Calculator helps you plan realistically: how many hours can your team actually spend on development work in the upcoming sprint? By entering team size, sprint length, working hours per day, a focus factor for overhead, and planned absences, you instantly get the net available hours.
Sprint Capacity Calculator: how does it work?
Formula: capacity = teamSize × days × hoursPerDay × focusFactor − timeOffHours. The focus factor (default 0.8) accounts for daily overhead such as stand-ups, code reviews, email and unexpected interruptions. A value of 0.8 means 80% of working time is effectively spent on sprint tasks. Subtract the total planned time-off hours for the whole team. The result is the net capacity you can compare against your sprint's story-point estimate.
Example
Team of 5 people, 10-day sprint, 8 hours per day, focus factor 0.8, 16 hours of time off in total. Gross hours: 5 × 10 × 8 = 400 hours. After focus factor: 400 × 0.8 = 320 hours. After time off: 320 − 16 = 304 available hours. If the team averages 8 hours per story point, roughly 38 story points fit in this sprint.
Frequently asked questions
What is a good focus factor?
A focus factor of 0.8 is a widely used starting point: you assume 80% of working time goes to sprint tasks and 20% to overhead such as meetings, email and unplanned requests. For new teams or teams with many ceremonies, 0.7 is safer; for experienced, stable teams you might use 0.85. Measure after each sprint how many hours were actually spent on tasks and adjust accordingly.
Should I work in hours or story points?
This calculator works in hours, because hours are the most direct measure of availability. To convert to story points, divide the net hours by your team's average time per story point (velocity per hour). Hours are especially useful for new teams that do not yet have a stable velocity.
How do I handle part-time team members and leave?
Adjust teamSize to the number of people and add all known absences to timeOffHours: holidays, public holidays, training days and known sick leave. For part-timers, reduce the hours per day or count them as a fraction of a full-time member in teamSize. Be conservative: a realistic sprint plan is always better than an overloaded one.
Facilitate retrospectives with your team?
Start for free →