Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 25 Next »

Release KPIs categorization

Release dashboard KPIs are classified into 3 sub-tabs

  1. SPEED

  2. QUALITY

  3. VALUE

The table below mentioned the corresponding category (sub-tab) for each KPI

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

  1. Overall Completion

  2. Dev Completion

SPEED

Release progress KPI

It explains the count of issues in To-Do, In Progress, Done.

Horizontal Percent Bar Chart

  • It gives the breakup (To-do, In Progress, Done) based on size (story points)

JIRA

  • Filter By Assignee

  • Filter By Priority

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

  • Slices represent the count of defects in each Status

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

  • the count of defects in each RCA

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

  • Slices represent count of defects in each Priority

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

  • Slices represent count of defects by each Assignee

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

  • No labels