Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents
minLevel1
maxLevel6
outlinefalse
typelist
printablefalse
Child pages (Children Display)
first3

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

Filters in Release Dashboard

Release dashboard has 2 filters

  1. 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

  2. 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

RemarksConfiguration

SPEED

Release Burnup

Displays the cumulative daily progress of the release in relation to the overall Release scope. It also provides insights into the scope added and removed during the release, providing valuable insights for monitoring, and managing the release progress.Users get to forecast the prediction completion of the Release. Alternatively, they can you check when development will be completed

Multi- Line chart

Agile Project Management

  • Jira

  • Azure Boards

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)

Agile Project Management

  • Jira

  • Azure Boards

JIRA

  • Filter By Assignee

  • Filter Ny 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

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

  • the count of defects in each RCA

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 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

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

    • Slices represent count of defects by each Assignee

    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