Navigating Uncertainty in Complex Software Systems
summary
Claims that testing must reframe testing as uncertainty reduction rather than bug catching, demonstrates quality engineering practices used at BBC mobile products, and applies the Cynefin idea to probe sense respond with small experiments/spikes. Case evidence includes Blockbuster turning down Netflix ($50M) and collapsing from a $4.8B business, Nokia selling to Microsoft (deal written off, ~8,000 layoffs, brand rights later $350M), and Sears filing bankruptcy in 2018. Concrete methods: stakeholder mapping, short probes, measuring uncertainty with proxy scales.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:37Speaker's approach to quality
- 7:11Uncertainty and fight response
- 14:54Cultivating curiosity
- 18:29Complexity vs complicated systems
- 22:03Why testing fails
- 25:55Testing as uncertainty reduction
- 29:48Summary
- 32:18Q&A
related talks
31mUncertainty of change
51mNavigating Uncertainty in Software Development: Effective Planning Techniques
30mValue, Money, and Costs: The Ultimate Common Language for the Testing Strategy
10mThe value of testing
50mThe End of Testing as We Know It
38mHow Testing is Evolving in DevOps
29mCynefin and Test Planning – an Option for Choosing the Right Testing Approach
22mDeprecating Simplicity - Building a New Test Culture