Agile Charts: Read Progress at a Glance

A written status report arrives late, is read by few, and is usually worded to reassure rather than reveal. Agile charts fix all three with one move: they make the state of the work visible to anyone walking through the room. Instead of asking about progress and waiting, you look at the wall. The idea is not the chart type but moving information out of a tool one person owns into a space everyone shares — and that is where understanding these charts begins.

Definition and Foundation

The umbrella concept for these charts in the Eighth Edition is the information radiator: a visible, physical display that provides information to the rest of the organization, enabling timely knowledge sharing. They are also known as big visible charts. The guide gives them three specific properties:

• Placement — posted where people can see the information easily, rather than kept inside a scheduling or reporting tool.
• Updating — they should be easy to update and should be updated frequently.
• Nature — often "low tech and high touch," meaning manually maintained rather than electronically generated.

In lean environments information radiators go by another name: visual controls. These illustrate processes so actual performance can easily be compared against expected, showing a process through visual cues. They can exist at every level of information, from business value delivered to tasks that have started, and should be highly visible to anyone. The guide's examples include task boards and burn charts.

That grounding changes how the topic reads: a chart is not a miniature report but an instrument for comparing actual against expected, displayed in a shared space. Put it in a file only the manager opens and it loses the property by which it is defined. This is why "low tech and high touch" reads as a deliberate choice rather than a technical shortcoming: a board the team updates by hand stays alive and owned by them, while a tool that generates the chart automatically moves ownership to the system and distances the team from the number.

How It Works in Practice

The burndown chart

A graphical representation of the work remaining versus the time left in a timebox. What sits on its vertical axis is not confined to tasks: it can show the number of story points remaining, or the amount of risk exposure that has been reduced. That last option opens a use most people miss — a descending chart tracking the retreat of risk rather than the retreat of work. Its value is turning risk exposure, an abstract aggregate measure, into a curve whose direction reads at a glance: is exposure falling at the expected rate, or are responses being executed on paper without moving actual exposure.

The iteration burndown chart

This is the more specific form: it tracks the work remaining in the iteration backlog and is used to analyze variance with respect to an ideal burndown based on the work committed at iteration planning. A diagonal line representing the ideal burndown is drawn, daily actual remaining work is plotted beside it, and a trend line is then calculated to forecast completion based on the remaining work. The value of that trend line is that it predicts the likely variance at iteration completion, allowing appropriate action to be taken during the iteration rather than after it. The chart here is an early-intervention instrument, not a late-documentation one. The difference between the two forms is not cosmetic: the general chart shows work remaining against time left in any timebox, while the iteration chart ties it to the iteration backlog and the commitment made at iteration planning, giving a deviation specific, actionable meaning.

The burnup chart

A graphical representation of the work completed toward a milestone, used mostly within adaptive development approaches to show project progress over time. Its structure is two lines rather than one: the work to be completed runs as a straight line across the top, while the work completed starts at zero and rises. Hence its best-known advantage: a scope change appears as a rise in the upper line, which the burndown cannot show because it folds both variables into one. A burnup can also track work done against the work expected to be done.

What these charts show besides progress

Burn charts, both up and down, can show project team velocity — the rate at which deliverables are produced, validated, and accepted within a predefined interval. The guide names other visual charts alongside them, including an impediment list showing the impediment to getting work done, its severity, and the actions being taken to resolve it. There is also a composite form the guide labels a combined burn chart, putting the up and down views into one display. The guide's illustration of an information radiator shows three things together: work completed, work remaining, and risks — meaning a single radiator may carry more than one chart, and none of them is read in isolation from the rest.

On the Exam

The 2026 ECO places these charts in Domain II, Process, under Task 9 — evaluate project status — whose stated enablers include developing project metrics and analysis, assessing current progress, measuring, analyzing, and updating project metrics, and communicating project status. Burnup/burndown charts are named explicitly among the data analysis techniques for monitoring and controlling the schedule.

The dominant pattern is a scenario describing the shape of a chart and asking for the interpretation or the action. Four keys settle most of it:

• An upper line that rose on a burnup → a change in scope, not a slowdown in performance.
• A slope shallower than the ideal line mid-iteration → a signal to intervene now, not a note for the retrospective.
• A question on why burnup was chosen over burndown → because it separates scope from accomplishment.
• A chart showing risk exposure declining → a legitimate use stated in the guide, not a misreading.

What deceives is options offering management uses that contradict the purpose: comparing charts across teams, using a chart to appraise individuals, or waiting until the iteration ends before acting. All three run against the definition of the instrument, displayed for timely knowledge sharing and for comparing actual against expected within the team. Add to them an option proposing to adjust the chart so it looks better to stakeholders, which inverts the purpose outright: visual controls show a process through visual cues to make comparison easy, not to flatter it.

Detailed Mistakes

Reading a burndown as a measure of scope

The burndown folds two variables into one line: what was completed and what was added. A line that fails to descend may mean a stalled team, or a team completing work at exactly the rate work is added to it. The two call for opposite responses: the first demands surfacing the impediment, the second demands controlling the intake of new work. Anyone who needs to tell them apart needs the burnup, which shows the scope line separately from the completion line.

Settling for an electronic display

The guide specifies placement, cadence, and nature: visible where people see them easily, easy to update and updated frequently, often manually maintained rather than electronically generated. A dashboard nobody opens except in a weekly meeting achieves the form and misses the function, which is timely knowledge sharing.

Dropping the ideal burndown line

An iteration chart without an ideal line displays data with no reference. Its stated purpose is analyzing variance with respect to the ideal burndown based on the work committed at iteration planning. A chart showing only what remains tells you where you are and not where you should have been — and it is the second piece of information that decisions are built on. Beside the ideal line sits the trend line calculated on the remaining work, which converts the present variance into a forecast of the likely variance at iteration completion.

Where It Does Not Apply

Burn charts rest on a timebox and on a quantity of work that can be tracked up or down. Where there is no timebox — continuous flow work — the burndown loses its horizontal axis in the intended sense, and other visual controls named in the guide are used instead, such as task boards, which show at a glance the status of a task or the number of tasks in each stage. Where scope itself is the more important variable, the burndown is no substitute for the burnup. A final constraint runs against common practice: these are not primarily reporting instruments for senior management but instruments for comparing actual against expected, used by the people doing the work — once they become appraisal material, the behavior of whoever updates them changes before their performance does.