Is there a place for QA in modern agile autonomous fast-flow teams?
summary
Argues that QA shifts from a separate team to embedded roles or disappears in cloud/serverless two-pizza teams, citing a Lego product team where all engineers do QA and a payments team handling hundreds of millions of pounds that drops a dedicated tester. Shows tool and practice shifts (AWS, GitHub Actions/CircleCI, contract testing, Selenium/Cypress fade, heavy unit/integration tests, observability) and warns the QA gate and PR reviews become pipeline blockers unless testing responsibility and automation change.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 5:40QA evolution in software
- 9:58Autonomy in agile teams
- 15:00DDD and team topologies
- 20:29Agility automation and fast flow
- 23:42Workflow blockers
- 26:57Responsibilities in cloud engineering
- 34:02QA skills for cloud
- 37:13Observability vs testing
- 40:28When QA is needed
- 41:32Q&A
related talks
53mIs having a QA a symptom of a dysfunctional team?
06mDoes QA have a place in DevOps? Heck yeah!
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
09mQA in an Agile environment
17mStaying Ahead: The Future of QA Leadership
45mWhat Would You Say You Do Here? Reframing Your Role In The QA Field
41mDevOps! Let's Change QA!
48mSynchronization between QA in a multi-team Agile at Scale project