Purpose
Work Stoppages Life Time shows a resolution time of impediments in a project: time in hours from the moment an item became "blocked" until the actual date/time of its closure.
How metric helps
Work Stoppages Life Time helps to determine how many hours per selected timeline/month work has been stopped because of blocking items.
How metric works
Chart overview
Chart shows a resolution time of impediments in hours - Axis Y by month - Axis X.
On hover over a column a hint appears with the following information:
- Average life time for the selected month;
- Total lifetime for the selected month.
Drill down includes the following:
- Issue ID;
- Type;
- Priority;
- Summary.
Chart legend shows the following:
- the last calculated number of the metric;
- difference between the last metric values and the previous.
Calculation
Work stoppages lifetime = ∑Li...n/Ni,
where
Li - a work stoppage lifetime in hours in a considered month. If an issue is closed in the month effort logged after the issue closure later 00:00 next day is also included;
Ni - number of work stoppages in a considered month.
Example
Case 1: number of issues remains unchanged during the month:
- Calculation for 612 work stoppages existing the whole month: 31 days*24 hours*612 issues/612 issues= 744 hours.
Case 2: number of issues changes during the month:
- Total lifetime: 3 days*24 hours*1 issue + 2 days* 24 hours*1 issue + 31 days * 24 hours * 5 issues = 3840 hours.
- Average lifetime: 3840 hours/7 issues= 549 hours.
Calculation notes
1 Work stoppage is an issue satisfying a blocked status defined in Project Settings>Data Sources>Task Tracking System>Scope Management criteria 'Work stoppages tracking'.
2 If an issue lives all month long, the average amount of hours will be the same for a particular month for different projects if a number of work stoppages doesn't change during a month.
Data Source
Data for the metric can be collected from a task tracking system (Jira, TFS, Rally, etc.).