| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
KPI Name / Definition
...
Representation
...
Tool
...
Maturity Levels
...
KPI Calculation
...
On Hover
...
Remarks
...
Number of Check-ins & Merge requests
helps in measuring the transparency as well the how well the tasks have been broken down.
Line Graph
Y- Axis - Count
X- Axis - Days
Aggregation Method - Sum'
Positive trend indication - Increase
Agile Project Management
Repos
...
M1: 0-2
M2: 2-4
M3: 4-8
M4: 8-16
M5: >16
...
NUMBER OF MERGE REQUESTS when looked at along with commits highlights the efficiency of the review process
It is calculated as a Count. Higher the count better is the ‘Speed’
Maturity of the KPI is calculated based on the latest value
Date: <<Value>>
...
Mean time to merge
measures the efficiency of the code review process in a a team
Line Graph
Y- Axis - Hours
X- Axis - Weeks
Aggregation Method - Average
Positive trend indication - Decrease
Agile Project Management
Repos
...
M1 : > 48 Hours
M2 : 16 - 48 Hours
M3 : 8 - 16 Hours
M4 : 4-8 Hours,
M5 : <4 Hours
...
It is calculated in ‘Hours’. Fewer the Hours better is the ‘Speed’
Maturity of the KPI is calculated based on the average of last 5 values that corresponds with the maturity scale
...
| Child pages (Children Display) |
|---|