| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
| Child pages (Children Display) | ||
|---|---|---|
|
Release KPIs categorization
Release KPI metrics provide valuable insights into various aspects of team performance and help organizations track their progress in Each Release. It is recommended to the be referred by the complete Scrum team that includes the Product owner, Scrum Master, developers, QA etc.
How are releases calculated?
The Release won’t be considered under calculation if the start and end dates are absent.
The Unreleased Release possesses an end date within an upcoming 6-month range following today or a start date within an upcoming 1-month range following today.
The Released Release, holds an end date in the range of the past 2 months from today.
Releases that follow the above conditions are applicable to the PsKnowhow Release board.
...
KPI Name / Definition
...
Representation
...
Tool
...
Maturity Level
...
Filters
...
KPI Calculation
...
On Hover
...
Remarks
...
dashboard KPIs are classified into 3 sub-tabs
SPEED
QUALITY
VALUE
The table below mentioned the corresponding category (sub-tab) for each KPI
Filters in Release Dashboard
Release dashboard has 2 filters
Project - User gets to see all the Projects he/she has access to. The default selection is the one that is selected if the user is coming from some other dashboard. If the user directly lands on Release dashboard, then defaults selection is alphabetically first project
Release - Automatically the latest unreleased version that has an end date nearest in the future as the default selection for a selected project. If there is no UNRELEASED VERSION, then user sees the most recent released version.
Sub tab | KPI Name | Definition | Representation | Tool | Filters | KPI Calculation | On Hover | Configuration |
|---|---|---|---|---|---|---|---|---|
SPEED | Release Burnup | Displays the cumulative daily progress of the release in relation to the overall Release scope. Users get to forecast the prediction completion of the Release. Alternatively, they can you check when development will be completed | Multi- Line chart | JIRA | Story Count Issue Count | Count of days from the Release start date to calculate closure rate of prediction Release Progress and Prediction logic based on
| ||
SPEED | Release progress KPI | It explains the count of issues in To-Do, In Progress, Done. | Horizontal Percent Bar Chart
|
Agile Project Management
Jira
Azure Boards
JIRA |
|
|
| 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>> | |
QUALITY | Defect count by Status | It shows the breakup of all defects within an iteration by Status. | Pie Chart
|
Agile Project Management
Jira
Azure Boards
JIRA | 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 |
QUALITY | Defect count by RCA | It shows the breakup of all defects within an iteration by status. | Pie Chart
|
Agile Project Management
Jira
Azure Boards
No Maturity
JIRA | 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 |
QUALITY | Defect Count by Priority | It shows the breakup of all defects within an iteration by Priority. | Pie Chart
|
Agile Project Management
Jira
Azure Boards
JIRA | 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 |
QUALITY | Defect Count by Assignee | It shows the breakup of all defects within an iteration by Assignee. | Pie Chart
|
Agile Project Management
Jira
Azure Boards
JIRA | 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 | ||||
QUALITY | Defect count by Testing Phase | Measures the number of defects that were not identified during each testing phase, such as QA, UAT, to enhance software quality and testing effectiveness. | Stacked Bar Chart | JIRA | No Filter | |||
VALUE | Epic Progress | Shows the progress of each epic in a release in terms of the total count and percentage completion, enabling effective release planning and tracking. | Stacked Bar Chart | JIRA | No Filter |