Cutter Fellow Ward Cunningham, who coined the technical debt metaphor,[1] observed that when the development process leads to new learning, re-executing the project — or parts of the project — could lead to a better result. For this reason, among others, newly developed operational software assets can contain, embody, or depend upon artifacts that, in hindsight, the developers recognize could be removed altogether, or could be replaced by more elegant, effective, or appropriate forms that can enhance maintainability and extensibility.
Advisor
Toward an Unbiased Definition of Technical Debt
Posted March 22, 2016 | | Amplify
About The Author
Rick Brenner is Principal of Chaco Canyon Consulting. He works with people in dynamic problem-solving organizations who make complex products or deliver sophisticated services that need state-of-the-art teamwork and with organizations that achieve high performance by building stronger relationships among their people. Mr. Brenner focuses on improving personal and organizational effectiveness, especially in atypical situations, as in the case of… Read More
Don’t have a login?
Make one! It’s free and gives you access to all Cutter research.