How do you explain Software Debt to a non-software developer? Jason Roberts has put together a Technical Debt Simulator: some simple visualizations of the cost of software debt over time depending on the type of coding practices the developers are implementing, and some tables that give an example of this cost in “days of extra work”. Let’s say we develop low technical quality software in a large and highly complex system, with the technical debt interest rate at 21%, we would have 91 months of additional cost over the life of the system.
Even though the simulator is pretty basic and does not lean on any concrete numbers or calculations, it is still a good and simple way to present Technical Debt and can be useful to explain to non-technical folk.
Check out the simulator here.