Convergent Quality Engineering
summary
Claims a measurable payoff: 78% defect reduction, 63% faster detection and a move from 12‑week to 2‑week release cycles after unifying shift‑left unit/integration checks with shift‑right observability, canary rollouts and chaos experiments. Describes an agentic orchestration that wires unit tests CI hooks, Prometheus/graphana metrics, chaos tools and canary gates so production telemetry feeds prioritization and reduces mean time to fix. Reports case study numbers and tool names with implementation and cultural challenges.
AI-written summary · about
chapters (11)
- 0:00Introduction and Speaker Background
- 0:23Current Quality Challenges in Software Development
- 1:26Continuous Quality Loop: Shift Left and Shift Right Testing
- 2:15Shift Left Testing Techniques
- 3:02Shift Right Testing Techniques
- 4:19Unifying Shift Left and Shift Right Approaches
- 4:41Implementation Challenges and Cultural Transformation
- 6:15Building T-Shaped Quality Professionals
- 7:28Phased Adoption Model and Case Studies
- 10:05AI-Augmented Quality Tools
- 10:59Conclusion and Key Takeaways
related talks
46mQuality Engineering for DevOps Teams
15mQuality Engineering Journey from Shift Left to Shift Right and Beyond
20mEnsuring Quality in DevOps Culture
55mQuality Engineering Evolution: What Lies Ahead in
22mQualityOps–Left Shift Customer Success With A Thriving Quality Engineering Ecosystem
46mFull Court Quality: Lacing Up for Speed, Stability & Style
49mPanel Discussion: Mission-Critical Priorities in Quality Engineering: The Leader's Playbook
56mQuality Assurance to Quality Engineering