Relieving Technical Debt through Short Projects

on YouTube ↗21m

" summary

Teams run one- to two-week interrupt reduction projects on a weekly rotation so one site handles most pages while the other focuses on short automation, docs, and detection work; projects come from a prioritized hot list of bugs and include handoffs and a design note about avoiding new toil. Expect initial targets like “70 tickets / 30 projects” to fail — actual result after ~8 months is a much lower pending ticket queue and fewer new tickets because fixes reduce incident frequency.

AI-written summary · about

" chapters (4)

1. 0:00Start
2. 6:30Treading water
3. 12:54Unbreak autom
4. 14:25Pending ticket

" related talks

• 11mRefactoring: Managing technical debt before it blows up in your faceAmanda Sopkin · LeadDev New York 2022
• 45mTechnical Debt Prioritisation - Identifying & Fixing Highest ROI IssuesNaresh Jain · Agile India 2021
• 31mDealing with Technical DebtKaterina Trajchevska · Laracon EU Online 2021
• 45mAccelerating Software Delivery: Why Your Team Is Slowing DownEwald Verhoeven · DevConf 2023
• 43mDeliver Fast with ConfidenceJoseph W. Yoder · JDD 2016
• 10mPractical tech-debt prioritizationSahana Carlsen · LeadDev Berlin 2023
• 36mDEVELOPER ORIENTED PROJECT MANAGEMENTRobert Pankowecki · wroc_love.rb 2014
• 05mLightning Talk: Tackling Technical Debt: Hello Junior Developers!Tulio Paschoalin Leao · CppCon 2021