a·gen·tic a·gil·i·ty

What’s in a burndown?

Explains burndown charts in Scrum, their purpose, common issues, and compares tracking by hours, story points, and acceptance tests to improve team progress visibility.

Published on
4 minute read
Image
https://nkdagility.com/resources/SdYtGr9X2KV
Subscribe

I was recently in Park City, Utah to teach the Professional Scrum Foundations course and i just got an email from one of the students. As I want to help everyone I will answer here:

If I recall from our training, you suggested teams could burn down their sprints using points or hours.  In your view is there a “better” answer in your opinion (pros/cons)?
-Pete

The first thing that we want to do is define explicitly what a burndown represents and the reason that we are creating one; i.e. what actions might we want to take. Only then can we decide what we want to measure and which is best for us.

What is a burndown?

During Sprint Planning the Development Team forecast what work it thinks it could do (selected a number of PBI’s from the Product Backlog) and created a Plan to complete them. This is known as the Sprint Backlog and it should have some measure of Remaining Work that allows the Development Team to see what they have left to do. As the Sprint Backlog (the Plan to complete the forecast PBI’s) evolves as more is known over the course of the Sprint the Remaining Work can vary and we need a way of visualizing trends so that the Development Team can take the necessary action.

A burndown is a visual representation of the Remaining Work in the Sprint Backlog as it varies over time.

What might we find?

So in order to identify actions we need to look at some things we might identify as a problem.

These are just some ideas of what might be found and are not indicative of all possible options and there are other lists of Bad Smells of the Sprint Backlog that you can find online.

Let me reiterate, that along with the Three Questions that are part of the Daily Scrum a Burndown is just a tool to help elicit communication and understanding within the Development Team. It is not a whip for a Project Manager to crack.

What burndown is right?

So to answer the question of wither to burn down Story Points, Hours or even Test Cases I would argue that we need them all! I want to see if my tasks are on track, but I also want to make sure that I am delivering Stories as well.

The Hours Burndown

This burndown is good for helping the Development Team identify how much work is remaining in the Sprint and if they are likely to still be able to meet their Sprint Goal.

The Story Point Burndown

Good for allowing the Development Team to see if they are actually getting things Done, verses completing all of the Tasks.

The Acceptance Tests Burndown

Also a good indicator of what is going on from a delivery perspective. If you are on track for Hours, and Story Points but you have only completed 50% of your Acceptance Tests and you have 2 days left on your Sprint, what does that tell you about your quality.

Conclusion

You will need to experiment with your Scrum Teams to see which burndown is right for you, but I would suggest that you want to be able to plot all of them so that your Development Team’s have all of the relevant information for their Daily Scrum to  help them identify any issues as early as possible.

Software Development Agile Planning Product Delivery Professional Scrum Agile Frameworks … 2 more Pragmatic Thinking Team Performance
Subscribe

Related blog

No related videos found.

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients​

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.​

ALS Life Sciences Logo

ALS Life Sciences

YearUp.org Logo

YearUp.org

Hubtel Ghana Logo

Hubtel Ghana

Genus Breeding Ltd Logo

Genus Breeding Ltd

Capita Secure Information Solutions Ltd Logo

Capita Secure Information Solutions Ltd

Workday Logo

Workday

Higher Education Statistics Agency Logo

Higher Education Statistics Agency

Cognizant Microsoft Business Group (MBG) Logo

Cognizant Microsoft Business Group (MBG)

Bistech Logo

Bistech

Ericson Logo

Ericson

Kongsberg Maritime Logo

Kongsberg Maritime

Boeing Logo

Boeing

Lean SA Logo

Lean SA

Qualco Logo

Qualco

Freadom Logo

Freadom

Emerson Process Management Logo

Emerson Process Management

DFDS Logo

DFDS

NIT A/S

Royal Air Force Logo

Royal Air Force

New Hampshire Supreme Court Logo

New Hampshire Supreme Court

Nottingham County Council Logo

Nottingham County Council

Washington Department of Transport Logo

Washington Department of Transport

Washington Department of Enterprise Services Logo

Washington Department of Enterprise Services

Ghana Police Service Logo

Ghana Police Service

Emerson Process Management Logo

Emerson Process Management

Xceptor - Process and Data Automation Logo

Xceptor - Process and Data Automation

Schlumberger Logo

Schlumberger

Workday Logo

Workday

Alignment Healthcare Logo

Alignment Healthcare

DFDS Logo

DFDS