Measure Performance: Reports

Report: Current Progress

Read the Current Progress donuts (completed, assigned, planned, estimated), drill into the items behind each one, and control how the Planned donut treats finished work.

Current Progress answers where does this body of work stand right now? It is a snapshot of today, not a trend: it has no date range, and every donut is drawn from the items' current state. Use it to check a release, an epic, or a team's queue before a planning meeting, and to find work that is unassigned, unplanned, or unestimated.

Open and scope it

  1. Open Measure Performance and pick Current Progress under Agile.
  2. Use For to choose item types, and Filters to pick the work: a Parent workstream for a release or epic, a Team, a Board, or a Tag. Without filters the report covers every item in the organization.
  3. Use Show to switch the donuts between Count, Time Estimate, Point Estimate, and Time Spent.

Reading the donuts

Each donut splits the same set of items two ways:

DonutLeft sliceRight sliceShown
CompletedItems in a done statusNot CompletedAlways
AssignedItems with a person or a persona assignedNot Assigned (neither)Always
PlannedItems on a board or cycleNot Planned (backlog)Always
Hours EstimatedItems with a time estimate greater than zeroNot EstimatedOnly when Show is Count or Time Spent
Points EstimatedItems with a point estimate greater than zeroNot EstimatedOnly when Show is Count or Time Spent

With Show set to an estimate, the slices are sized by hours or points rather than item count, so a Completed donut reading 60% means 60% of the estimated effort is done, not 60% of the items.

Example. For a release workstream the Completed donut shows 40 of 100 items done, Assigned shows 30 Not Assigned, and Hours Estimated shows 25 Not Estimated. Forty percent done is only half the story: a quarter of the remaining work has no estimate, so the Burn Down for this release is running on incomplete scope. Fix the estimates first, then trust the forecast.

Drill into the items behind a donut

Click Items in a donut's header. The chart is replaced by a table headed, for example, Current Progress - Completed, split into the two slices (Completed and Not Completed) with each item listed. Click an item to open and edit it; click Back to Charts to return.

Filter completed items out of the Planned donut

The Planned donut has a Filter Completed toggle in its header:

  • Off (default): finished items count as planned or not planned like any other item, so you see everything that was ever planned.
  • On: finished items are left out, so the donut shows only open work that is or is not on a board. This is the view to use when the question is "what still needs planning?"

The toggle affects only the Planned donut and its Items table. Your choice is remembered per organization in your browser and is saved with a view.

Open workload by persona

When your organization uses personas, a table above the donuts, Open workload by persona, shows for each persona the Open items, how many are Waiting for a person (persona set but no one assigned), the planned Estimate (hours, or points if your organization estimates in points), and Point effort.

An item is counted under the persona chosen on it, or under its assignee's first active persona when none is chosen; items with neither appear as Unspecified. A person with several personas is counted once, and subtask estimates already included in their parent are not counted again. This table describes open work and planned effort only; it is not a capacity or availability model. For hours already logged use User Time Tracking or the Time Allocation Matrix.

Pitfalls

  • No date range. An item completed two years ago is still Completed today. To see completion over time, use Trending Progress.
  • Archived items are excluded unless you turn on Include Archived under Options.
  • Estimated means greater than zero. An item with an estimate of 0 counts as Not Estimated.