An iteration burndown chart is a key component in an agile project, particularly in scrum. It gives scrum teams and other stakeholders a quick view of whether the team is on track to complete the work for the current iteration. However, burndown charts have several limitations.
In this post, we’ll start by learning about iterations in agile software development. Then we’ll examine the role of the burndown chart, why we use it, and its advantages and disadvantages, and how you can overcome a burndown chart’s shortcomings with LinearB’s Project Delivery Tracker tool.
Table of Contents
- What Is an Iteration in Agile Development?
- What Role Does the Burndown Chart Play in Iterations?
- Project Delivery Tracker Gives You The Complete Picture
- Better Planning, Better Execution, Better Software
What Is an Iteration in Agile Development?
An iteration, also known as a sprint in scrum terminology, is a time-boxed period during which a set of specific tasks are to be completed. These tasks are generally related to the project under development and as much as possible they focus on delivering new features or functionality. The goal of an iteration is to complete the tasks within the set time frame so that the team can deliver the project to the customer on time.
The team, led by the project manager or scrum coordinator, then creates a plan of how they will complete the tasks and assigns each task to a specific team member. The team members work on their assigned tasks throughout the sprint and update the rest of the team on their progress during daily scrums. Iterations usually last two weeks, but they can be shorter or longer depending on the team’s needs.
What Role Does the Burndown Chart Play in Iterations?
The burndown chart is a graphical representation of the amount of work remaining in an iteration. The vertical axis of the burndown chart represents the amount of work remaining, with “work” typically being defined as story points. The horizontal axis represents the days in the iteration:
In grey, you have the ideal work remaining line. (As you can see, it consists of a set of straight lines so it’s unrealistic to expect that the team can stay on it exactly). The red line shows you the amount of work that has actually been completed.
In this chart, we see that progress in this sprint is slower than hoped for: The “actual” line is above the “ideal” line. And what if the “actual” line were below the “ideal” line? This would indicate that the project is ahead of schedule!
As the team is working during the sprint, the chart updates to record the work that they completed.
By the way, a burn up chart conveys the same information just slightly differently. You can read about the differences here.
Advantages of Burndown Charts
- A burndown chart provides a clear and succinct visual representation of progress and the amount of work left in a sprint.
- It helps identify potential risks or issues early on, allowing the team to course-correct as needed and avoid any last-minute surprises.
- Lastly, it can help improve estimation accuracy by tracking actual progress against estimated work remaining.
Disadvantages of Burndown Charts
On the other hand, there are also many potential disadvantages to using a burndown chart:
- A burndown chart can be time-consuming to create and maintain, especially when the team makes it manually using a tool like Excel.
- It can often be challenging to interpret and use for tracking progress because the y-axis is not labeled with specific task types or categories. As a result, it can be difficult to tell if the remaining work is all of one kind or spread across multiple types and how the work maps to particular epics, projects, and user stories.
- It doesn’t provide insight into why the work remaining has changed. This is critical information for teams trying to improve their estimation accuracy.
Project Delivery Tracker Gives You The Complete Picture
LinearB’s Project Delivery Tracker (PDT) is a project board designed specifically for development leads. It provides a complete picture of a project’s delivery status and detailed insights into its progress and the health of the team. It allows dev leaders to make informed decisions without interrupting their developers. All of this enables team leads to deliver higher quality software on time.
Let’s zoom in on some individual pieces of the Project Delivery Tracker to understand better how you can leverage LinearB to track your progress during a sprint.
Remember how we talked about how the burndown chart just tells you the amount of work that has been completed? The work breakdown metric in LinearB tells you what kind of work has been done.
- New work is completely new code that is providing new functionality.
- Refactor is old code that has been rewritten.
- Rework is new code that has been rewritten.
If your burndown chart is showing that your team’s progress is lagging, you can look at the work breakdown to see where your team is spending their time. For example, a high refactor rate suggests that they are paying off technical debt and a high rework rate suggests that they are having to fix recently-introduced bugs.
Cycle Time Breakdown
The burndown chart tells you whether you’re behind schedule, but it doesn’t tell you why. The cycle time breakdown metric in LinearB gives you instant insight into the bottlenecks slowing down your team. With just one click, you can see cycle times for individual issues so that your actions can be super targeted.
In the example above, coding and deploy times are healthy but review time is really slow. As a team lead, you now know that you need to address long review times, enabling you to start speeding up your team’s sprint burndown rate right away.
You could leverage LinearB’s WorkerB automation bot to send automated alerts to your team members to ensure that they stay on top of their reviews!
In addition to trying to increase the amount of work your team completes in a sprint, it’s also important to remember the other part of a burndown chart: the amount of work planned.
Time estimates are notoriously difficult in software development, and it’s especially difficult to predict the amount of work an entire development team can complete in a sprint. But LinearB’s planning accuracy can help, massively:
By looking across projects and sprints, you can see if your planning accuracy is consistently off and also why. A common cause is that unforeseen issues had to be tackled during the sprint, which you can see in the bright green “Added” portion of each of the bars in the chart.
If your team has to frequently take on unplanned work during a sprint, this suggests that there is technical debt in your codebase that is causing bugs or that requires time-consuming maintenance.
Better Planning, Better Execution, Better Software
Burndown charts are an essential tool for managing a software development iteration. But, as we’ve seen, they only give you a simple gauge of your team’s progress. As a team lead, you need to understand in more detail where your team is spending their time, why you’re not achieving more progress, and why your initial plans may have been off.
LinearB gives you all of that insight, and it does it through metrics and charts that you can parse at a glance. And not only is LinearB easy to use, it is easy to set up.
To learn just how easy it is to start using LinearB, and all the ways it can help you to refine your processes and improve your team’s quality and speed, set up a demo today.