Sprint Burndown Calculator

Calculate remaining sprint work and projected completion based on burndown rate.

About Sprint Burndown Calculator

Sprint burndown tracks work remaining against the team's demonstrated pace: remaining = total_points − completed_points, velocity = completed_points ÷ sprints_elapsed. Projecting remaining work forward at the current velocity estimates how many more sprints are needed at the current pace, while the required daily burn rate shows what pace is needed to finish the current sprint's remaining work in the days left.

Formula

ideal_remaining = total_points × (1 - elapsed_days / sprint_days)

total_points: Total story points committed for the sprint
elapsed_days: Days elapsed in the sprint
sprint_days: Total sprint duration (days)

Worked example

With the default values below, Sprint Burndown Calculator returns Remaining Story Points of 28. Change any input above and every figure here is recalculated in your browser.

Inputs used

Total Story Pointsaccepts 0–1,000,000 points: 80 points
Completed Story Pointsaccepts 0–1,000,000 points: 52 points
Sprints Elapsedaccepts 0.1–1,000 sprints: 2 sprints
Days Remaining in Current Sprintaccepts 0–365 days: 4 days

Results

Remaining Story Points: 28 points
Team Velocity: 26.0 points/sprint
Percent Complete: 65.0%
Sprints Remaining at Current Velocity: 1.08 sprints
Required Daily Burn Rate: 7.00 points/day

Step by step

1Remaining: total − completed= 28 points
2Velocity: completed ÷ sprints elapsed= 26.0 points/sprint
3Sprints remaining at current velocity= 1.08 sprints

Assumptions and limits

The result is derived only from the 4 inputs listed above. Anything not among them is not part of the calculation.
In particular, this calculator does not take inflation, tax, fees or charges or compounding frequency into account.
Figures are rounded for display to 2 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.

How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.

Frequently Asked Questions

Why measure velocity across multiple sprints instead of just the current one?

Velocity from a single sprint can be skewed by holidays, one-off distractions, or estimation variance; averaging completed points across several recent sprints gives a more stable, representative pace for forecasting.

What does it mean if the required daily burn rate greatly exceeds current velocity?

It signals the current sprint's remaining work likely won't be finished in the time left at the team's historical pace — either the scope needs to be trimmed, more capacity needs to be added, or the sprint goal needs to be renegotiated.

Should story points be comparable across different teams?

No — story points are a relative, team-specific estimation unit; comparing velocity in points directly between teams is a common anti-pattern since each team's point scale is calibrated differently.

How does burndown differ from burnup?

A burndown chart shows remaining work trending toward zero over time; a burnup chart shows completed work trending toward the total scope line — burnup has the advantage of visibly showing scope changes (the total line moving) that burndown can obscure.