Practical tech-debt prioritization
summary
A concrete prioritization framework shows relative scores for impact risk and complexity and ships as a Notion template; engineers estimate with left t-shirt sizing, then run a collaborative vote in a FigJam template to fill four weeks of work. The process wins 30% of our time for quality in one quarter, produces 32 small “quality fruits” for one to two day fixes, and yields measurable wins: improved endpoint performance migrated and modernized stack and better pytype coverage.
AI-written summary · about
chapters (6)
- 0:00Tech-debt prioritization intro
- 1:50Defining impact
- 3:58Incepting team needs early
- 5:44Empowering team solutions
- 7:27Impact-first roadmap messages
- 9:17Recap and improvement
related talks
11mRefactoring: Managing technical debt before it blows up in your face
45mTechnical Debt Prioritisation - Identifying & Fixing Highest ROI Issues
20mPrioritizing Technical Debt as if Time and Money Matters
36mPrioritizing Technical Debt as if Time & Money Matters
32mPrioritizing Technical Debt as if Time and Money Matters
30mPrioritizing Technical Debt as if Time and Money Matters
17mHow to deal with technical debt in fast-paced environment
36mNo More ‘Someone Else’s Problem’: Tackling Tech Debt at Scale