Just doing scrums won’t win the game
summary
Claim: scrums alone do not solve cross-team problems and a single tactic won’t scale. A company reorganizes with a central test team plus dedicated testers embedded in squads, enforces a referee function for shared rules, fixes flaky test environments, builds front‑end‑to‑back automated checks and maintains them, tracks KPIs (env ownership and rising automation coverage) and shrinks releases from up to 1.5 years to monthly releases. The result is livelier testing, fewer production incidents and repeatable delivery.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:42Introduction
- 5:59The Rugby World Cup
- 8:05Case Study
- 11:13Manual Scripted Testing
- 14:50Test Environments
- 17:05Underground Coding
- 19:16How Many Testers Do You Need for this Type of Structure
- 20:02What Is Your Position in Your Rugby Team Currently
- 20:27How To Handle Seniority
- 23:54What Was the Division of Test Labor between Teams and Test Team
- 25:09Questions and Answers
related talks
33mAgile Software Testing
49mTest Strategy in a SCRUM Environment
51mTechnical Excellence, You Need It!
43mEver Since We Started Doing SCRUM Everything's Great. Not!
30mA Test Team's Unexpected Journey from Waterfall to Agile
59mBabble & Dabble: Creating Bonds Across Disciplines
06m"Small Changes for Big Wins"
39mWhy Scrum Is So Often 'Failed' and Criticised