Sprint Burndown Calculator
Calculate remaining sprint work and team velocity from total story points, completed points and sprint count.
Inputs
Total story points planned for the sprint (or release).
Story points completed so far.
Number of sprints elapsed so far, used to compute velocity.
Working days left in the current sprint, for a daily burn rate needed.
Remaining Story Points
28points
Team Velocity
26.0points/sprint
Percent Complete
65.0%
Sprints Remaining at Current Velocity
1.08sprints
Required Daily Burn Rate
7.00points/day
Step by step
Remaining: total − completed
80 − 52
= 28 points
Velocity: completed ÷ sprints elapsed
52 ÷ 2
= 26.0 points/sprint
Sprints remaining at current velocity
28 ÷ 26.0
= 1.08 sprints
How it works
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)
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.
You might also need
- Team Capacity CalculatorCommonly used together
- Release Velocity CalculatorCommonly used together
- Lead Time for Changes CalculatorCommonly used together
- Platform Reliability Score CalculatorAlso in DevOps Metrics & DORA
- DevOps Maturity Score CalculatorAlso in DevOps Metrics & DORA
- Engineering Productivity CalculatorAlso in DevOps Metrics & DORA