Purpose

Not Done Bucket Review shows how work that is not done at the end of an iteration is transformed during a sprint or release. Transformation are as follows:

• Blocked means there work stoppages have place;

• Not Done means items do not get a "Done" status and not blocked;

• Done means items get a "Done" status according to the 'Done' column in Project Settings>Data Sources>Task Tracking system>Workflows.

How metric helps

Not Done Bucket Review helps to reveal issues in preparing scope for development. For example, it shows how long a blocked scope exists in an iteration so that it may explain why a plan for the iteration is not done.

How metric works

Chart overview

Chart shows a scope conversion in Story Points, Work Items, Person hours (remaining efforts), Person hours (original estimates) - Axis Y by day in a sprint or release - Axis X. Sprint or release is selected from the drop down in the chart.

Open

On hover over a point a hint appears with the following info: amount of scope in the statuses from a considered category. Category here is Blocked, Not done, Done. statuses are taken from Project Settings>Data Sources>Task Tracking system>Workflows.

Chart legend shows the latest values for the amount of scope in Blocked, Not done, Done categories.

By click on a point a pop up appears with the following information got from a task tracking system: 

• Issue ID

• Type

• Priority

• Summary

Calculation

Calculation for a metric depending on a selected unit of measure:

Data Source

Data for the metric can be collected from a task tracking system (Jira, TFS, Rally, etc.).