Sprint Velocity & Capacity Calculator
Plan your next Agile sprint: compute average and median team velocity from past sprints, work out team capacity in focused hours, and get a recommended story-point commitment range adjusted for time off and focus factor.
Input
Team & Sprint
Working days in one sprint (e.g. 10 for a 2-week sprint)
Net working hours per person per day (excluding breaks, meetings)
Velocity History
Comma or space-separated story points from recent sprints
Adjustments
Total person-days lost to PTO, holidays, sickness across the team this sprint
Share of working time spent on sprint work (typical range 60-85%)
Used to convert story points to hours in the results
Output
Capacity Summary
| Metric | Value |
|---|---|
| No data yet | |
Hours Breakdown
| Item | Hours |
|---|---|
| No data yet | |
Guides
Planning an Agile or Scrum sprint means answering one hard question: how much work can the team realistically commit to? This calculator turns your past sprint data and this sprint's availability into a defensible story-point commitment range — no spreadsheets required, and everything runs right in your browser.
What it does
The tool works out three things at once:
- Team velocity — the average and median story points your team completed across recent sprints, plus the historical min-to-max range.
- Team capacity — the focused hours the team actually has this sprint, after subtracting time off and applying a focus factor.
- Recommended commitment — a conservative-to-stretch story-point range for the upcoming sprint, scaled for current availability and bounded by your best historical sprint.
How to use it
- Enter your team size, sprint length in working days, and the productive hours per person per day (net of breaks and standing meetings).
- Paste your completed story points from the last few sprints, comma- or space-separated (e.g.
42, 38, 45, 40, 43). - Add any team time-off days (PTO, holidays, sickness) as person-days lost this sprint.
- Set your focus factor — the share of working time genuinely spent on sprint work, typically 60–85%.
- Optionally set hours per story point to see capacity expressed in equivalent points.
Results update live as you type. The Capacity Summary table shows average/median velocity, the velocity range, the recommended commitment range, and an availability- and focus-adjusted capacity figure. The Hours Breakdown table walks from nominal team hours down to net focused hours and their story-point equivalent.
How the numbers are calculated
- Nominal hours = team size × sprint days × hours per person per day.
- Available hours = nominal hours − (time-off days × hours per day).
- Net focused hours = available hours × focus factor.
- Availability ratio = (team person-days − time-off days) ÷ team person-days.
- Adjusted capacity takes your average velocity and scales it by the availability ratio and by (current focus ÷ an 80% baseline), since your historical velocity already bakes in a typical focus level.
- Recommended commitment brackets the average and median velocity, scaled by availability, with the stretch end capped at your highest recorded sprint so the target stays grounded.
Which velocity number should I commit to?
Median velocity is often the safer planning anchor than the average — a single unusually big or small sprint skews the mean but barely moves the median. Use the recommended commitment range as guardrails: commit near the conservative end when the sprint has a lot of unknowns, and toward the stretch end for a well-understood backlog.
Why does time off matter so much?
Capacity is roughly linear in available hours. A few days of PTO across the team can quietly remove a meaningful slice of a sprint, which is why the tool folds time-off days into both the hours breakdown and the availability-adjusted commitment.
Privacy
All calculations happen locally in your browser. Your team's velocity history and capacity numbers are never uploaded or stored anywhere.