Sandworms, Emergent Strategy, & Bug Hunting: Software Testing Lessons from Dune
summary
A test automation tooling team of 40 engineers supports about 5,000 engineers and runs sanctioned experiments to shift left: moving effort from long system integration phases into architecture changes, exploratory testing, bug bashes, training and tooling. Gaps are documented, presented to leadership and a mandate for experiments follows. A modern testing strategy is socialized via videos and a podcast, adoption spreads through decentralized leadership, and early results show reduced handoff delays and rising ownership of quality.
AI-written summary · about
chapters (17)
- 0:00Opening keynote
- 1:45Dune as Enterprise metaphor
- 6:48Automation as spice
- 7:56Testers as Fremen and Bene Gesserit
- 10:04Sandworms as change leaders
- 13:00Adapting to testing change
- 15:08Driving Enterprise change
- 18:42Resistance to change
- 23:06Facing fears in testing
- 25:53Emergent strategy for testing
- 28:18Vision in testing strategy
- 30:02Decentralized leadership
- 31:51Letting go for collective success
- 33:15Trust through collaboration
- 34:38Missionaria Protectiva as influence
- 40:11Flowing with change
- 41:56Q&A
related talks
01h 00mSandworms, Emergent Strategy, and Bug Hunting: Lessons from Dune...
55mTest Management Revisited
36mHow to defuse a bomb Wait, I mean a bug
43mOne Strategy, One Community: A deep dive into a Global Testing Transformation
57mOptimizing Your Testing Team
58mTesting Strategy - New Model, Better Outcomes
45mBuilding Tools to Free up Exploratory Testers
59mBabble & Dabble: Creating Bonds Across Disciplines