Developer | Defect Rate

Definition (Hover Text)

Defect Rate is the percentage of merged pull requests that address defects or bugs identified after the code has been merged into the codebase.

Source Tools

Github, Gitlab, Bitbucket, Azure Repo

Graph type

Line

X Axis - Days/Weeks/Months
Y Axis - Percentage

Filters

Branches & Developers

Hover Format on KPI

<From Date - To Date>: <Defect Rate %>
No. of PRs: XX

Fields on Explore

• Project

• Repository

• Branch

• Developer

• Days/Weeks

• No. of Merges

• Defect PRs

• Defect Rate

Business Logic

Calculation Formula

The Defect Rate is calculated by identifying pull requests that address defects using keywords like "Fix," "Bug," or "Repair" in their titles.

For a given time period, the formula is:

Defect Rate (%) = (DefectsPR / MergedPR) × 100

Where:

DefectsPR is the number of pull requests with keywords indicating they address defects.
MergedPR is the total number of pull requests merged during that time interval.

Trend

A decreasing Defect Rate is a positive trend.

Maturity Levels

Nil

Instance level thresholds

Nil

Configurations

Processor Fields

Nil

KPI Specific fields

Target KPI Value

How to Validate KPI

Suggested ways of working

• Accurately track the status of all defects with proper timestamps.

• Standardize how defects are logged and categorized (e.g., severity, type) across teams for consistent data collection.

Benefits of KPI

How does the KPI help

The Defect Rate KPI helps improve overall code quality by highlighting how often defects are addressed in pull requests. It enables early detection of issues in the development and review processes, driving process improvements. Additionally, it supports better resource allocation by identifying areas that need more focus, such as testing or quality control.