A little less testing, a little more quality
summary
Shows concrete tradeoffs: a three-month release cadence forces heavy testing but not better outcomes, so the team moved admin web apps out of the monolith and runs a one-year migration to enable faster deploys. The result is more frequent releases, progressive rollout to customer cohorts, fewer tests overall yet faster feedback and fewer serious incidents; a customer‑support quote confirms improved stability. Also covers developer feedback loops, architectural approvals and when to accept versus observe risk.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:09Risk management beyond testing
- 4:00Product risk evolution
- 7:12Four ways to address risk
- 9:22Broken release cycle
- 11:49Architectural change for quality
- 13:53Collaboration for quality
- 14:36Non-testing quality activities
- 15:38Three dimensions of quality
- 18:55Quality engineers' role
- 20:17Career growth in QE
- 21:00Q&A
related talks
35mBetter, Faster, Stronger - Delivering High Quality Products
49mOptimizing QA Flow to Minimize Time to Release While Meeting Quality Standards
10mBeyond “try harder”: Effective strategies to tackle bugs
46mTalk about value, not testing – how to bring about rapid change
32mClimbing the Mountain of CI/CD: A Tester’s Tale
41mShift Left, Shift Right and Improve the Centre
40mScaling testing & test automation without losing control
33mTESTING IN PRODUCTION