Source: dzone.com
3 Tech Debt Metrics Every Engineer Should KnowCategory: Software, Business, Architecture
If you’ve ever argued for carving out time for this, you know that it can feel like a crusade of epic proportions. But it can be done, and in this guide, we’ll find out how to do it.
You should aim for a tech debt budget that brings you back down, or up, to the maximum amount of technical debt you can tolerate.
Andreas Klinger, Head of Remote at AngelList, puts it well in his article ‘Refactoring larger Legacy Codebases’: Put simply, your goal is to identify the intersection of things you'll work on this sprint, month, or quarter, and the parts of your codebase that have tech debt.
Not only is the topic of technical debt a lot easier to broach now, but we also know how much debt we're willing to take on, and when/how to pay it back.
You should aim for a tech debt budget that brings you back down, or up, to the maximum amount of technical debt you can tolerate.
Andreas Klinger, Head of Remote at AngelList, puts it well in his article ‘Refactoring larger Legacy Codebases’: Put simply, your goal is to identify the intersection of things you'll work on this sprint, month, or quarter, and the parts of your codebase that have tech debt.
Not only is the topic of technical debt a lot easier to broach now, but we also know how much debt we're willing to take on, and when/how to pay it back.
Related Articles
Community Partners
DevOps Careers