Sprint velocity calculator
Enter the points your team finished in recent sprints to get the average, median and range, and a best, likely and worst-case forecast of how many sprints the remaining backlog needs.
Free · Runs in your browser · Updated 26 September 2026
Sprint velocity calculator
Oldest first. Separate with spaces, commas or new lines.
Capacity of the coming sprints compared with the past ones. 80 if people will be away.
YYYY-MM-DD. Adds finish dates to the forecast.
- Average
- 21.45 sprints
- Median
- 21
- Range
- 18 to 25
- Spread
- ± 2.7Sample standard deviation.
| Scenario | Velocity used | Sprints | Finish |
|---|---|---|---|
| Best casefastest sprint | 25 | 5 | — |
| Likelyaverage of all sprints | 21.4 | 6 | — |
| Worst caseslowest sprint | 18 | 7 | — |
| Recent trendaverage of the last three | 22.7 | 6 | — |
Whole sprints, rounded up. This is arithmetic on past sprints, not a promise: scope changes and unplanned work move it.
Average velocity 21.4. Likely 6 sprints remaining.
How it works
Past sprints, divided into the work left.
Forecast
sprints needed = ⌈ remaining points ÷ velocity ⌉
The calculator takes the remaining backlog and divides it by a velocity, rounding up to whole sprints, because a sprint that is only partly needed is still a sprint. It does this three times: with your fastest sprint (best case), the average (likely) and your slowest sprint (worst case). With three or more sprints it also shows the average of the latest three, which follows a recent change in pace.
- Team availability scales the velocity for the coming sprints. Enter 80 if people will be away for a fifth of the time; enter more than 100 only if you are adding people who are already productive.
- The spread is the sample standard deviation of your sprints. A large spread relative to the average means the forecast is loose.
- Add a start date to turn sprint counts into finish dates, using the sprint length in weeks.
Limits
A forecast is arithmetic, not a promise.
- It assumes the remaining work is estimated on the same scale as the past work. If the backlog was estimated differently, the result is meaningless.
- It assumes the scope does not grow. Most real backlogs do, so re-run it every sprint with the current remaining points.
- Unplanned work, dependencies on other teams and holidays are not modelled, except through the availability figure.
- Points measure relative effort, not time. Do not turn velocity into a target: teams that are measured on it tend to inflate their estimates.
FAQ
Questions people ask first.
- What is sprint velocity?
- The amount of work a team finishes in one sprint, usually counted in story points. It describes what the team actually completed in the past, which is why it is used to estimate how long the remaining work will take.
- How many sprints do I need before the average means anything?
- The calculator works from one, but one sprint is an anecdote. Three or more give a steadier average, and the spread shows how much the numbers move. If your team or process changed recently, use only the sprints since the change.
- Should I use the average or the median?
- The average uses every sprint. The median ignores how extreme the highest and lowest are, so one holiday-shortened sprint moves it less. When they differ a lot, look at the individual sprints before trusting either.
- Do unfinished stories count?
- Most teams count a story only when it is completely done, and carry the rest into the next sprint. Counting half-finished work inflates velocity and makes the forecast optimistic.
- Can I compare velocity between teams?
- No. Story points are relative to each team’s own scale, so 30 points from one team and 30 from another are not the same amount of work. Velocity is a planning tool for one team, not a productivity score.
From the team behind the tools
Building a product?
Daniotech builds web, mobile and real-time software for startups and teams. Tell us what you are making and who it is for.