Definition (Hover Text)

This KPI measures the number of defects and categorizes them based on their root causes. It helps in identifying the underlying reasons for defects, allowing for targeted improvements.

Source Tools

Jira, Azure

Graph type

Line Chart

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

A lower count of defects, especially those with recurring root causes, indicates better quality.

Maturity Levels

NA

Instance level thresholds

Target KPI Value denotes the bare minimum a project should maintain for a KPI.

Global Configurations- (Field Mapping)

Processor Fields

• Custom fields Mapping

  • Root Cause eg; Code issue

KPI Specific fields

Workflows Mapping

Whenever we update the defect mapping and issue type mapping, whether we add or remove any issue type, we must run the processor. This is necessary to show the changes in the KPI.

Defect Mapping :

Image Added

Mandatory fields

Project Settings

1. Navigate to Project Settings: Start by going to the Project Settings in your application.

2. Access the Mapping Section: Within Project Settings, find and click on the Mapping option.

3. Mandatory Field: In the Mapping section, you’ll find the Mandatory Field. This is where you’ll configure the necessary global mapping fields.

4. Configure the Fields:

Defect Mapping :

• Issue Type to identify Defect - all the issue type that signify defect

Image Added

Issue type Mapping :

• Issue type for subtask Defect - Any specified issue category will be treated as a subtask that is linked to a story.`

Root Cause RCA : User need to provide that custom field which is associated with Root cause

Image Added

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

Best Practice

Root Cause Analysis

• Conduct regular reviews of defects and their root causes to identify patterns and trends.

Cross-Functional Collaboration

• Encourage collaboration between different teams (development, testing, operations) to gain diverse perspectives on root causes.

Continuous Improvement

• Establish a feedback loop where the team can learn from past defects and continuously improve their processes.

Preventive Measures

• Implement preventive measures based on the insights gained from root cause analysis to avoid similar defects in the future. Continuously refine and improve processes based on the findings from root cause analysis.

Benefits of KPI

Identifies Root Causes

• Helps in understanding the underlying reasons for defects, enabling the team to address the root causes rather than just the symptoms

Quality Improvement

• By addressing root causes, the overall number of defects can be reduced, leading to higher product quality.

Cost Reduction

• Reduces the cost associated with fixing defects by preventing them from occurring in the first place.

Data-Driven Decisions

• Provides valuable data that can be used to make informed decisions about process improvements and resource allocation.