Purpose
Time in Status: is useful to understand which step of a workflow might be a bottleneck in the whole delivery chain. Time in Status shows time spent by issues in each state of their workflows.
There two types of this measure :
Average Time in Status
Cumulative Time in Status
How metric helps
Time in Status helps to find bottlenecks in the project via highlighting those statuses which consume unacceptable amount of time. For example, long time "In Testing" might be caused by a lack of QA engineers on a project. Further analysis of items in their statuses leads to understanding of root causes - and appropriate decisions how a process should be adjusted in order to eliminate inefficiencies.
How metric works
Chart overview
Time in Status is measured in hours (Axis Y) and in days (Axis Y) in weekly (Axis X) and monthly (Axis X) basis. Chart can be viewed for a specific issue type used in a project.
On hover over a column a hint appears with the following info:
Status
Number
Average/Cumulative time
Median time
Chart legend shows the following: workflow statuses for the selected issue type (if tickets have not been in any status during defined period, then this status is not shown in legend).
By click on a column a pop up appears with the following information got from a task tracking system: Issue ID; Type; Priority; Summary; Time in Status, h; Time in Status, d (value of time in status is a total time which a work item has spent in a particular status till today).
1 Chart shows time in status separately for each period, but a drill down shows total time which a work item has spent in a particular status (no matter which period was selected the result will be same).
Calculation
T status = (Timestamp a ticket left the status - Timestamp a ticket put in the status).
Cumulative time in status = sum up T status for all issues within the set period.
If status of the issues hasn't been changed during timeline, it will be accumulated with the other issues and display the whole time of the status in which item has been during selected timeline.
Avg time in status = sum up T status for all issues within the set period and divide by the number of issues. Rounding is to the whole number.
Average time will be calculated with the same logic as the cumulative time and after, accumulated time will be divided by the number of issues which were in the same status during the selected timeline.
Please see the examples below.
Example
Item 1 Blocked 40H
Item 2 Blocked 20H
Item 3 Blocked 25H
Item 4 Blocked 30H
Week 1
Average Time in Status = (40 + 20 +25 +30)/4 = 115/4 = 28.75
Cumulative Time in Status = 40 + 20 +25 +30 = 115
Week 2
1st Week Item 1 stays in Blocked 40 h (the whole week)
2nd week the Item 1 continues to be Blocked, the calculation of hours continues…41, 42, ….45…at the end of the week it will be 80 if status is not changed!
Average Time in Status = (80 + 20 +25 +30)/4 = 155/4 = 38.75
Cumulative Time in Status = 40 + 20 +25 +30 = 155
RAG thresholds: no.
1 If an issue is put in the same status several times within the selected time period, time is summarized for several occurrences.
2 Only statuses from the "To Do" and "In Progress" buckets are included into the calculation, i.e. statuses of "Done" bucket are not counted - because a very last status in each workflow will consume all averages thus showing irrelevant statistics.
Data Source
Data for the metric can be collected from a task tracking system (Jira, TFS/VSTS, Rally, etc.)
Copyright © 2024 EPAM Systems, Inc. |
|---|
All Rights Reserved. All information contained herein is, and remains the property of EPAM Systems, Inc. and/or its suppliers and is protected by international intellectual property law. Dissemination of this information or reproduction of this material is strictly forbidden, unless prior written permission is obtained from EPAM Systems, Inc. |