Halfway through a sprint, the question is not how much is done but whether the team will finish on time. A burndown compares the work remaining with an ideal line that falls steadily to zero. This calculator turns your numbers into a projection: the total duration at the current pace, the days of delay, the points behind the ideal line and the pace needed to finish on time.
How the calculation works
- Current pace = points completed ÷ days elapsed
- Projected duration = total scope ÷ current pace
- Ideal remaining = scope × (1 − days elapsed ÷ days planned)
- Points behind = actual remaining − ideal remaining
- Pace needed = points remaining ÷ days left
Example
A project has 120 points to deliver in 10 working days. After 6 days, 54 points are done, so the pace is 9 points per day. At that rate the work takes 13.3 days, 3.3 more than planned. The ideal burndown would have 48 points left, and the actual figure is 66, which is 18 points behind. To finish on time, the team needs 16.5 points per day, nearly twice the current pace.
Why it matters
A sprint review that comes too late cannot change anything. Checking the projection in the middle of the sprint leaves time to cut scope, ask for help or warn stakeholders. It also puts a number on the effort needed to recover, which helps the team judge whether the target is realistic.
Good to know
Work seldom burns down in a straight line: it is often slow at the beginning, when tasks are being started, and faster at the end. A linear projection is therefore pessimistic early in a sprint and optimistic late. Points are relative estimates, and the result is only as good as they are. This tool is for education.
Related tools
The sprint velocity calculator forecasts the number of sprints in a backlog, the team capacity calculator estimates what a sprint can hold, and the earned value calculator measures cost and schedule performance.