Register and get even more out of the maturity test: personalized best practice comparisons and recommendations!
Technical debt is a metaphorical term to describe the “debt” that occurs, as an example, in programming code if the programming has not been done correctly. This sometimes happens to facilitate launching faster. An example of this debt can be so-called hard coding, which creates non-flexible systems. Other examples are lack of documentation or tests. Debts that arise need to be “paid off” by subsequent actions. If the technical debt becomes too large, the programming will end up in a state where all time goes to fixing the problems created by the shortcuts. Which is to say: All resources go to paying interest on the technical debt rather than amortization. Similar to how most people’s private finances look, it’s likely unreasonable to be completely debt-free and neither is that a goal that needs to be achieved. Rather, it’s about keeping the debt under control and getting the right balance of interest and amortization.
