By its simplicity, the concept of technical debt quickly became the baseline indicator for quality assurance management of software projects. Initially invented by Ward Cunningham in the 90′s, the Technical Debt consists of those tasks (feature, bug fixing, code refactoring, architecture optimizing, etc.) that a development team would – whether willingly or not – delay to a later sprint or product release.
It immediately provides the team with a breath of fresh air, but as with any other kind of borrowing, the later you reimburse the debt, the higher the interest will be. In other words, if a feature costs 100 to be developed today, it will cost 100 + something tomorrow, 100 + something higher the week after and so on. Thus, the higher the debt, the lower the innovation and competitivity.
Being able to analyze and manage a project’s technical debt is crucial to avoid this loss of productivity and reactivity.