Page Comparison

Definition (Hover Text)

measures number of defects along with the root cause of defects

Source Tools

Jira, Azure

Graph type

Line

Filters

-

Hover Format on KPI

Sprint Name:

RCA1: <<Value>>

RCA2: <<Value>>

RCA3: <<Value>>

RCA4: <<Value>>

Fields on Overlay

Sprint Name

Defect ID

Issue Description

Root Cause

Business Logic

Calculation Formula

No. of defects linked to stories in the iteration grouped by Root Cause

Trend

Lower the count, better is the ‘Quality’

Maturity Levels

-

Instance level thresholds

Configurations

Processor Fields

• Custom fields Mapping

  • Root Cause eg; Code issue

Mandatory fields

• Issue Type Mapping

  • Issue types which will have linked defects  eg; Story

How to Validate KPI

Suggested ways of working

Sample JQLs

project = "Your Project Name" AND issuetype = Bug AND Sprint in openSprints() ORDER BY "Root Cause" ASC

Benefits of KPI

How does the KPI help

The Defect Count by Root Cause Analysis (RCA) KPI helps teams identify the root cause of defects, enabling them to take corrective actions to prevent them from recurring. This leads to improved product quality, reduced costs, and increased customer satisfaction by addressing the underlying issues and preventing similar defects from occurring in the future.