Five Key Challenges for Agile Testers tomorrow
summary
Argues that deployment cadence is shortening toward 10 releases a day, so full regression suites become infeasible and teams must adopt risk-based test selection, feature switches and fast rollback; shows Google’s attribute-component-capability matrix and context mapping from Domain‑Driven Design as concrete tools for locating risk; describes hiring a test architect who teaches developers exploratory techniques rather than bottlenecking tests; recommends effect maps, production metrics, Lean Startup and How to Measure Anything to track business impact rather than vanity bug counts.
AI-written summary · about
chapters (12)
- 0:00Intro
- 2:24A scarier message
- 3:58Shorter delivery phases
- 5:31No overnight builds
- 8:40Fast feedback from customers
- 10:19Agile testing quadrants
- 13:56Managing risk
- 16:55No more iterations
- 18:29Kanban
- 24:29Solution
- 31:39Context Mapping
- 37:59Recommended books
related talks
33mAgile Software Testing
09m“Leading a Testing Revolution”
34mHelping Testers Add Value to Agile Projects
43mHow I fell in love with Agile testing and why you should, too!
08mTesting In Agile
46mSammy Kolluru: Enhancing the Capabilities of Your Test Team: Preparing for Agile
39mMyths & Challenges of Agile Testing
09m"A few things about Agile Testing"