Source: dzone.com
Technical Debt: Interview With Adam Tornhill and Alex OmeyerCategory: Business, Data
Last week we hosted a webinar where Alex Omeyer interviewed Adam Tornhill about technical debt: what is it, why it's important, and how to manage it effectively.
It means that we have to work with the people we already have to get more work done — and the technical debt is a critical part of that.
My definition is: technical debt is any code that is more expensive than it should be, code that we have to pay interest on.
Then when we're talking about medium pieces of debt, typically you have a Team Lead who can go to a Product Manager and have a conversation about the debt that should be included in this sprint.Then it's the Product Manager's responsibility to decide how to allocate Engineering resources between maintenance and the features they have in the sprint.For the large pieces of debt, what I see usually, depending on the size of the company, is that they have Staff or Principal Engineers, who create technical proposals for bigger projects.
It means that we have to work with the people we already have to get more work done — and the technical debt is a critical part of that.
My definition is: technical debt is any code that is more expensive than it should be, code that we have to pay interest on.
Then when we're talking about medium pieces of debt, typically you have a Team Lead who can go to a Product Manager and have a conversation about the debt that should be included in this sprint.Then it's the Product Manager's responsibility to decide how to allocate Engineering resources between maintenance and the features they have in the sprint.For the large pieces of debt, what I see usually, depending on the size of the company, is that they have Staff or Principal Engineers, who create technical proposals for bigger projects.
Related Articles
Community Partners
DevOps Careers