Top Highlights

• Understand When to and When Not to
• These prioritization questions get to the heart of the skill which is to be able to understand when, and when not to, address tech debt. There are a couple key factors to consider: Developers’ perspectives Business impact Tradeoffs on other initiatives
• Track It In the Same Place
• If tech debt tasks do not end up in the backlog, they will never get executed. Track tech debt issues in the same backlog you use, and hold them accountable to the same standards. In many orgs, that means having a spec with the key points in place.
• Empower developers to find, suggest, prioritize, and address tech debt. At each step, they will feel happy to be included, and feel better about the decisions being made of which tech debt to prioritize.

Tags