Definition (Hover Text)

Cycle time helps ascertain time spent on each step of the complete issue lifecycle. It is being depicted in the visualization as 3 core cycles - Intake to DOR, DOR to DOD, DOD to Live

Source Tools

Jira

Graph type

Bar Chart

Y Axis - Phases (Intake to DOR, DOR to DOD, DOD to Live)

X Axis - Days

Filters

Duration, Issue type

Hover Format on KPI

<<Days>>

Fields on Overlay

Issue ID, Issue Type, Issue Description, Intake to DOR, DOR to DOD, DOD to Live

Business Logic

Calculation Formula

Trend

Inversely Proportional - Higher Cycle time is considered bad

Maturity Levels

N/A (To be defined in future)

Instance level thresholds

N/A

Configurations

Processor Fields

KPI Specific fields

Status when issue is created

DOR Statuses

DOD Statuses

Live Statuses

Issue type to be included

How to Validate KPI

Suggested ways of working

1. Atleast one status should be defined to identify when stories are Ready to be picked up in a sprint

2. There should a status in workflow which depicts that an issue is resolved based on DOD

3. If the team is not following Continuous deployment, then an additional status to identify when a story goes LIVE should be defined

Sample JQLs

Benefits of KPI

How does the KPI help