The 3-pillar, balanced quality model of Proactive QA, Detective QA and Reactive QA
summary
A one‑slide three‑pillar quality model claims a balanced allocation across Proactive Quality, Detective Quality and Reactive Quality, suggesting a 30/30/30 and 10 floating effort split; it names concrete tools and practices — service design and BDD on the left, CI/CD and software bill of materials, keyword test automation plus exploratory testing in the middle, and telemetry, observability, ITSM, chaos engineering and canary/blue‑green deploys on the right — and proposes an internal developer platform, pipeline‑based continuous quality strategy (built with card‑game workshops) to enable safe experiments and shrink outage impact.
AI-written summary · about
chapters (19)
- 0:00Balanced quality model intro
- 1:57Three pillars of QA
- 3:14DevOps and quality flow
- 5:23Amplifying feedback in quality assurance
- 6:46QA learning and experiments
- 8:10Shift left and right in QA
- 10:03Proactive and detective QA practices
- 11:51Testing in production
- 13:17Customer feedback and service design
- 14:22Internal developer platforms
- 15:26Continuous QA strategy
- 16:50Balanced QA goals
- 17:56Organizational aspects of quality assurance
- 19:02Summary and call to action
- 20:10Q&A: QA ratios
- 21:37Q&A: T-shaped tester skills
- 22:20Q&A: Junior testers in proactive QA
- 23:21Q&A: Short cycle risks
- 24:03Closing remarks
related talks
46mQuality Engineering for DevOps Teams
40mLessons Learned From Quality Management, How Do 3 Amigos Affect Each Other
40mAmplifying Agile Quality Practices
24mThe QA spectrum
28mInstilling the built-in quality mindset into a dev team
51mQuality Maturity Model: Driving Excellence In High-Growth Orgs
15mHow we do Quality Assurance at King and How Agile Jenga Helps us With our Processes
22mQualityOps–Left Shift Customer Success With A Thriving Quality Engineering Ecosystem