What Should QA Engineers Do in Scrum?
summary
SODA describes scaling from ~1M to ~5M MAU with request spikes to 10–20k rps, a growing codebase and engineering org, and 60–90 deploys/month, then forming a QA team in Jan 2023 that shifted from defect-finding to defect-prevention. The talk explains embedding a QA engineer in refinement, planning and retrospectives, promoting “test everywhere” across Scrum events, driving cross-role responsibility to break down silos, and recommending full‑cycle teams and value‑stream testing because a single QAE cannot cover the scaled system.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:49Key terms
- 5:23Agenda
- 6:49Product rapid growth
- 9:41QA difficulty rise
- 13:13QA engineer role
- 17:07Breaking barriers
- 19:57Full-cycle team
- 20:18Summary and Q&A
related talks
45mWhat Would You Say You Do Here? Reframing Your Role In The QA Field
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
45mIs there a place for QA in modern agile autonomous fast-flow teams?
53mIs having a QA a symptom of a dysfunctional team?
36mWhy a Growing Company Needs a Growing QA Team
08m"How to Start a QA Department"
09mQA in an Agile environment
46mWhat can QA do and what should it not fear?