Better, Faster, Stronger - Delivering High Quality Products
summary
Claim: testing alone doesn’t improve quality — it only measures a preexisting bar. Practical moves: ship every commit with feature toggles, remove rollbacks so teams no rollback strategies fix forward, and apply work-in-progress limits to cut cycle time from >10 days to ~5 days. Favor unit-heavy testing pyramid, developers write tests and pair program, use monitoring. Evidence: one retailer moves from cautious releases to frequent deploys and now ships ~7× more with no rise in critical production errors.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:25What is quality
- 1:53Testing does not improve quality
- 3:38The process for quality
- 10:21The process for engineering
- 17:25The value of quality
- 21:26Finetuning the team
- 26:55Lessons learned
related talks
38mBuilding a high quality product
33mTESTING IN PRODUCTION
42mImproving Testing Quality by Changing Culture
23mA little less testing, a little more quality
37mBetter | Faster | Stronger - Delivering High-Quality Products
24mImproving Development Quality and Speed with Agile Testing
15mImprove continuous delivery by target quality aspects by your tests
24mTesting Less, Achieving More: How we mastered The Art of Strategic Testing