A burndown chart calculator checks whether a team will finish its work in time. Enter the length of the sprint, the total story points, the days that have passed and the points that are done, and the calculator gives the current burndown speed, the speed that is needed to finish, and the points that remain. It runs in your browser and nothing you enter is sent anywhere.
How to use the burndown chart calculator
- Enter the sprint duration in working days and the total story points.
- Enter the days since the sprint started.
- Enter the story points burnt so far.
- Press Check the sprint.
What a burndown chart is
A burndown chart is a graphical representation of work left to do versus time [1]. Teams that work in sprints, which are short, fixed periods of work, use it to see whether the work that remains is falling to zero by the end of the sprint. Remaining work can be measured in time or in story points, a sort of arbitrary unit [1]. The ideal line is a straight line that connects the start point to the end point [1].
The two speeds
The calculator uses two formulas, which are our own working. The current burndown speed is the story points burnt divided by the days since the sprint started. The required burndown speed is the total story points minus the points burnt, divided by the sprint duration minus the days since the sprint started. The first tells you how fast the team has been going, and the second how fast it must go from now on to finish on time. If the current speed is at least as big as the required speed, the team is on track, and the calculator says so.
Worked example
Take a team with a two-week sprint of 10 working days and 35 story points. After 5 days, the team has burnt 15 points. The current speed is 15 divided by 5, which is 3 points a day. The required speed is 35 minus 15, which is 20, divided by 10 minus 5, which is 5, so 4 points a day. The team has to go faster than it has gone so far, so it is behind, and the calculator shows a message to say so.
Working days
The calculator assumes working days, so a sprint of two weeks is 10 days. Count only the days that the team works, and use the same days for the duration and for the days that have passed. If the team has a holiday, take it out of both figures. Story points cannot be negative, and the calculator checks that the points burnt are not more than the total.
What to do about it
If the required speed is much more than the current speed, the team can move some tasks to the next sprint, ask for more help, or find out what is slowing the work down. If the current speed is more than the required speed, the team may have room to take on more. The numbers are a prompt for a conversation, and the team knows best what is going on.
What it does not do
Velocity is a measure of the productivity rate within a predefined interval [1], and the average speed here is a simple version of that. The calculator gives no finish date. It also gives only an overall average, and does not show the day-by-day line of a chart. If you want to draw the chart, record the points remaining at the end of each day and plot them, with a straight ideal line from the total at the start to zero at the end.
Reading the result
The calculator shows the current speed and the required speed, both in story points a day, the points that remain and a message that says whether the team is on track. The message compares the two speeds: if the current speed is at least the required speed, then a team that keeps going at the same pace will finish in time. It is a simple comparison and does not know about problems that may come up.
Drawing the chart
To draw a burndown chart, make a table with a row for each day of the sprint. In the first column, write the day, and in the second, write the story points that remain at the end of that day. Plot the days along the bottom and the points up the side. Draw a straight line from the total points at the start to zero at the end, which is the ideal line. If the real line is above the ideal line, the team is behind, and if it is below, the team is ahead.
Why the line is not straight
Real work rarely goes at a steady pace. Teams often finish few tasks at the start of a sprint, while tasks are being understood, and more at the end. A flat line for several days may mean that tasks are too big, or are blocked. A sudden drop may mean that several tasks were finished together. Look at the shape as well as at the two speeds, and talk about it at the team meeting.
Story points
Story points are a team's own way of sizing tasks, and one team's point is not the same as another's. Do not compare speeds between teams. Compare a team's speed with its own past sprints, and use that to plan how much work to take into the next sprint.
Common mistakes
- Counting calendar days. Use working days.
- Counting started tasks as done. Burn points only when a task is finished.
- Changing the total during the sprint. Keep the original total for the comparison.
- Reading the speed as a promise. Work is rarely even from day to day.
What next
Use this often? Add Burndown Cha to your Home screen.
Frequently asked questions
What is a burndown chart calculator?
A tool that compares the speed a team has worked at in a sprint with the speed it needs to finish.
How do you calculate the current burndown speed?
Story points burnt divided by the days since the sprint started.
How do you calculate the required burndown speed?
(Total story points − points burnt) ÷ (sprint duration − days since the start).
What is the answer for a 10 day sprint of 35 points after 5 days and 15 points?
The current speed is 3 points a day and the required speed is 4 points a day, so the team is behind.
Does it predict the finish date?
No. It compares two average speeds and gives no finish date.
Sources
Was this tool helpful?
What went wrong?
We only receive the reason you pick, never what you typed into the tool.
Thanks for your feedback.