Talk about value, not testing – how to bring about rapid change
summary
Claims a move from long, 14‑month releases to weekly releases and eventually a startup exit (~£350–360M) by reframing testing as demonstrable value; engineers build automation (developers write Selenium suites), coverage climbs quickly (prototype in three weeks, big coverage within months), test case management is discarded for pragmatic checks (test case management system of doom), roadmaps stop being Gantt charts of devastation, ops and devs pair, put devs on call, add monitoring and rollbacks to hit 99.999% uptime targets and actually ship.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 3:14Failures of traditional testing
- 12:24Defining value in organizations
- 23:46Risk-based to value-based testing
- 31:54Overcoming friction in change
- 36:49Balancing business and culture
- 46:01Q&A
related talks
09m“Leading a Testing Revolution”
29mMoving Fast!
32mClimbing the Mountain of CI/CD: A Tester’s Tale
53mTransforming testing methodologies: From manual to robust strategies
23mA little less testing, a little more quality
41mShift Left, Shift Right and Improve the Centre
36mContext-driven Agile Tester
40mEmbracing Shift-Left Testing