Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Average Time in StatusĀ 

  2. 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.

...

  • Status

  • Number

  • Average/Cumulative time

  • Median timeImage Removed

...

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).

...

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.

...

Note

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.

...