Developer | Rework Rate

Definition (Hover Text)

Rework Rate is the percentage of code changes where an developer rewrites code they recently updated within a given period (Past three weeks).

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>: <Rework Rate %>

Fields on Export

• Project

• Repository

• Branch

• Developer

• Days/Weeks

• Rework Rate

Business Logic

Calculation Formula

Rework Rate is calculated by dividing the number of code changes that were rewritten within the pre-configured time frame (e.g., three weeks) by the total number of code changes made during the same period. The result is then expressed as a percentage.

Rework Rate (%) = (Number of rewrites within the time frame / Total number of code changes) × 100

Trend

A decreasing rework rate is a positive indicator.

Maturity Levels

M1: > 80%
M2: 50 - 80%
M3: 20 - 50%
M4: 5-20%  
M5: <5%

Instance level thresholds

50%

Configurations

Processor Fields

Nil

KPI Specific fields

Target KPI Value

How to Validate KPI

Suggested ways of working

• Focus on clear, well-defined requirements to avoid unnecessary rework.

• Encourage comprehensive code reviews to catch potential issues before merging.

• Prioritize writing clean, maintainable code to reduce the need for frequent revisions.

• Implement robust testing practices to identify issues early, minimizing the need for rework.

Sample JQLs

N/A

Benefits of KPI

How does the KPI help

A high rework rate can indicate inefficiencies, miscommunication, or rushed coding. By tracking this KPI, teams can improve planning, minimize wasted effort, and strengthen overall code stability and quality.