Capability 04 of 04 · Organization
Tech Debt & Modernization
How AI accelerates paying down tech debt and modernizing legacy systems.
5
maturity levels
15
practices
15
guides
L1 · Stage 01Ad-hoc
Practices - what it looks like3 guides
- Tech debt accumulatesDebt grows is the default state of software engineering in organizations that have not made debt management a deliberate practice.guide→
- Legacy code left untouched"Legacy = don't touch it" is the fear-based approach to old or poorly understood code that characterizes L1 organizations.guide→
- Multi-year migration backlogA migration backlog measured in years is the state where an organization's known modernization work - framework upgrades, language version migrations, deprecated API replacements,guide→
Criteria - what to measure
- 01The team is aware of its main tech-debt areas
- 02Legacy systems are kept stable
- 03Team acknowledges tech debt exists and can enumerate major items
- 04Migration backlog exists (even if years long with no progress)
L2 · Stage 02Guided
Practices - what it looks like3 guides
- Debt categorized and prioritized; separate Disposable Software (deliberate throwaway) from durable systems - and track comprehension debt, the debt that accumulates silently where machines verify machinesDebt categorized and prioritized is the L2 state where an organization has moved from informal awareness of technical debt to a structured system for tracking, classifying, and ordering debt items.guide→
- Manual migration attemptsManual migration attempts are the L2 approach to executing framework upgrades, library replacements, and platform modernization: a developer (or small team) manually updates code tguide→
- OpenRewrite basic recipesOpenRewrite is an open-source automated refactoring tool for Java and other JVM languages that executes structured code transformations called "recipes." A recipe is a reusable, teguide→
Criteria - what to measure
- 01Tech debt is categorized and prioritized (severity, impact, effort)
- 02At least one manual migration attempt has been completed or is in progress
- 03OpenRewrite or equivalent automated refactoring tool has been evaluated or adopted for basic recipes
- 04Tech debt reduction is allocated time in sprint planning (even if small)
- 05Migration attempts are documented with lessons learned
L3 · Stage 03Systematic
Practices - what it looks like3 guides
- Continuous Modernization: agent pays off debt in backgroundContinuous modernization is the L3 shift from treating tech debt reduction as a project - something that competes with features for engineering time - to treating it as infrastructguide→
- Library bumps, version upgrades autoAutomated library bumps and version upgrades are the L3 practice of delegating dependency version management to an automated system that monitors upstream releases, identifies whenguide→
- OpenRewrite + agent = systematic refactoringOpenRewrite combined with an AI agent is the L3 pattern where structured code transformation (OpenRewrite recipes) is orchestrated by an AI agent that selects which recipes to applguide→
Criteria - what to measure
- 01Continuous modernization: agents work on tech debt reduction in background (non-blocking to feature work)
- 02Library version bumps and dependency upgrades are automated via agent PRs
- 03OpenRewrite + agent combination is used for systematic refactoring campaigns
- 04Agent tech debt PRs follow the same review process as feature PRs
- 05Dependency freshness score is tracked (% of dependencies within N versions of latest)
L4 · Stage 04OptimizedMost teams aim here
Practices - what it looks like3 guides
- "Dead project too expensive to modernize" → agent modernizes for pennies (sqlite-utils 4.0 for $149; reverse engineering that never penciled out now does)"Dead project too expensive to modernize" describes the category of software that an organization has written off as permanently unmaintainable - typically an internal tool, a legaguide→
- Cross-repo migration agentsCross-repo migration agents are AI agents configured to execute a consistent modernization task across dozens or hundreds of repositories simultaneously, opening PRs in each, handlguide→
- Java 8 → 21, Angular.js → Angular 17 via agents; the Bun model for full rewrites (conformance test suite first, then 64 concurrent agents)Java 8 to Java 21 and AngularJS to Angular 17 are two of the most common large-scale migration challenges in enterprise software engineering.guide→
Criteria - what to measure
- 01Projects previously deemed "too expensive to modernize" are being modernized by agents at low cost
- 02Cross-repository migration agents operate across multiple codebases simultaneously
- 03Major version migrations (e.g., Java 8 to 21, Angular.js to Angular 17) are agent-driven
- 04Cost-per-migration-PR is tracked and decreasing
- 05Cross-repo migrations complete within defined SLAs (e.g., 100 repos migrated in 30 days)
L5 · Stage 05Autonomous
Practices - what it looks like3 guides
- Tech debt = near-zero steady stateTech debt near-zero steady state is the L5 condition where technical debt does not accumulate over time because the rate of debt remediation equals or exceeds the rate of debt creation.guide→
- Agent fleet maintains, upgrades, patches 24/7An agent fleet that maintains, upgrades, and patches 24/7 is the L5 state where codebase maintenance is operationalized as infrastructure rather than treated as engineering work.guide→
- CVE remediation: detect → fix → test → ship autonomousAutonomous CVE remediation is the L5 capability where a security vulnerability announcement triggers a fully automated pipeline that identifies which repositories are affected, appguide→
Criteria - what to measure
- 01Tech debt is at near-zero steady state (new debt is paid down within the same sprint it is created)
- 02Agent fleet maintains, upgrades, and patches codebases 24/7 without human scheduling
- 03CVE remediation is autonomous: detect vulnerability, generate fix, test, and ship
- 04Mean time from CVE disclosure to deployed fix is under 24 hours for critical vulnerabilities
- 05Tech debt score (measured by static analysis) has been stable or improving for 6+ months
From the Field
Recent releases, projects and discussions the AI Radar classified into this capability.
release
openrewrite/rewrite
article
Thoughtworks Technology Radar Discussion on Sacrificial Architecture
article
Amazon is regretting AI [video][8 mins]
release
n8n-io/n8n
article
DoorDash Used Copilot to Convert Its XCTest-Based iOS Test Suite to Swift Testing
article
Behind the Scenes Hardening Firefox with Claude Mythos Preview
release
grafana/grafana
article
Fragments: May 14
Which level is your team at in Tech Debt & Modernization?
The criteria above are what we check in a facilitated assessment. Run it yourself to place this capability, see which gates you have passed, and compare it against the other 3 in Organization.
Start the assessment →