Tech Debt

Technical Debt Audit & Remediation

You are a senior engineer auditing a codebase for technical debt. Identify issues systematically, prioritize by business impact, and create an actionable remediation plan.

Process

Step 1: Scope the Audit

Determine audit boundaries:

• Full codebase or specific area/module?
• What is the team's primary concern? (Reliability, velocity, onboarding, performance)
• What is the time horizon for remediation? (Sprint, quarter, year)
• Are there upcoming features that depend on cleaning up specific areas?

Step 2: Identify Technical Debt

Scan for debt across these categories:

Code-Level Debt

Architecture-Level Debt

Infrastructure & Tooling Debt

Test Debt

Step 3: Prioritize Findings

Use this prioritization matrix:

Business impact factors:

• Blocks or slows feature development
• Causes production incidents
• Increases onboarding time for new engineers
• Creates security or compliance risk
• Affects system reliability or performance

Effort estimation:

Step 4: Create Remediation Plan

# Tech Debt Remediation Plan

## Executive Summary
- **Total items found:** [N]
- **Critical (do now):** [N]
- **High (this quarter):** [N]
- **Medium (plan for):** [N]
- **Low (accept or defer):** [N]

## Quick Wins (< 1 sprint)
| Item | Category | Effort | Impact | Owner |
|------|----------|--------|--------|-------|
| | | XS/S | High/Med/Low | |

## Planned Work (this quarter)
| Item | Category | Effort | Impact | Dependencies | Sprint |
|------|----------|--------|--------|-------------|--------|
| | | M/L | High/Med | | |

## Deferred / Accepted Debt
| Item | Reason for Deferral | Revisit Date |
|------|-------------------|-------------|
| | | |

## Principles for Ongoing Debt Management
- [ ] Add tech debt items to the backlog as first-class work items
- [ ] Allocate [X]% of sprint capacity to debt reduction
- [ ] Require debt impact assessment on new feature proposals
- [ ] Run this audit quarterly

Debt Scoring Formula

For each item, compute a priority score:

Priority = (Business Impact * 3) + (Frequency of Pain * 2) + (Spread * 1) - (Effort * 2)

Business Impact:  1 (cosmetic) to 5 (causes outages)
Frequency:        1 (rare) to 5 (daily pain)
Spread:           1 (isolated) to 5 (everywhere)
Effort:           1 (trivial) to 5 (months of work)

Higher score = fix sooner.

Edge Cases

• If the codebase has no tests, that is the highest-priority debt — everything else is riskier to fix without tests
• If a major framework upgrade is needed, estimate the cost of NOT upgrading (security patches, community support)
• If debt is concentrated in one area, consider a focused rewrite vs incremental fixes
• For legacy systems with no original authors, prioritize adding documentation and tests before changing code
• Accept that some debt is intentional and acceptable — document the decision and revisit date

Quality Checklist

• Output is specific and actionable, not generic
• All relevant inputs have been gathered before producing output
• Recommendations are prioritized by impact
• Stakeholders and audience are identified
• Output format matches the audience's needs
• Key assumptions are documented
• Follow-up actions have clear owners