Choosing Quality to Improve Your Team's Velocity
summary
The talk explains how bugs, technical debt and development velocity interact and argues for choosing quality to sustain long-term velocity. It covers ways to measure project quality, which signals to monitor, and actionable steps to take when quality problems arise.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:04Technical debt and velocity
- 3:11Quality cost vs lack of quality
- 6:04Project death spiral
- 8:11Detecting and fixing defects
- 11:09Managing technical debt
- 12:59What to do when failing
- 14:03Conclusion
related talks
37mDebugging Engineering Velocity
01h 02mAgile Metrics: Velocity is NOT the Goal
41mEscape Velocity - Better Metrics for Software Teams
48mVelocity Deep Dive
01h 14mQuality versus Speed in the SDLC
45mAccelerating Software Delivery: Why Your Team Is Slowing Down
31mTech Debt: Leverage for velocity acceleration
11mTake back control of code quality