Burn Up vs Burn Down Charts

A hand points to a graph on a piece of paper sitting on a wood table. The graph is similar to what a burn up chart looks like as this article is about burn up and burn down charts used in Agile and Scrum methodologies for project planning.

Burn up and burn down charts are visual representations of progress in the scope of a project, showing the amount of effort expended against expected output or set goals. Burn charts are common components of Agile and Scrum project management ideologies and are used to visualize progress for team leaders, stakeholders, and even team personnel.

This article looks at burn up and burn down charts, how they work, and how they differ from each other for organizations that want to visualize their objectives and project progress.

What Is a Burn Up Chart?

Burn up charts are visual representations that track work completed to date against the total work planned for a set time (e.g., project, sprint, or quarter). The total work planned often appears as a straight line—known as the scope—and serves as the team’s ultimate objective.

Beneath the scope line, burn up charts use two lines to represent progress over the course of the project. As seen below, the first line (red) represents “to dos” and goals for the project. It equally splits the effort across sprints to meet the project scope, while the second line (green) shows the actual progress made during each sprint of the project.

A graph showing a burn up chart as described above..
A graphic representation of a burn up chart. Source: EPMC.
Read more: Best Project Management Software & Tools | TechRepublic

What Is a Burn Down Chart?

Burn down charts are visual representations of work remaining against work completed in a downward-sloping graph. Unlike burn up charts, burn down charts do not have a scope line because the X-axis serves as the ultimate destination for project completion.

Otherwise, the first line (red) shows a similar expected progress line that equally divides effort (also known as “points” within Agile planning) across the length of the project. The second line (green) likewise indicates actual progress per sprint to visualize gaps between expected and real progress.

A graph showing a burn down chart as described above.
A graphic representation of a burn down chart. Source: EPMC.
Also read: Agile Principles: What They Are and Why They Matter | Developer.com

How Do Burn Charts Work?

Before jumping into the work, project managers and team leads determine the points needed to complete a project. Managers can then set a scope (or Y-axis starting point for burn down charts) and an expected progress line by sprint to track progress once a project starts.

Burn up and burn down charts can give teams visibility into progress or lack thereof to inform team planning and changes. As seen in the examples above, teams behind schedule in earlier sprints can make adjustments to get ahead of schedule until project completion.

For burn up charts, note the scope line (blue) shows that the objective changed during the project. Whether a client is asking for additional services or a new feature for a software update, project scopes can vary over time. Burn up charts offer the flexibility to show this variability. 

While the expected progress line (red) is often a straight line pointed toward the end goal, this can also be a flexible line to show which sprints will require the most effort.

Burn Up Charts vs. Burn Down Charts

Burn up and burn down charts allow teams to track progress and adjust workflows as necessary to complete the project. While burn up charts use an upward slope and burn down charts use a downward slope, both charts contain a Y-axis to represent points or effort while the X-axis represents some degree of time.

Because of their similarities, whether to use a burn up or burn down chart is the personal preference of the team implementing the project management tool.

Moving up from zero or down from zero is the core visual appeal of each, but the burn up chart’s use of a scope line offers more flexibility for teams with regularly changing project expectations. Similarly, teams with a constant point expectation can use a burn down chart without worrying about plotting a scope.

Recent Coverage

Sam Ingalls
Sam Ingalls
Sam Ingalls is an award-winning writer and researcher covering enterprise technology, cybersecurity, data centers, and IT trends, for eSecurity Planet, TechRepublic, ServerWatch, Webopedia, and Channel Insider.

Related Articles

Project Management Sprint

More and more businesses are adopting an agile approach to achieving their goals, from operations to IT to marketing. The project management sprint system...

Change Order

When changes need to be made to a project after the project has already been approved by the client, a professional service firm needs...

Smartsheet

Founded in 2005, Smartsheet is a leading cloud-based project management solution that offers robust features, workflows, and automations to help teams of all sizes...

Rally Software (formerly Agile Central)

What is Rally Software? Rally Software, previously known as CA Agile Central, is a leading agile software development SaaS platform. It allows teams and organizations...

ScalaHosting

ScalaHosting is a leading managed hosting provider that offers secure, scalable, and affordable...

HRIS

Human resources information system (HRIS) solutions help businesses manage multiple facets of their...

Best Managed Service Providers...

In today's business world, managed services are more critical than ever. They can...