Overview | |
|---|---|
Definition (Hover Text) | gauges the speed of software delivery by measuring the duration between a code change and its deployment in production. It provides visibility into the efficiency and effectiveness of the development process. |
Source Tools | Jira, Repos (Github, Gitlab, Bitbucket) |
Graph type | Line |
Filters | Repo Name |
Hover Format on KPI | Date Range: <<Lead time in Days>> |
Fields on Overlay |
|
Business Logic | |
Calculation Formula | Time taken in no. of days from the time of commit to the time an issue moves to production |
Trend | Lower the time, better is the lead time |
Maturity Levels | M1: >3 Months M2: 1-3 Months, M3: <1 Month, M4: < 1 week, M5: < 1 Day |
Instance level thresholds | |
Configurations | |
Processor Fields | |
KPI Specific fields | |
How to Validate KPI | |
Suggested ways of working | |
Sample JQLs | |
Benefits of KPI | |
How does the KPI help | |
...