Understanding Rework Percentage
How we calculate. Rework % = rework effort ÷ total effort × 100. The form uses the same arithmetic as the worked examples on this page. See our methodology and accuracy policy.
Real-world scenario: A typical Rework Percentage case uses rework hours 180 and total project hours 1200. Enter the same figures below to reproduce the worked path.
What is Rework Percentage?
Quality and process efficiency metric. High rework often points to late defect discovery or unclear acceptance criteria.
- Define rework codes in time tracking
- Exclude planned iteration if agile policy says so
- Compare releases not one-off spikes alone
The Formula
Worked Example
Common Use Cases
- Process improvement: shift-left goals
- Release retros: quality cost
- Client reporting: warranty effort
Pro Tips
- Tag root causes
- Don’t hide rework in “misc”
- Pair with escaped defects
Limitations: Rework Percentage results are educational software estimation aids—not bids, contracts, or performance scores. Calibrate models to your organization’s history.
FAQ
Is code review rework?
Usually no—rework is fixing after “done.” Follow your time-coding policy.
What if total hours is 0?
Rework % is undefined—check time logs.
Authoritative References
For estimation and quality models, consult:
- COCOMO — Constructive Cost Model overview
- IFPUG — function point standards
- SEI / Carnegie Mellon — software engineering practice