Deliver Fast with Confidence
summary
Agile plus tests alone do not stop technical debt; continuous small refactorings, measurement and injected slack time do. Teams use Sonar/Jenkins, IDE refactor tools (rename, extract) and version control to automate checks, run daily 30–60 minute cleanup, and show dashboards that track debt. Case examples: a large Java codebase (~2M LOC) split across 29 teams, another org grows seven mob teams and sees defects fall. Practical, safe moves: Boy Scout rule and backlog colorization for technical work.
AI-written summary · about
chapters (42)
- 0:00Introduction
- 0:31Agile Development
- 1:25Technical Cadet
- 1:44Backlog
- 2:02Product Development
- 2:27Under the Hood
- 3:18Problems
- 4:01Our favorite language
- 4:33Contagious
- 5:22Technical Debt
- 6:00Values
- 6:10Hidden Values
- 8:09Values Drive Practice
- 8:53Agile Practices
- 12:19Simple Solutions Always Work
- 13:22Continuous Improvement
- 16:25Clean Code
- 17:59Boy Scout Model
- 19:23Top 10
- 23:40Kaizen
- 24:47Slack Time
- 27:08Spotify
- 28:14allocate time
- 29:53delivery size
- 31:18New technology
- 31:28Practice practice practice
- 32:08Colorize your backlog
- 32:45Fit it into your processes
- 33:04Refactoring
- 34:08Defects
- 34:36Debt
- 35:33Continuous Inspection
- 36:45Automate
- 37:02Pause Points
- 37:26Checklists
- 38:45Where do you start
- 39:35Architecture can evolve
- 39:53Values drive your practice
- 40:21Lazy manifesto
- 41:03Kaizen principle
- 41:28Rethinking manifesto
- 42:05Core ideas
related talks
45mAccelerating Software Delivery: Why Your Team Is Slowing Down
36mNo More ‘Someone Else’s Problem’: Tackling Tech Debt at Scale
01h 01mThe Technical Debt Prevention Clinic
48mDeveloper Joy – How Great Teams Get s%*t Done
31mDealing with Technical Debt
01h 12mBuilding a Technical Credibility to Fight Technical Debt
44mWhat are you Risking by Ignoring Technical Debt?
25mLiving With Technical Debt: Acknowledge It, Specify It, Reduce It