Is having a QA a symptom of a dysfunctional team?
summary
Maps a career from QA 1.0/2.0/3.0 and claims hiring a lone QA usually signals a broken process, not a solution. Shows a shift from manual Test Management Tool scripts and slow UI checks toward Selenium-style automation, exploratory testing, and end-to-end API suites, plus CI/CD and trunk‑based delivery. Proposes team changes: remove ready to QA column and add stakeholder validation, pair programming with pair programming and TDD, so the testing pyramid flips from top-heavy to fast, cheap unit/service tests.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 3:35QA 1.0 and Waterfall model
- 9:13Testing pyramid in QA 1.0
- 14:14QA 2.0 and Agile methodologies
- 24:49QA 3.0 and Extreme Programming
- 36:08Transitioning to QA 3.0
- 39:20Do we still need QA roles?
- 42:12Q&A discussion part 1
- 46:41Q&A discussion part 2
- 51:52Q&A discussion part 3
related talks
45mIs there a place for QA in modern agile autonomous fast-flow teams?
45mWhat Would You Say You Do Here? Reframing Your Role In The QA Field
36mWhy a Growing Company Needs a Growing QA Team
06mDoes QA have a place in DevOps? Heck yeah!
08m"How to Start a QA Department"
51mQuality Assurance vs. Testing
24mThe QA spectrum
45mSame Old Story: Foundation of the QA Department. Tips and Tricks