Build a sprint burndown chart from scope, elapsed days, and completed work, then compare ideal remaining work with current pace and required catch-up rate.
Last updated
What this burndown planner does Compare ideal sprint burndown, current progress, required remaining pace, and projected completion day so the team can see whether the sprint backlog is burning down fast enough.
Example sprint states
Sprint status
Sprint is on track
The current pace is 0 points per day above the required remaining pace. At 10 points per day, the projected finish is day 10.
Current pace
10 pts/day
Required remaining pace
10 pts/day
Ideal rate
10 pts/day
Projected finish
Day 10
Remaining at sprint end
0 pts
Variance today
0 pts
Ideal line vs current pace
IdealCurrent pace
The vertical marker shows day 5. Negative variance means the team is ahead of the ideal line; positive variance means work is above the ideal remaining line.
Burndown comparison sheet
Day
Ideal remaining
Projected remaining
Variance
0
100 pts
100 pts
0 pts
1
90 pts
90 pts
0 pts
2
80 pts
80 pts
0 pts
3
70 pts
70 pts
0 pts
4
60 pts
60 pts
0 pts
5
50 pts
50 pts
0 pts
6
40 pts
40 pts
0 pts
7
30 pts
30 pts
0 pts
8
20 pts
20 pts
0 pts
9
10 pts
10 pts
0 pts
10
0 pts
0 pts
0 pts
Catch-up and scope note At the current pace, the planned work burns down to zero within the sprint window.
Burndown chart calculator: compare ideal sprint pace with projected completion
A burndown chart calculator turns sprint scope, sprint length, and current completion pace into a simple planning view: how fast work should burn down, how fast it is actually burning down, and whether the team is likely to finish inside the planned sprint window if the same pace continues.
What a burndown chart is really showing
A burndown chart compares the work that should remain on each day of a sprint with the work likely to remain if the current pace continues. The ideal line is simply the original scope divided evenly across the sprint, while the projected line reflects the completion rate you enter.
That comparison is useful because teams rarely need another raw velocity number. They need to know whether remaining work is shrinking fast enough to finish on time, whether the current plan is realistic, and how large the gap is between the plan and the current pace.
Further reading
Atlassian — Burndown chart — Agile reference explaining what sprint burndown charts are for and how teams use them in practice.
How to read ideal remaining versus projected remaining
If projected remaining work stays close to the ideal line, the sprint is broadly on track. If projected remaining work stays above the ideal line, the team is burning down more slowly than planned and may need to reduce scope, remove blockers, or increase throughput to finish on time.
The comparison sheet is especially helpful because it shows the variance day by day instead of only reporting one end-state number. A sprint can be behind early and recover later, or it can look comfortable early and then drift off plan as blockers or unplanned work appear.
Worked example: 100 story points across a 10-day sprint
Suppose the sprint starts with 100 story points across 10 sprint days. The ideal burndown rate is 10 points per day. If the team is actually completing 8 points per day, the projected completion time becomes 12.5 days and about 20 points remain at the end of day 10.
That result does not prove the sprint will fail. It shows that, under the current pace, the plan finishes late. The next practical question is whether the team can raise throughput, cut scope, or accept a later finish. That is exactly the kind of conversation a burndown chart should support.
Current pace versus required remaining pace
A useful burndown chart calculator should not stop at the ideal line. Once you enter the current sprint day and completed work so far, the calculator can compare the team's actual burn rate with the pace needed across the remaining sprint days.
That required remaining pace is often the most actionable number in a sprint burndown chart. If the current pace is 6.4 points per day but the remaining backlog needs 13.6 points per day, the team has a concrete gap to discuss instead of a vague sense that the sprint is behind.
Using story points, tasks, or hours
Burndown charts are commonly built from story points, but the same planning logic can work with tasks, tickets, engineering days, or estimated hours if the team uses the unit consistently. Do not mix units inside the same sprint unless you first convert them into a single comparable measure.
For lightweight teams, completed tasks may be easier to maintain than story points. For product teams using Scrum, story points usually preserve the familiar agile planning language. The calculator labels the units generically so you can treat each point in the table as the unit your team actually tracks.
What to do when the burndown chart is behind
When projected remaining work sits above the ideal burndown line, first separate delivery problems from measurement problems. Check whether work was completed but not updated, whether scope was added mid-sprint, and whether blocked items are distorting the current pace.
If the data is accurate, the practical options are usually to remove blockers, reduce or defer scope, increase delivery focus, or reset expectations with stakeholders. The catch-up rate shows the scale of the recovery needed, but the decision still belongs in the sprint review, stand-up, or backlog refinement conversation.
Further reading
YouTrack — Burndown chart — Project-management documentation describing how burndown charts track remaining work and sprint progress.
Limits of a burndown chart calculator
This calculator assumes a steady completion pace, which is rarely how real sprint work behaves. Actual delivery often changes because of dependencies, review bottlenecks, production issues, interruptions, and scope changes. The result is therefore a planning baseline, not a forecast guarantee.
It also assumes that the work estimate itself is meaningful. If the story-point estimate is weak or the sprint backlog changes materially during the sprint, the projected completion day can become less useful. Recalculate whenever the scope or pace changes enough to change the decision.
Further reading
Asana — Burndown chart — Project-management guide on reading burndown charts and using them for sprint planning conversations.
Wikipedia — Burn down chart — General reference on burndown charts, sprint tracking, and agile reporting terminology.
Frequently asked questions
What is the difference between an ideal burndown line and the actual line?
The ideal line shows how much work would remain if progress were perfectly even across the sprint. The projected or actual line shows what remains at the completion pace you enter. The gap between them shows whether delivery is ahead of plan, roughly on plan, or behind plan.
Does a burndown chart guarantee that a sprint will finish on time?
No. It is a planning tool, not a guarantee. It assumes the current completion pace continues and that the total scope remains stable. Real sprint outcomes can still change if blockers appear, estimates change, or scope is added or removed.
Why can a sprint look behind early and still finish on time?
Because work is not always completed evenly. Teams may spend early days on setup, design, testing infrastructure, or dependency resolution, then complete a larger amount of work later. A single snapshot matters less than the ongoing trend and the team's ability to recover the gap.
Should I use burndown charts for projects outside Scrum?
You can, as long as the work can be expressed as a remaining backlog and a meaningful timebox. The concept works outside formal Scrum, but the estimate quality, update cadence, and interpretation still need to match the team's real delivery process.
What should I enter for current sprint day?
Enter the number of working days already elapsed in the sprint. For example, in a 10-working-day sprint at the end of day 5, enter 5. The calculator uses that value to compare completed work so far with the ideal remaining line for the same point in the sprint.
What is the required remaining pace in a burndown chart?
Required remaining pace is the amount of backlog that must be completed per remaining sprint day to finish on time. It is calculated from remaining work divided by remaining days, so it gives a direct recovery target when a sprint is behind.
Can I use tasks instead of story points?
Yes, if the tasks are similar enough for the count to be meaningful. Story points usually handle uneven task size better, while task counts can work for smaller teams or repeatable work. The key is to keep the unit consistent across total scope and completed work.
Why is my projected finish day later than the sprint length?
That means the current completion pace is not fast enough to burn the remaining backlog to zero before the sprint ends. Review whether scope changed, whether completed work has been recorded correctly, and whether the team can remove blockers or defer lower-priority items.
