Skip to content

Alternative Progress Visualization

Definition

The sprint burndown is one of Scrum's most misused artifacts. Intended as a tool for the team to manage themselves during a sprint—to see progress at a glance and re-plan daily—it's often appropriated as a reporting tool for management, then resented by teams. When that happens, teams either rebel or the data becomes inaccurate because they don't truly own it.

A good ScrumMaster updates the burndown to free the team from overhead. A great one helps the team find a fun way to manage themselves visually—which might not be a burndown at all. If the team owns the visualization, they'll invent something better suited to their context and be genuinely engaged in maintaining it.

In the Book

Watts tells the story of Mirjam and team B.O.B. Mirjam started updating the burndown every morning because the team threatened to abandon it if they had to maintain it themselves. Eventually the burden fell on Mirjam herself.

In a daily scrum, she asked: "Do you still find the graph useful?" Yes. "Can someone spare time to find a way to remove this overhead?" Over lunch, two team members sketched an electronic solution—a simple spreadsheet mirroring the wall, auto-calculating the graph. Mirjam printed and posted it daily.

But teams get slack about updates when they're not fully invested. The spreadsheet eventually disappeared.

In the next retrospective, Mirjam asked if they wanted to try something else instead of a burndown. The team came back with four alternatives:

  1. Burnup chart: inverted burndown (showing completed work instead of remaining). Not novel, but the team liked the variation.

  2. Work-type graph: tracked features, bugs, and changes separately, giving a richer picture than a single line.

  3. Weather forecast: a daily indicator of team sentiment—"how's the sprint going?" Forecast-style (sunny, cloudy, stormy). Simple, qualitative, engaging.

  4. Story points as pints: completed story points mapped to pints of beer (2 points = 1 pint). The more points delivered, the more pints. Fun, motivating, memorable.

The team chose a hybrid: the "pints" visualization (team motivation and output) plus the weather forecast (team feeling about sprint health). Both were lightweight and the team eagerly maintained them.

Watts makes a crucial point: The goal is not for the team to draw a graph but to find a way of visually representing their collective progress so they can effectively manage themselves. Great ScrumMasters recognize when a team is ready to own and adapt their own visualization (Shu-Ha-Ri: they've moved past following the rule and into shaping it).

He also warns about misuse: when the burndown becomes a tool for outsiders to micromanage the team, teams rebel. The irony is that if third parties let the team use it for their own benefit, it becomes an incredibly valuable information radiator for the rest of the organization. But its primary purpose must be team self-management, not external control.

Why It Matters

Progress visualization is about feedback and autonomy. When a team owns the metric, they're more likely to be honest about it, invest in maintaining it, and extract signal from it. Different teams optimize for different information—one wants to see work-in-progress flow, another wants sentiment, another wants motivation. Prescribing a single artifact misses the point: the value is in the team's collective reflection on progress, not in the format of the chart. This principle extends to any team-level metric; the team should choose or shape what it measures and how it visualizes, not be measured by outsiders.