Do you actively manage technical debt debt on your software development projects and if so, how do you do it?
How Technical Debt Is Abused. Working with and coaching many teams from many sectors for far too many years, I have found that technical debt always gets misused in the same ways. Teams — or especially tech architects — quoting that you should “spend 20% of your time on technical debt.”
One aspect of managing technical debt is in convincing non-technical managers that you need time allocated for refactoring and bug fixing.
Here's an article with specific suggestions on how to do that.
On our teams we actively manage technical debt. We do Scrum, so we spawn a technical debt card for either the current iteration or the next iteration depending on the estimate and our remaining sprint capacity and they get prioritized just like features and bug cards do. We also manage larger, cross-team debt items by having a cross-team backlog of technical debt that we prioritize and inject into each Scrum team during their sprint planning.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With