Is There Room For Test Strategy in Agile
summary
Argues every project needs a tailored test strategy and shows concrete results and formats: a 20‑page strategy, a compact mind map, a one‑screen email for executives, or just post‑its. Recommends CI pipelines, unit tests, in‑memory DBs and mocks, exploratory sessions attached to Jira tickets, dashboards and load generators. Cites metrics: reduced regression time to half a working day, unit coverage 30%→70% and delivers short architectural recommendations that teams actually implement.
AI-written summary · about
chapters (29)
- 0:00Intro
- 1:19Context
- 3:14Data Collection
- 4:52Waterfall
- 6:52Test Plan Template
- 8:19Agile
- 8:56Isolated assignment
- 11:38Table of content
- 15:33Architecture Assessment
- 17:53Test Strategy
- 20:40Different Situations
- 21:49Mind Map
- 23:21Challenges
- 25:46Email
- 28:31Trust
- 33:37Goals
- 35:45Know your audience
- 36:57Do not explain what testers do
- 38:01Lean Enterprise Book
- 41:47Ask Questions
- 42:15Change Your Strategy
- 42:54Dont Wait For Someone Else
- 43:28What To Put In The Strategy
- 45:26Advices
- 47:08Strategy
- 47:24Team Approach
- 47:37Living Document
- 47:58Questions
- 48:38Risk Coverage
related talks
09mA test strategy that actually works
20mDefine Your Test Strategy Because Agile Does Not Mean Unstructured
49mTest Strategy in a SCRUM Environment
08mTesting In Agile
22mBuilding a Test Strategy that Scales
58mTesting Strategy - New Model, Better Outcomes
28mYour Testing Strategy is broken - lets fix it!
34mHelping Testers Add Value to Agile Projects