# Technical Debt
Status: public
Confidence: medium (0.76) (verified)
Last verified: 2026-05-28
Generation: ai_structured


## TL;DR

Technical debt is a software engineering metaphor for later rework created by expedient design or implementation choices.

## Core Explanation

The source set follows the idea from Cunningham's original experience report into later theory-building and systematic mapping work.

## Source-Mapped Facts

- Ward Cunningham introduced the technical debt metaphor in the WyCash portfolio management system experience report. ([source](https://doi.org/10.1145/157709.157715))
- Kruchten, Nord, and Ozkaya describe technical debt as a metaphor that helps reason about short-term software decisions and longer-term consequences. ([source](https://doi.org/10.1109/MS.2012.167))
- A systematic mapping study on technical debt and its management reviewed research from 1992 through 2013. ([source](https://doi.org/10.1016/j.jss.2014.12.027))

## Further Reading

- [The WyCash Portfolio Management System](https://doi.org/10.1145/157709.157715)
- [Technical Debt: From Metaphor to Theory and Practice](https://doi.org/10.1109/MS.2012.167)
- [A Systematic Mapping Study on Technical Debt and Its Management](https://doi.org/10.1016/j.jss.2014.12.027)