Application development - Concept
Technical debt
Extra future work created by shortcuts or compromises made in technology today
What's it for?
Makes the future cost of today's shortcuts visible so teams can decide when the extra work should be repaid.
For example…
A rushed temporary report is later replaced with a proper data feed
A rushed release hard-codes a pricing rule in three places, creating technical debt because every future pricing change now requires extra work
Think of it like…
Only paying the minimum on a credit card: cash flow feels fine until interest compounds