Fix your broken windows managing technical debt
summary
Claims a real payoff: Gartner: 50% reduction in delivery time when teams actively manage debt. Defines debt as intentional or unintentional, tracked in existing tools like Jira/Trello, and triaged between legacy and greenfield code. Recommends concrete tactics: reserve 20% sprint capacity for fixes, require unit tests for new code, wrap legacy apps in container images, introduce CI/CD improvements, and break monoliths into smaller services. Emphasizes cultivating a continuous‑improvement culture so small defects don’t compound into months of slow delivery.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:20Broken windows theory
- 1:03Dirty dishes metaphor
- 2:30Impact on business
- 3:13Defining technical debt
- 4:57Tracking in tools
- 5:59Strategy for debt
- 7:23Tactics to address
- 8:49Accepting debt
- 9:52Legacy apps and debt
- 13:04Fresh start apps
- 14:29Key takeaways
related talks
45mAccelerating Software Delivery: Why Your Team Is Slowing Down
11mRefactoring: Managing technical debt before it blows up in your face
17mHow to deal with technical debt in fast-paced environment
01h 01mThe Technical Debt Prevention Clinic
48mTechnical Debt Trap
44mDeclare Bankruptcy on Technical Debt
53mThe Technical Debt Trap
45mTechnical Debt Prioritisation - Identifying & Fixing Highest ROI Issues