Burndown Chart Calculator

Burndown Chart Calculator

Free online burndown chart calculator to measure remaining sprint work, compare actual progress with the ideal burndown pace, and estimate whether the team is ahead or behind plan. This calculator is useful for scrum teams, project managers, product owners, agile coaches, and developers who want a simple way to review sprint progress without building a full chart manually. It works well for story points, hours, tasks, tickets, or any other unit used to track sprint scope.

A burndown view starts with total scope at the beginning of the sprint and then reduces that amount as work is completed. The ideal burndown line shows how much work should remain if progress is perfectly even across the sprint. The actual remaining work shows the true amount still open based on current completion. Comparing the two helps teams quickly understand whether they are on track, ahead, or behind. This calculator turns those ideas into fast numbers you can use in daily standups, sprint reviews, or planning meetings.

The formula of burndown chart

Remaining work = Total sprint scope – Completed work

Ideal remaining work = Total sprint scope – ((Elapsed sprint days / Total sprint days) x Total sprint scope)

Completion rate = (Completed work / Total sprint scope) x 100

Variance from ideal = Remaining work – Ideal remaining work

Here total sprint scope means the full amount of planned sprint work, completed work means the amount already finished, elapsed sprint days means the number of days already passed in the sprint, and total sprint days means the full sprint duration. A positive variance from ideal means more work remains than planned, which usually means the sprint is behind the ideal pace. A negative variance means the team is ahead of the ideal pace.

Solved Example

Example 1: Find the burndown values if total sprint scope is 100 story points, completed work is 45 points, elapsed sprint days are 5, and total sprint days are 10.

Solve: Remaining work = 100 – 45 = 55 points

Ideal remaining work = 100 – ((5 / 10) x 100) = 100 – 50 = 50 points

Completion rate = (45 / 100) x 100 = 45%

Variance from ideal = 55 – 50 = 5 points

This means the sprint is 5 points behind the ideal pace.

Example 2: Find the result if total scope is 80 tasks, completed work is 50 tasks, elapsed days are 6, and total sprint days are 10.

Solve: Remaining work = 80 – 50 = 30 tasks

Ideal remaining work = 80 – ((6 / 10) x 80) = 80 – 48 = 32 tasks

Completion rate = (50 / 80) x 100 = 62.5%

Variance from ideal = 30 – 32 = -2 tasks

This means the sprint is 2 tasks ahead of the ideal pace.

Example 3: Find the result if total scope is 120 hours, completed work is 36 hours, elapsed days are 3, and total sprint days are 10.

Solve: Remaining work = 120 – 36 = 84 hours

Ideal remaining work = 120 – ((3 / 10) x 120) = 120 – 36 = 84 hours

Completion rate = (36 / 120) x 100 = 30%

Variance from ideal = 84 – 84 = 0 hours

This means the sprint is exactly on the ideal pace.

Table of burndown chart calculator

How to use this burndown chart calculator

Enter the total sprint scope in the proper input field. After that, enter the amount of completed work so far. Then enter the elapsed sprint days and the total sprint days. Finally, click the calculate button. The calculator will show remaining work, ideal remaining work, completion rate, and variance from ideal in the result box. You can use story points, hours, tasks, or tickets, but all work values should use the same unit.

This calculator is useful during daily standups, sprint checkpoints, and end-of-sprint reviews. If remaining work is higher than the ideal remaining work, the team may be behind schedule and might need to adjust scope, remove blockers, or change delivery focus. If remaining work is lower than ideal, the team may be ahead of schedule. Tracking the variance helps teams understand whether the sprint is moving at the right pace without needing a complex reporting tool.

When using the result, remember that sprint work is rarely burned down in a perfectly straight line. Teams may complete large chunks of work late in the sprint, and scope can change after planning. This calculator is best used as a simple progress indicator, not as a strict judgment tool. It gives a quick numerical view that supports sprint planning, agile reporting, delivery tracking, and better communication about progress and risk.