| 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
...
Developer Dashboard has been created to gather information and analyze the activity of a Repo. To enable this a new processor named as ‘Debbie’ has been created under which each of the existing Repos can be configured. The individual repo processors are also available if the Debbie processor is disabled through a flag.
A new configuration screen (Repo Tools setup) where we can create a new project on GitHub, Gitlab, or Bitbucket. This eliminates the need to navigate to each platform separately when creating new projects.
In future, the dashboard which have an option for users to look at the repo activity of an individual. <Planned for Q1 2024>
| Child pages (Children Display) |
|---|