What is a Sprint Burndown Chart and How to Use It?

Does anyone know why we learned to recite the periodic table of elements by memory? Do you even recall what “Sm” stands for?

Yes, there are a lot of useless things we learn through our lives and that’s how I used to feel about Burndown charts until recent weeks. Now that I know the true meaning and how useful they are, Burndown charts have become one of my most precious tools in Project Management.

So, what the heck is it?

A Burndown Chart is the graphic representation of your team’s velocity, it shows how quickly (or slowly) the team is working through the sprint’s user stories. So, it compares the total effort of the team against the amount of work for each iteration (sprint).

The Burndown chart should be shared regularly during the sprint so everyone can notice the progress and tell whether or not they will be able to complete the sprint and, of course, taking action to ensure this.

But, how should you read it?

First, you will need to recall about cartesian planes, x-axis and y-axis. For burndown charts this is what each one means:

• X-axis (Horizontal): This is the timeline, usually the days that have passed from the beginning of your sprint.
• Y-axis (Vertical): This is the work that needs to be done by using the remaining time estimate (that’s why we need to estimate tasks as most accurately as possible).

Start with good estimates

The product manager has given you a feature, and now you need to estimate. Don’t guesstimate, make your best to do it as accurately as possible. How? Try this:

• Don’t wait until grooming to read the documentation, read it in advance
• Ask a lot of questions
• Ask for designs, and if not, call out this may impact your estimate
• Clarify the scope/restrictions and make sure everyone is aware
• If you don’t feel sure, better not accept it

How do the burned tasks get burned?

The chart uses closed tasks for decreasing the remaining effort, but, what’s a closed task? This you will need to set it up. Most of the PM tools have a scrum board with configurable columns which you can locate task statuses (To Do, In Progress and Done). Whenever you move a task to that Done column, your Burndown chart will show less value for the remaining tasks. The goal is to get to zero at the end of your sprint.

Burndown charts need two key items from your sprint: estimates and Done tickets, this combination will set up your sprint for success or not. Make sure you estimate accurately with enough information, set up your PM tool to identify a really closed task, this way you can rely on your Burndown chart to tell the feasibility of completing your sprint on time.

Join 2000+ Founders and Developers crushing their businesses and careers with monthly advice. You can also follow us on LinkedIn , Twitter & Instagram!