Sandworms, Emergent Strategy, and Bug Hunting: Lessons from Dune...
summary
Claims a concrete program: a modern testing strategy that pairs automation with coaching, decentralised leadership and measurable experiments. A tooling team supports 5,000 engineers inside a 31,000‑employee telco, runs data‑driven experiments, creates training, podcasts and showcases, and pushes change beyond testing into architecture and story slicing. Jira and automation feature as tools and levers. Adoption spreads (reaching 30,000 employees in communications), ownership diffuses, and the initiative shows early traction though results remain a work in progress.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 1:12Why Dune resonates testing
- 7:41Enterprise like Dune politics
- 10:35Spice in Enterprise orgs
- 13:48Dune themes for change
- 20:30Facing fears in transformation
- 27:02Intentional adaptation and dream destinations
- 31:14Shared outcomes clarity
- 34:32Decentralized leadership
- 39:12Trust across teams
- 41:45Flowing with change
- 44:52Q&A: AI in testing
- 48:24Q&A: Emperor in testing
- 49:26Q&A: Leadership in testing
- 50:10Q&A: Influence top management
- 52:19Q&A: Experiment without fear
- 53:41Q&A: Pushback from manual testers
- 55:06Q&A: AI the Mad Mouse
- 55:48Q&A: Role after idea adoption
- 56:30Q&A: Dune part one or two
- 56:52Q&A: Bene Gesserit in testing
- 57:35Q&A: First steps for testers
- 58:39Q&A: Dune house choice
- 59:00Q&A: Startup threats
related talks
45mSandworms, Emergent Strategy, & Bug Hunting: Software Testing Lessons from Dune
55mTest Management Revisited
57mOptimizing Your Testing Team
59mBabble & Dabble: Creating Bonds Across Disciplines
43mOne Strategy, One Community: A deep dive into a Global Testing Transformation
09m“Leading a Testing Revolution”
58mTesting Strategy - New Model, Better Outcomes
18mAutomation Lessons Learned