...
Standard Time in Status metric works excellent excellently in most cases. But what if you want to analyze specifically what's happening in your sprints you might want to have a custom chart. Here is how to create it.
...
This metric is based on Task Tracking System's (Jira, Azure Boards or Rally) data.
Tickets assigned to sprints are taking taken into account.
Metrics doesndon't calculate time in Done Statuses (set in configuration)
Main calculation logic: T status = (Timestamp a ticket left the status - Timestamp a ticket put in the status). Also metric takes into account when ticket has been assigned to a sprint & whether it left a sprint before its end.
Example: ticket created & assigned to a sprint during a sprint in To Do status, spent 1 day & got unassigned. In this case time in To Do status for this ticket for that sprint will be 1 day.
Example: ticket created & assigned to a sprint before its start & spent the whole sprint in To Do status till the end. Time in status will be equal to sprint duration (+ time from creation to sprint assignment for calculation logic 1) in this case.
There are 2 types of calculation logic - whether to take into account time spent in status before sprint assignment or not. In 4b example if we want to take into account time from creation to sprint assignment then we use logic 1, if not - logic 2.
Use logic 1 if you want to see what happened before assignment to a sprint - e.g. it could reveal carry-overs
Use logic 2 if you want to see where your ticket spend spends more time within an a sprint.
In case of re-opens metric calculate sum of time spent in the same statuses.
There are options to aggregate values in a median, average or cummulative cumulative way.
Time in status is measured in days.
...
Configuration
We have 4 6 variables in the code of this metric:
...
How to interpret this metric & next steps
Please read the information on how to interpret this metric here.
...