Accelerating Software Delivery: Why Your Team Is Slowing Down
summary
Bugs and technical debt throttle flow: teams lose velocity, releases miss windows, and flaky tests multiply if left disabled. Concrete fixes include no dedicated bug sprints, put tech debt on top of backlog, and automate boring DOD work (unit tests in pipelines, docs, UI checks). Use data‑driven decision tools like AHP + Pugh matrices to weigh tradeoffs, plan repayments for deliberate debt (example math: €2,400 saved vs €6,000 cost → €3,600 short), prefer small frequent deploys to get early user feedback.
AI-written summary · about
chapters (16)
- 0:00Introduction and flow concept
- 5:23Recognizing team slowdowns
- 8:34Redefining bugs and legacy
- 12:48Understanding technical debt
- 20:53Adding resources doesn't solve issues
- 23:01Vicious cycle of technical debt
- 25:09DevOps and early feedback
- 28:19Automate boring tasks
- 30:49Definition of done matters
- 31:54Untested hypothesis principle
- 33:44Flow vs anti-patterns in deployment
- 34:46Data-driven decisions over gut feeling
- 37:36Decide as late as possible
- 39:25Good enough over total conformance
- 44:03Practical tips for technical debt
- 45:08Q&A
related talks
31mTech Debt: Leverage for velocity acceleration
43mDeliver Fast with Confidence
15mFix your broken windows managing technical debt
23mThe Cost of Speed: Rethinking "Move Fast" in DevOps
28mTechnical Debt: Why it'll ruin your software
29mEconomies of Speed
31mDealing with Technical Debt
17mHow to deal with technical debt in fast-paced environment