Technical Debt is defined as the consequences of poor software architecture and software development within a codebase. Carrying too much technical debt reduce the ability of software to change and evolve. In this article, Jurgen De Smet explains how to manage technical debt from a business perspective.
In this article, Jurgen De Smet discusses technical debt from his perspective of having worked with a large organization maintaining a very large software system. The article presents the different steps that were used to reduce technical debt. The strategy that was created aimed at combining business strategy with technical debt in a single management system. The business perspective was used to evaluate the necessity to re-factor items of the software system. The final situation is that it takes now only three days each month for the solution architect to maintain the process of visualizing the technical debt and having it linked to the business priorities.
Read the complete article on http://blog.co-learning.be/2013/02/28/learn-hxxow-to-manage-technical-debt-from-a-business-perspective/