Burndown Chart

Run two-week cycles for a while and the same problem shows up: you only find out what finished once the cycle is over. In the middle, everyone knows where their own work stands and nobody knows where the team stands.

That gap showed up in daily scrum, the fifteen-minute meeting where a team shares progress and blockers. One person after another says "I worked on the checkout screen yesterday and I'm still on it today," and after ten days of the same sentence nobody can tell whether the team moved at all. "Almost done" sounds identical on day nine and on day one.

So everything landed in the last two days. Someone would count the remaining items on a Thursday, discover the cycle wasn't going to close, and by then it was too late to cut scope or pull in help.

A burndown chart exists to move that judgment forward to every day. Instead of describing progress, the team plots the amount of work left and connects the dots. Where the line sits says whether the team is ahead or behind without anyone having to explain.

Five things go on the page.

1. The horizontal axis — the days of the cycle. It runs from the first day of the sprint to the last, usually with weekends and holidays removed. A sprint is a fixed-length cycle a team commits to delivering something in.
2. The vertical axis — the amount of work remaining. The most common unit is story points, a number describing the relative size of one item. Because points measure size rather than hours, they add up across a team whose members work at different speeds.
3. The starting point — the total remaining on day one. It's the sum of everything pulled into the cycle at planning, so a cycle that took on 40 points starts at 40.
4. The guideline — a straight line from the starting point down to zero on the last day. It traces where the line would sit if the team finished an equal amount every day. Almost no team tracks it; it's there as a reference.
5. The actual line — the real remaining total plotted each day. It only drops when an item moves to done, which gives it a staircase shape.

Reading it comes down to where the two lines sit relative to each other. Above the guideline means more work is left than planned; below means the team is ahead. Sometimes the shape says more than the position. A line flat for three days or more means nothing finished in that time, usually because one item was scoped too large or reviews are backed up. A vertical drop on the final day means every completion arrived at the buzzer, which is to say the chart gave the team no signal all cycle.

The chart has one blind spot. A line that goes up means new work arrived, but the chart can't tell you whether the scope grew or the team slowed down.

The drawing is normally done by the issue tracker. The team moves work between states and the line gets redrawn from those records every day, which means the real authoring happens in the states rather than the picture. Sit on finished work for two days and move it all at once and the line stays flat then drops in one step, delaying whatever decision the chart was supposed to prompt. What counts as movable is set by the definition of done (DoD), a checklist the team writes in advance — usually reviewed, tested, and running in production.

The audience is the team itself. The chart goes up on screen during daily scrum and drives what gets picked up first that day. If the line has drifted above the guideline, the call might be to clear the review backlog before anyone starts something new.

It travels badly outside the cycle. Remaining points are a unit the team invented for itself, so 40 means nothing to an outsider, and the chart shows no trace of what was actually built. Stakeholders get working software at the sprint review instead. The value that carries into the next cycle isn't this picture either — it's velocity.

"The burndown has been flat for three days. What's going on?"

Nothing has moved to done in three days, so where is the work stuck.

"At this rate we end Friday with 8 points left. Should we drop something now?"

Two days won't clear it, so decide in advance what rolls to the next cycle.

"That's a cliff this time, not a staircase."

Every completion piled up on the last day, so there was no visible progress to act on.

At Pagedeck the chart is always on screen when daily scrum opens. Theo moves what he finished the previous day and the line drops by that much, and Mia reads the position to decide what to ask. When the line hugs the guideline she says nothing about it. When the gap has held for more than two days she asks which item is stuck.

A gap on day six still leaves options. One item can roll to the next cycle, someone on other work can join for a day, or the scope can be trimmed to whatever is usable by Friday. Learning the same thing on the final day rules out all three.

A line below the guideline gets read as a healthy team. It's dropping faster than planned, so that seems obvious. But the line only tracks what moved to done, so a loosely applied definition of done drives it down on work that isn't actually finished. Move items that are still waiting on review and the line falls beautifully while that work returns next cycle. Now both this cycle's chart and next cycle's plan are wrong.

Splitting the chart per person is another common impulse. If it works for a team it should work for an individual, and it looks like a way to see who is behind. But the moment the chart splits, its purpose changes: a picture the team used to decide what to do today becomes a picture of whose line dropped least. That makes it rational to grab small items that move your own line rather than surface a blocked one, and people stop pairing up to push a single item over the finish.