Technical Debt Prioritization
Prioritize technical debt with weighted scoring for impact, risk, and effort. Enter values for instant results with step-by-step formulas.
Worked Examples
Example 1: Security-Critical Debt
Problem:Outdated authentication library with known CVE. Effort: 3 weeks. Impact: 7/10. Risk: 10/10. Velocity impact: 3/10.
Solution:Priority score: 7.4 (High). Despite moderate impact and low velocity drag, security risk makes this urgent. Should be addressed in next sprint.
Result:High priority | Security critical | 3 week effort | Address immediately
Example 2: Velocity-Killing Debt
Problem:Monolithic codebase making features take 3x longer. Effort: 8 weeks. Impact: 9/10. Risk: 4/10. Velocity: 10/10.
Solution:Priority score: 7.3 (High). High effort but enormous velocity impact. Consider incremental migration—strangler fig pattern rather than big bang.
Result:High priority | Velocity critical | Incremental approach | 8 week total
Example 3: Low-Priority Debt
Problem:Inconsistent code style in legacy module. Effort: 1 week. Impact: 2/10. Risk: 1/10. Velocity: 2/10.
Solution:Priority score: 3.2 (Low). Annoying but not impactful. Address opportunistically when touching this code anyway. Don't dedicate sprint time.
Result:Low priority | Cosmetic | Opportunistic fixes | No dedicated time
Frequently Asked Questions
What is technical debt?
Technical debt is the implied cost of future rework caused by choosing easy/quick solutions over better approaches. Like financial debt, it accumulates interest—shortcuts now create maintenance burden later. It includes code debt, architecture debt, test debt, and documentation debt.
How do you prioritize technical debt?
Prioritize by: impact on development velocity, risk to system stability/security, effort to remediate, and business value unlocked. High-impact, low-effort items (quick wins) often go first. High-risk items may need immediate attention regardless of effort.
What percentage of time should go to tech debt?
Common approaches: 20% rule (one day per week), dedicated tech debt sprints (1 per quarter), or capacity allocation (15-25% per sprint). The right amount depends on debt severity—teams with critical debt may need 40%+ temporarily.
How do you measure technical debt?
Metrics include: code complexity scores (cyclomatic complexity), test coverage percentage, dependency age, deployment frequency, bug fix time, and developer surveys. No single metric captures all debt—use a combination.