What it means
Like financial debt, technical debt can be useful: a shortcut to meet a deadline can be the right call. But it has interest. Each quick fix, copied piece of code or missing test makes the next change a little harder, until simple features take weeks.
Old frameworks, unsupported libraries and systems nobody fully understands are common forms of technical debt.
Why it matters for a business
Unmanaged technical debt shows up as slow delivery, rising bugs and developers afraid to change things. Paying it down steadily, as part of normal work, keeps software affordable to change.
A business example
Things to watch
-
Record known debt so it is visible.
-
Pay some down in every sprint.
-
Add tests before changing risky code.
-
Upgrade frameworks before they lose support.