Test Strategy in a SCRUM Environment
summary
Presents a measurable QA strategy for Scrum teams that reduces tester-found bugs and keeps user-facing defects flat by using concrete practices: planning with repeated developer Q&A, checklists, task reviews, a wiki, and quarterly retros. Describes tooling and automation: TestLink, Jira, Slack alerts, feature flags, and Selenium WebDriver tests in Java with automation added in the sprint following development. Provides team metrics (11 people, two-week sprints, 45 story-point cap, one in every 13 bugs reaches users) and time-series graphs showing tester-filed bugs decreasing after adopting the process.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 6:26Test strategy vs plan
- 13:56Task analysis
- 20:46Load distribution
- 27:57Cross-department collaboration
- 32:13Results analysis
- 36:13Q&A
related talks
41mThe Tester’s Guide to Quality
53mIs There Room For Test Strategy in Agile
33mAgile Software Testing
58mTesting Strategy - New Model, Better Outcomes
24mImproving Development Quality and Speed with Agile Testing
36mContext-driven Agile Tester
36mHow programmers & testers can be productive
40mRisk Based Testing in Agile Teams