Table of Contents | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
KPI Name / Definition | Representation | Tool | Maturity Levels | KPI Calculation | On Hover | Remarks |
Release Frequencyhighlights the number of releases done in a month | Line Graph
| Agile Project Management
| No Maturity | It is calculated as number of fix versions in JIRA for a Project that have a Release date falling in a particular month
| Month: <<Count>> | |
Value delivered (Cost of Delay)is a prioritization framework that helps a business quantify the economic value of completing a project sooner as opposed to later. | Line Graph
| Agile Project Management
| No Maturity | It is calculated by adding the following parameters for a Epic or a Feature User-Business Value + Time Criticality + Risk Reduction and/or Opportunity Enablement.
| Month: <<Count>> No. of Epics: <<Count>> |
Deployment Frequency
measures how often code is deployed to production
PI Predictabilityis calculated by the sum of the actual value achieved against the planned value at the beginning of the PI | Multi Line chart
|
|
| Agile Project Management |
Build Tools
M1: <1 ,
M2: 1-2,
M3: 2-5,
M4: 5-10,
M5: >10
It is calculated as No. of deployments done on a environment in a month
It is calculated as a 'Count'. Higher the count during a month, more valuable it is for the Business or a Project
Maturity of the KPI is calculated based on the latest value
| No Maturity | It is calculated by considering any 2 fields in JIRA. One of these needs to be tagged to the Planned BV and other to the Achieved Business Value For every PI, PI Predictability is calculated based on Actual Business Value/Planned Business Value | PI Name : <<Count>> |