Measure Performance: Reports

Report: Burn Up

Track completed work climbing toward total scope, read the per-period bars, the cumulative line and the projection, and know when to use Burn Up instead of Burn Down.

Burn Up answers how much have we finished, and how does that compare to everything in scope? Where Burn Down shows the work remaining shrinking toward zero, Burn Up shows completed work climbing, with total scope drawn as a separate line. Because scope has its own line, a Burn Up makes scope growth visible instead of hiding it inside a flattening burn-down.

Open and scope it

  1. Open Measure Performance and pick Burn Up under Agile.
  2. Set the Range: for a sprint or release, switch Range to From TimeBoxes and pick the timebox so the chart spans exactly that period.
  3. Choose Show (Count, Time Estimate, Point Estimate, Time Spent) and narrow with For and Filters. Apply at least one filter (for example a Parent workstream or a Board) so the scope line is meaningful.

Reading the chart

SeriesWhat it shows
Completed Daily / Weekly / MonthlyBars: work completed in each period, named for the chart's granularity
CompletedLine with a shaded area: running total of the bars, that is everything completed since the start of the range
ProjectedDashed line: where the Completed line will be at the end of each future period at your current pace
TotalDashed gray line: everything in scope at the end of each period, done or not. Drawn only when at least one filter is applied, because across the whole organization it sits far above the trend and flattens the chart

The gap between Total and Completed is the work remaining. The two lines meet when the work is done.

How the projection is calculated

The Projected line uses the same rule as the Burn Down report: DevStride finds the first period in which the scope had any work, divides the work completed since then by the calendar 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 period shows both its completed-so-far and its projected close. Weeks run Monday to Sunday, and the period containing today is drawn as a partial period.

Example. The Total line steps up from 80 to 110 points in week four while Completed climbs steadily at 10 points a week. On a Burn Down the same event looks like the team "slowing down"; here it is plainly 30 points of new scope. Either the end date moves out three weeks, or the 30 points move out of this release.

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). The Transactions tab lists the status changes.

Pitfalls

  • No filter, no Total line. Add a filter if you need the scope line.
  • Completed starts at zero at the left edge of the range. It counts completions inside the range, so it is not the all-time completed total; the Total line, by contrast, includes work finished before the range.
  • Estimates are current values. Re-estimating an item today changes its contribution to every past period.