The metaphor of technical debt is widely used in software project management in general and especially Scrum. This article written by Philippe Kruchten, Robert L. Nord and Ipek Ozkaya try to put this concept in perspective, discussing how it has become somewhat diluted lately with its extension to other areas than code or its associations with tools like static code analyzers.
Using only tools to measure technical debt might lead to leaving aside potential technical debt items that are undetectable by tools like structural or architectural debt. They argue we need ...
Previous Topic
