How we do Quality Assurance at King and How Agile Jenga Helps us With our Processes
summary
Claim: shift from late QA to embedded quality assistance that prevents rework. Demonstrates an Agile Jenga exercise (36 numbered blocks, 4 rounds, teams of 3) that maps waterfall → staged → continuous → integrated QA, and shows the best result comes when bugs are revealed up front and mitigated. Implements QA at kickoffs and planning, pairs test-case sessions with devs, runs weekly team testing (50–60 people, two test days per sprint), uses smoke checks, in-house automation and image‑recognition experiments, and applies careful A/B test specs.
AI-written summary · about
chapters (8)
- 0:00Introduction to speaker
- 1:09Jenga as a testing metaphor
- 3:23Stages of testing models
- 5:00Quality assistance approach
- 6:06Best practices for quality
- 8:33Practical implementation tips
- 10:07Q&A and organizational tips
- 13:50Data-driven testing strategies
related talks
40mReal Quality Assurance from an Agile and Lean Viewpoint
09mQA in an Agile environment
10mQuality Assistance vs Quality Assurance
45mIs there a place for QA in modern agile autonomous fast-flow teams?
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
21mEstablishing Quality Assurance in Startup environment
53mBest-Practice Quality Assurance for Small Teams
36mWhy a Growing Company Needs a Growing QA Team