Sprint Velocity Calculator
Velocity Turns a Backlog Into a Date
A backlog of story points means nothing on its own — it only becomes a forecast once you know how many points a team actually finishes per sprint. Averaging recent sprints gives a working velocity figure, and dividing the remaining backlog by that velocity gives a defensible answer to "how many sprints left," instead of a guess pulled from optimism.
The Formula
Sprints Needed = Remaining Story Points / Average Velocity (rounded up)
Sprints needed is rounded up because a partially completed sprint still counts as a full sprint on the calendar.
Where This Is Useful
- Release forecasting — convert a backlog size directly into an estimated number of sprints, and from there a target date.
- Spotting velocity trends — a velocity that's drifting down sprint over sprint is an early signal worth investigating before it affects a release date.
- Setting realistic sprint commitments — a team's historical average is a better planning input than an aspirational number.
Worked Example
A team completed 18, 22, 20, 25, and 20 story points over five sprints, with 84 points remaining in the backlog:
| Story points per sprint | Average velocity | Remaining points | Sprints needed |
|---|---|---|---|
| 18, 22, 20, 25, 20 | 21 points/sprint | 84 | 4 sprints |
How to Use This Calculator
- Enter Story Points per Sprint as a comma-separated list of completed points from recent sprints (for example,
20,25,18). - Optionally enter Remaining Story Points — the backlog size still to be completed.
- Select Calculate to see the average velocity and, if a backlog size was entered, the number of sprints needed to clear it.
Related Calculations
Once velocity is known, check whether the team has the hours to sustain it with the Team Capacity Calculator, or track completion against the plan with the Task Completion Percentage Calculator.