Cynefin & Test Planning - an Option for Choosing the Right Testing Approach
summary
Cynefin maps testing context to concrete practices: obvious → automate unit and smoke checks, complicated → scripted or acceptance testing, complex → exploratory and session‑based testing, chaos demands rapid containment or exit. The claim is that choosing tools and effort by domain—probe/exploit, control/lead—yields more decision‑useful information than reflex automation. Context shifts continuously, so tests, automation and metrics must change with the system rather than forcing the system to fit a fixed practice.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:20Structure
- 1:35The testers role
- 2:52How to provide information
- 3:33Braille
- 5:30The Goal
- 5:59Easy to Believe
- 9:14What it means for testers
- 11:06Exploring
- 11:22Exploration
- 11:33Leadership Management
- 12:06Complexity
- 12:41Commodity
- 13:18Knowable
- 13:55Complex
- 15:20Exploratory
- 16:39Approach
- 17:25Statics
- 18:39Chaos
- 21:18Explore
- 22:07Standardization
- 22:55Conclusion
related talks
29mCynefin and Test Planning – an Option for Choosing the Right Testing Approach
40mCynefin and Sense-Making in the Digital World
20mEffective Testing Approaches for your Application with Cecelia Martinez
51mNavigating Uncertainty in Software Development: Effective Planning Techniques
46mWhat is Context-Driven Testing?
57mOptimizing Your Testing Team
18mEffective Test Automation Framework Design
58mTesting Strategy - New Model, Better Outcomes