Concept describing short-term technical compromises that slow long-term maintainability and development.
Technical debt describes deferred or suboptimal technical decisions that speed short-term delivery but degrade long-term maintainability and development velocity. The concept covers code, architecture, and process debt as well as strategic risks. It provides a decision framework to assess, prioritize, and gradually repay these liabilities.
Ratio of estimated repayment effort to overall development effort.
Percentage of code lines covered by tests; indicator of maintainability.
Average time to resolve production incidents.
An old monolith system holds high technical debt; migration needed to improve maintainability and scalability.
Rapidly implemented features without sufficient tests increase long-term defect rates and maintenance costs.
Outdated infrastructure components are postponed, increasing security and reliability risks.
Inventory existing debt and categorize it.
Assess risk, cost, and business relevance.
Prioritize and integrate into backlog and sprints.
Continuously measure and adjust the repayment strategy.