Release KPI metrics provide valuable insights into various aspects of team performance and help organizations track their progress in Each Release.
How are releases calculated?
For Future Releases -
If the End Date is present, all the releases within the range of the next 6 months are displayed.
Else If the Start Date is present, all the releases with a start date within the range of the following 1 month are displayed.
if Start Date and End Dates are not present then no release is displayed.
For Past Release -
If the End Date is present and it is in the range of the previous 2 months then the release is shown in PSknowHOW
KPI Name / Definition | Representation | Tool | Maturity Level | Filters | KPI Calculation | On Hover | Remarks |
|---|---|---|---|---|---|---|---|
Release progress KPI explains the count of issues in To-Do, In Progress, Done. | Horizontal Percent Bar Chart
| Agile Project Management
| No Maturity |
| It is calculated as a ‘Percentage’ for To, In Progress, Done based on size i.e story Point | Story Point: <<Percentage Value>> Issue Count: <<Percentage Value>> | |
Defect count by Status It shows the breakup of all defects within an iteration by Status. | Pie Chart
| Agile Project Management
| No Maturity | No Filter | the size of each slice would correspond to the proportion of data points belonging to that particular status | No Effect | Defects are considered based on the field ‘Issue type to identify defect’ which falls under Jira/Azure Mappings--> Defect Mappings |
Defect count by RCA It shows the breakup of all defects within an iteration by status. | Pie Chart
| Agile Project Management
| No Maturity | No Filter | the size of each slice would correspond to the proportion of data points belonging to that particular RCA | No Effect | Defects are considered based on the field ‘Issue type to identify defect’ which falls under Jira/Azure Mappings--> Defect Mappings |
Defect Count by Priority It shows the breakup of all defects within an iteration by Priority. | Pie Chart
| Agile Project Management
| No Maturity | No Filter | the size of each slice would correspond to the proportion of data points belonging to that particular Priority | No Effect | Defects are considered based on the field ‘Issue type to identify defect’ which falls under Jira/Azure Mappings--> Defect Mappings |
Defect Count by Assignee It shows the breakup of all defects within an iteration by Assignee. | Pie Chart
| Agile Project Management
| No Maturity | No Filter | the size of each slice would correspond to the proportion of data points belonging to that particular Assignee | No Effect | Defects are considered based on the field ‘Issue type to identify defect’ which falls under Jira/Azure Mappings--> Defect Mappings |