Burndown charts and when to use them

Burndown charts are visual tools that help the team to track progress and see how they are performing compared to the planning. The chart also helps the team to track the amount of work and time remaining. You get your data for the burndown chart from the product backlog, the sprint planning and the amount of work done during the sprint. I will get into how to estimate the amount of work in later blogs. For now the focus is on how the burndown chart works.

The burndown chart shows the amount of work on the y-axis and the time remaining on the x-axis. It shows an ideal line and the line for actual delivery. The focus of the chart is to keep the remaining work on track. When the work is on track the orange line will be below or on the blue line. When the work is behind schedule the orange line will be above the blue line. 

Burndown chart

The pro's and cons of the burndown chart

When the work and scope of the project or sprint is highly predictable the burndown chart can be a powerful tool. But in projects with higher complexity it can become a drain on motivation.


  • Burndown charts are easy to understand and read
  • Since they are easy to understand they help to focus the team on the end result (the finish line)
  • The visual representation of the finish line can really help the team to stay motivated
  • The visual burndown chart helps in communicating project status to stakeholders


  • Most projects have to deal with a widening of their scope (scope creep). The burndown chart will show you are behind on your planning, but it will not show why.
  • When the estimates of the amount of work are too low, the burndown chart can become a reason for the team to get dejected.
  • Burndown charts tend to show a limited scope of work, for instance the work in one sprint or only work in the build or test phase. This leads to people losing overview of the total project.
  • The easy setup of the burndown chart can lead to the expectation that the progress will be very easy.


I would advise using the burndown chart when you are reaching the finish line of a project or sprint and the amount of work is highly predictable. When there is a months of time left in the project as whole, the burndown chart can be counterproductive. People know there is a lot of work which they do not see yet, this can lead to apprehension after the first couple of sprints.

When scope creep is (practically) a certainty or work estimates feel like gambles instead of actual estimates based on the facts i do not use the burndown chart. The scope creep is difficult to represent in the burndown chart.


Add Comment

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.