Burndown Chart in Agile: Examples & How to Read [2026]
A. Togay Koralturk, Best-Selling PMP Author
Last updated on August 21, 2026
10 min read
In every sprint, the question that matters most is simple: will the team finish its committed work on time? A burndown chart answers it with a single picture — it plots the work remaining each day, and if the line is falling fast enough to reach zero by the sprint's last day, the team is on track. When it isn't, the team finds out mid-sprint, while there is still time to do something about it. This guide explains the burndown chart in full — what it is, an example, how to read the ideal and actual lines, how to create one, how it differs from a burnup chart, and how it is tested on the PMP and CAPM exams.
What is a burndown chart?
A burndown chart is a simple graph that shows how much work remains in a sprint or project over time. The vertical axis is the work remaining — usually in story points — and the horizontal axis is time, typically the days of a sprint. As the team completes work, the line "burns down" toward zero.
Its value is immediacy. Instead of reading a status report, anyone can look at the chart and see whether the team is on track to finish: a line heading smoothly toward zero by the last day is healthy, while a line lagging above where it should be is a warning. Burndown charts are a staple of Scrum and are often reviewed in the daily standup, because they turn "how are we doing?" into a picture the whole team already understands.
Anatomy of a burndown chart
Every burndown chart has two lines against the same axes. The ideal line (or guideline) is a straight diagonal from the total work at the start of the sprint down to zero at the end — the steady pace the team would need to finish exactly on time. The actual line is the real work remaining, plotted each day; it is jagged, because work is not completed at a perfectly even rate. Here is a sprint burndown with both:
In this example the sprint starts with 40 story points of work and runs ten days. The dashed ideal line shows the even pace needed to hit zero on day ten. The solid actual line sits above the ideal line the whole way, which means the team is consistently behind — more work remains than planned — and it ends with a few points still unfinished. That gap between the lines is the chart's core message: how far ahead of or behind the plan the team really is.
Ready to take the next step in project management?
200,000+ Learners Trust Our Instructors
How to read a burndown chart
Reading a burndown chart is mostly about comparing the actual line to the ideal line and noticing its shape. Each pattern tells you something specific:
| The actual line… | Means |
|---|---|
| Sits above the ideal line | Behind schedule — more work remains than planned |
| Sits below the ideal line | Ahead of schedule — work is being cleared faster than planned |
| Tracks the ideal line closely | On pace to finish on time |
| Goes flat (horizontal) | No work is being completed — often a blocker or impediment |
| Rises (goes up) | Work was added mid-sprint — scope grew |
The two patterns people miss are the flat line and the rising line. A flat actual line looks harmless but means nothing is getting to done — a signal to investigate an impediment in the daily standup. A rising line means scope was added after the sprint started, which a burndown chart shows only as an unexplained bump; distinguishing added scope from slow progress is exactly where a burnup chart does better, as we will see below.
Sprint vs. release burndown charts
Burndown charts come at two zoom levels. A sprint burndown chart tracks the work remaining within a single sprint, day by day, and is the one teams watch most closely. A release (or epic) burndown chart tracks the work remaining across a whole release or epic, sprint by sprint, giving a longer-range view of whether the larger goal is on track.
They work the same way and read the same way; only the scale changes. The sprint burndown answers "will we finish this sprint's work?", while the release burndown answers "will we finish the release on time?" Teams often keep both — the sprint version for day-to-day pace and the release version for the bigger commitment. The release burndown is also where velocity comes in, since the average work completed per sprint is what projects when the release will land.
How to create a burndown chart
Most agile tools generate burndown charts automatically, but knowing how they are built makes them easier to trust. The steps:
- Total the committed work. Sum the story points (or hours) the team committed to for the sprint — this is the starting height of the chart.
- Set the time axis. Mark each day of the sprint along the horizontal axis.
- Draw the ideal line. Connect the total work on day one to zero on the last day — a straight guideline.
- Plot the actual remaining work daily. At the end of each day, record how much work is still left and plot the point.
- Connect the actual points. The line joining them is the actual burndown, ready to compare against the ideal.
The one discipline that matters is measuring remaining work, not work done — and counting only items that fully meet the definition of done. A burndown built on optimistic "almost finished" estimates burns down smoothly on paper and then stalls at the end, when the not-quite-done work turns out not to be done at all.
Burndown vs. burnup chart
A burndown chart's biggest weakness is that it shows only one line of remaining work, so it cannot separate two very different events: the team completing work, and someone adding work. Both change the remaining total, but they mean opposite things. This is where a burnup chart helps.
A burnup chart plots two lines: the work completed (rising toward the goal) and the total scope (a line that moves up when scope is added). Because scope is its own line, a burnup chart makes scope changes obvious — you can see the total-scope line jump — whereas a burndown chart hides that jump as a smaller-than-expected drop. Burndown is simpler and perfect for a stable sprint; burnup is clearer when scope is likely to change, which is why many teams use both.
Benefits and limitations
Burndown charts are popular for good reasons, but they are not the whole story:
- Benefit — instantly readable: anyone can see sprint progress at a glance, which makes it ideal for standups and stakeholder updates.
- Benefit — early warning: a widening gap above the ideal line flags trouble while there is still time to act.
- Benefit — simple to produce: it needs only the remaining work and the day, and every agile tool generates it.
- Limitation — hides scope changes: it cannot distinguish added scope from slow progress, which a burnup chart can.
- Limitation — only as honest as the data: if "remaining work" is estimated optimistically or ignores the definition of done, the chart misleads.
The takeaway: a burndown chart is an excellent pace gauge for a sprint, best paired with a burnup chart or a cumulative flow diagram when scope and flow matter as much as pace.
Burndown charts on the PMP® and CAPM® Exams
Because agile and hybrid approaches are a large part of the PMP exam, the burndown chart appears as an agile tracking tool. You are expected to know that it plots work remaining against time, that the actual line above the ideal means behind schedule and below means ahead, and that a flat line signals a blocker while a rising line signals added scope. The distinction from a burnup chart — which separates scope from progress — is also fair game.
The harder questions are situational: a burndown shows the team will not finish the committed work, and you must choose the agile-correct response. That answer is almost never to extend the time-boxed sprint or push the team into overtime; it is to work with the Product Owner to adjust scope and still deliver a done increment on time. The CAPM tests the same reading skills a little more directly. Our PMP Complete Study Guide, the most complete on the market, covers the agile metrics and the mindset behind them so these scenarios are straightforward.
PMP Practice Question: Burndown Chart
Halfway through a two-week sprint, the burndown chart's actual line has stayed consistently above the ideal line, and the gap widens a little more each day. It is clear the team will not complete everything it committed to by the end of the sprint, and the increment is demonstrated to stakeholders on the last day.
What should the team do?
a) Reduce the time spent on testing and review for the remaining items, and restore the usual quality bar next sprint.
b) Work with the Product Owner now to move the lowest-priority committed items back to the product backlog.
c) Continue working in priority order and let any unfinished items carry over into the next sprint as spillover.
d) Ask to extend the sprint by three days so the full commitment can be met before the demonstration.
Correct answer: B.
Rationale: The chart's value is that it surfaces the problem at the midpoint, while there is still time to act on it, and the agile response protects the two things a sprint never trades away: the time-box and the quality of what ships. Descoping with the Product Owner keeps both intact, delivers a smaller but genuinely done increment on schedule, and lets the priority call be made by the person who owns value. The near-miss is passive spillover: carrying unfinished work forward quietly is common in practice, but it makes the shortfall a surprise at the demonstration and takes the scope decision away from the Product Owner, while cutting testing trades a schedule gap for a quality debt the burndown will never show, and stretching the sprint breaks the fixed cadence that makes velocity and forecasting meaningful. To drill this kind of sprint-monitoring judgment, work through our PMP practice exams or, at the entry level, our CAPM practice exams.
Ready to take the next step in project management?
200,000+ Learners Trust Our Instructors
Frequently asked questions
What is a burndown chart?
A burndown chart is a graph that tracks the work remaining in a sprint or project against time. Work remaining, usually in story points, is on the vertical axis, and time is on the horizontal axis. As the team completes work, the line burns down toward zero, giving an at-a-glance view of whether the team is on pace to finish.
How do you read a burndown chart?
Compare the actual line to the ideal line. If the actual line is above the ideal, the team is behind schedule; if below, it is ahead; if it tracks the ideal closely, it is on pace. A flat actual line means no work is being completed, often a blocker, and a rising line means scope was added to the sprint.
What is the difference between the ideal line and the actual line?
The ideal line is a straight guideline from the total committed work on day one down to zero on the last day, representing the even pace needed to finish exactly on time. The actual line is the real work remaining plotted each day. The gap between them shows how far ahead of or behind the plan the team really is.
What is the difference between a burndown and a burnup chart?
A burndown chart plots a single line of work remaining, so it cannot separate completed work from newly added scope. A burnup chart plots two lines — work completed and total scope — so scope changes are visible as movement in the scope line. Burndown is simpler; burnup is clearer when scope is likely to change.
What does a flat line on a burndown chart mean?
A flat, horizontal actual line means no work is being completed — the remaining work is not going down. It usually signals a blocker or impediment stopping items from reaching done, and it is a prompt to investigate in the daily standup. A flat line is easy to overlook because it does not spike, but it is a real warning sign.
Is the burndown chart on the PMP exam?
Yes. Agile and hybrid approaches are a large part of the PMP exam, and the burndown chart is a common agile tracking tool it tests. You should be able to read the ideal-versus-actual comparison, interpret flat and rising lines, distinguish it from a burnup chart, and choose the agile-correct response when a sprint will not finish its committed work.
Is the burndown chart on the CAPM exam?
Yes. The CAPM covers agile tracking tools including the burndown chart, usually a little more directly than the PMP — often defining it or asking you to read a simple ideal-versus-actual comparison. Because the CAPM is scenario-based, you should still be ready to interpret the chart in a short situation.
What Is Scrum? Roles, Events & Artifacts [2026]
Scrum is a lightweight agile framework for complex work. Its theory, the 3 roles, 5 events, and 3 artifacts, scrum vs. agile, benefits, and PMP exam tips.
Scrum Master: Role, Responsibilities & Skills [2026]
A scrum master is a servant leader who helps a team work effectively. Responsibilities, scrum master vs. project manager, skills, becoming one, and exam tips.
Product Owner: Role, Responsibilities & Skills [2026]
The product owner maximizes a product's value and owns the backlog. Responsibilities, product owner vs. scrum master, skills, how to become one, and exam tips.
