I’ve read 2 articles recently about technical debt: one by Martin Fowler, and one by Max Pool on Codesqueeze.
I particularly agree with Max’s idea that if you ‘Make your case, and show the business value, the majority of the time you will get that signature for the refactor’.
I always hear developers blaming management for a lack of time to refactor, but in my experience management is not the problem. Half the time management doesn’t even know they’re in the red. Also, they are generally thrilled to hear about how refactoring can better facilitate rapid delivery and how it’s actually a time-saver rather than a time-expenditure, if folded into the every-day development process.
In the past, I have taken the effort to consider how badly an issue is affecting development productivity, considered the effort required to fix the problem, and where relevant brought the argument forward not only to project managers, but in some cases directly to business facing consultants or clients themselves. As software professionals is it our job to make recommendations and consider trade-offs, etc. How can we say we have integrity otherwise? If we can justify the refactor, it is our job to pitch it accordingly.
This type of thinking needs to become ingrained in our day-to-day work. Seeking improvement in our software, process, and skill sets are an absolute must if we want to continue adding value in our field. Blaming management alone for technical debt is not acceptable.
No related posts.
Related posts brought to you by Yet Another Related Posts Plugin.
0 Responses to “Justifying Repayment of Technical Debt to Management”