How to Calculate the Number of Sprints From Backlog and Velocity

How to read your result

Sprint planning for a whole release starts with one question: how many sprints will the remaining backlog take? The answer is a division, but the quality of the answer depends on which numbers you divide and how you handle uncertainty. This guide shows the calculation, how to choose velocity, how to turn sprints into dates and what usually goes wrong. The sprint and velocity calculator does the arithmetic and the date maths for you.

Three inputs matter: the backlog, the velocity and the sprint length. The backlog is the total story points of work not yet done. Velocity is the number of story points the team finishes per sprint. Sprint length is usually one to four weeks.

The sprint count formulas

sprints needed = ⌈ backlog points ÷ velocity ⌉

duration in weeks = sprints needed × sprint length in weeks

end of last sprint = start date + duration in weeks × 7 days − 1 day

The ceiling brackets mean "round up": a team that needs 6.67 sprints needs 7, because the last sprint is only partly used but still takes the whole sprint length.

Worked examples

Each example uses numbers you can load into the calculator above; the results match the tool exactly.

Choosing velocity

Use the last three to six completed sprints. Drop sprints that were unusual, such as ones with a public holiday week or a major incident, but say that you did. The average gives the expected case; the minimum and maximum give the slow and fast cases. A team with a stable velocity will have a narrow range; a wide range tells you the date is uncertain and that is useful information in itself.

Velocity belongs to one team and one scale of story points. A new team has no velocity: run two or three sprints before projecting. If the team changes size, scale the velocity roughly in proportion and watch the first few sprints.

Accounting for scope growth

Real backlogs grow. If the team adds about 8 points of new work each sprint, the effective velocity against the original scope is the velocity minus the growth. With velocity 24 and growth 8, a 120-point backlog takes 120 ÷ 16 = 7.5, so 8 sprints, not 5. Track the average growth over recent sprints and subtract it from velocity when you project, or add it to the backlog.

For effort planned in hours rather than points, use the task time estimator. To forecast from progress against a plan use the estimated time remaining calculator.

Step by step: from backlog to release date

1. Total the backlog. Add the story points of all items not done: 120.
2. List recent velocities. For example 18, 22, 24, 26, 30. Minimum 18, mean 24, maximum 30.
3. Divide and round up for each velocity: 7, 5 and 4 sprints.
4. Convert to weeks. Multiply by the sprint length: 14, 10 and 8 weeks.
5. Convert to dates. Add the weeks to the start date and subtract one day to get the last day of the final sprint.

Assumptions, limits and common mistakes

Assumptions and limits

• The method assumes a fixed backlog and a stable team. Both change in practice.
• Story points are relative. The formula is only meaningful with the velocity of the same team, measured in the same points.
• Hardening sprints, release freezes and holidays are not included.

Common mistakes

• Using the best sprint as the forecast. It is the most optimistic case, not the likeliest.
• Rounding sprints down. A part-sprint still occupies a full sprint on the calendar.
• Forgetting scope growth. A growing backlog makes every projection too early.
• Mixing teams or point scales. Velocities are only comparable inside one team.

Frequently asked questions

More calculators