Measure Performance: Reports

Report: Burn Down

Track remaining work over time, read the Remaining, Completed, Projected and Idealized series, and use Normalize Scope to see your true burn rate when scope arrives mid-cycle.

Burn Down answers how much is left, and will it be gone by the deadline at our current pace? It plots the work remaining in your filtered scope at the end of each period, the work completed in each period, a projection of where you will land, and the ideal straight line to zero. Use it during a sprint or release to see early whether you are on track.

Open and scope it

  1. Open Measure Performance and pick Burn Down under Agile.
  2. Set the Range. For a sprint, switch Range to From TimeBoxes and pick the sprint's timebox; for a release, pick a custom range ending on the target date so the Idealized line lands on it.
  3. Apply Filters that define the scope: a Board or cycle, a Parent workstream, or a Tag.
  4. Choose Show (Count by default, or Time Estimate, Point Estimate, Time Spent) and narrow by item type with For.

Reading the chart

SeriesWhat it shows
RemainingLine: work in the scope that is not in a done status at the end of each period. Work in any done-type status is excluded, so Remaining and the completed bars always agree
Completed Daily / Weekly / MonthlyBars: work completed in each period, named for the chart's granularity
ProjectedDashed line: where Remaining is expected to be at the end of each later period at your current pace. Never goes below zero
IdealizedStraight line from the first period that had scope down to zero at the end of the range, pro-rata by day

If Remaining tracks or sits below Idealized you are on pace; if Projected reaches zero after the end of the range you are not. A Remaining line that goes up means scope was added.

How the projection is calculated

The Projected line is a rate per elapsed calendar day, not per period. DevStride finds the first period in which the scope had any work, divides the work completed since then by the days that have actually elapsed, and extends that daily rate from the end of the last closed period to the end of each later period, the current one included.

Three things follow:

  • A period you are three days into counts as three days, not a whole week or month of low progress, so the projection does not swing at the start of a period.
  • The current period shows both values: Remaining carries the actual so far, Projected carries the expected close, fanning out from the same point at the end of the previous period.
  • Periods before your work existed are ignored, so a project scoped partway through the range is projected from the day it started.

Both Projected and Idealized mark the end of each period, so a team burning down at exactly the ideal pace retraces the Idealized line.

Normalize Scope

By default Remaining reacts to scope changes as they happen: add items mid-sprint and the line jumps up before coming back down, which makes the real burn rate hard to read and makes sprints hard to compare.

Switch on Normalize Scope (under Options, in the Data row) and DevStride treats everything that was ever in the period as present from day one. Total scope is calculated as everything completed in the period plus everything still remaining at its end; Remaining starts at that total and only ever falls. Projected follows the normalized line; the completed bars and Idealized do not change.

Normalize Scope is off by default, exists only on Burn Down, shows a Normalize pill in the toolbar while on (click the pill to turn it off), has no effect when the chart has a single period, and never changes your data. It is remembered per report in your browser and saved with a view.

Example. A two-week sprint starts at 40 points. On day six Remaining jumps from 24 to 36: twelve points were pulled in. Without normalization the chart reads as a team that stalled; with Normalize Scope on, Remaining starts at 52 and falls steadily at about 2.7 points a day, and Projected shows the sprint closing with 14 points left. The team's pace was fine; the plan took on more than it could finish, and Cycle Carry-Forward will show those 14 points next sprint.

The time axis

Weeks run Monday to Sunday. The period containing today is a partial period: Remaining stops at today's snapshot while Projected extends to the period's end. Nothing is plotted into the future, and a custom range that starts later in the current week or month treats that period as not yet begun rather than counting the days before the range as elapsed.

Items and Transactions tabs

The Items tab groups items by period into Completed, Not Completed, and Returned to Active (items moved back out of a done status), each with a count. The Transactions tab lists the status changes.

Pitfalls

  • An unfiltered Burn Down is meaningless. Across the whole organization Remaining never approaches zero. Always scope it to a board, cycle, or parent.
  • Unestimated items are invisible when Show is an estimate. Check the Current Progress Hours Estimated donut for the same scope first.
  • Estimates are current values. Re-estimating an item today changes its weight in every past period. Use Velocity for per-cycle numbers that keep the estimate at completion time.
  • Done-type statuses only. Work in a status that is not of type Done still counts as remaining, even if your team treats it as finished.