Skip to content
Omnikalc

How many sprints will it take to finish the backlog?

Enter the points done in your last three sprints and the points left in the backlog: get the average velocity, the number of sprints and a best and worst case.

Updated on
Your inputs

Value out of range

Value out of range

Value out of range

Value out of range

Value out of range

Results

Average velocity (points per sprint)

37.7

Velocity is fairly stable, which makes the forecast more reliable
Sprints to finish the backlog (average velocity)
7
Sprints if the team repeats its best sprint
7
Sprints if the team repeats its worst sprint
8
Weeks to finish (average velocity)
14

Planning a release needs an answer to a simple question: how many sprints are left? A team’s velocity, the points it finishes in each sprint, gives a data-based answer. This calculator averages your last three sprints, then divides the remaining backlog by that velocity, and also shows the best and worst cases, so that the forecast comes as a range and not as a promise.

How the calculation works

  • Average velocity = sum of the last three sprints ÷ 3
  • Sprints to finish = backlog ÷ average velocity, rounded up
  • Best case = backlog ÷ best sprint, rounded up
  • Worst case = backlog ÷ weakest sprint, rounded up
  • Weeks = sprints × sprint length

Example

A team finished 34, 41 and 38 points in its last three two-week sprints, so its average velocity is 37.7 points. With 260 points left in the backlog, it needs 7 sprints, or 14 weeks. If the team repeats its best sprint, it still needs 7 sprints; if it repeats its weakest, it needs 8. The velocity varies by 18%, which is acceptable.

Why it matters

Forecasts based on measured velocity are more reliable than estimates made on a whiteboard, and they respond to what the team actually delivers. The range gives product owners and stakeholders an honest view of the schedule risk, so they can trade scope against dates.

Good to know

A forecast assumes that the backlog does not grow: new requests, rework and changes in scope extend the end date. Velocity is team-specific and depends on the estimation scale, so a change in team size or in how points are assigned breaks the comparison. Treat the result as a planning aid, not a commitment. This tool is for education.

The burndown forecast calculator checks progress within a sprint, the team capacity calculator estimates what a sprint can hold, and the earned value calculator tracks cost and schedule performance.

Frequently asked questions

What is sprint velocity?

The amount of work, usually in story points, that a team completes in a sprint. It is measured from past sprints and used to forecast how much a team can take on.

How many sprints should I average?

Three to six recent sprints are a good compromise: enough to smooth out one-off swings, and few enough to reflect the team as it is today. Ignore sprints that were disrupted by holidays or a change in team size.

Is velocity a measure of productivity?

No. Points are relative estimates of each team, so velocities should not be compared between teams or used as targets. Pushing velocity up as a goal tends to inflate estimates rather than deliver more.

Why show a best and worst case?

Because velocity varies. Showing the range of sprints, rather than a single date, conveys the uncertainty in the forecast. The best case assumes every sprint matches the best of the last three, the worst case the weakest.

Was this calculator helpful?

Thanks for your feedback!

Results are estimates provided for information purposes. They do not replace professional advice.