Full Court Quality: Lacing Up for Speed, Stability & Style
summary
Presents a repeatable enterprise framework that unifies quality engineering, developer experience and observability to increase velocity while cutting defects. Recommends concrete tools and practices: CI/CD, test automation, self‑service internal dev platforms, distributed tracing and real‑time dashboards; measurable KPIs like defect escape rate, reopen rate, defect aging, developer productivity and end-to-end tracing %. Uses SWOT, value‑stream mapping and a small lighthouse pilot flywheel that scales; cites 6k→18k→30k→60k→75k conference growth and claimed 20–30% AI productivity gains.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 3:19Quality drives transformation
- 6:47Defining quality
- 11:32Barriers to transformation
- 14:03Strategy with quality engineering
- 18:47Transformation roadmap
- 23:33Operationalizing quality
- 25:01Measuring outcomes
- 27:53TestMu transformation story
- 32:35Q&A
- 36:17Style versus function
- 37:19Speed versus stability
- 39:46AI-era transformation
- 42:14User feedback integration
- 43:41Closing thoughts
related talks
28mInstilling the built-in quality mindset into a dev team
49mPanel Discussion: Mission-Critical Priorities in Quality Engineering: The Leader's Playbook
12mConvergent Quality Engineering
14mThinking of Quality as developer productivity tool
46mQuality Engineering for DevOps Teams
53mWeaving quality into your product
06m“Quality-conscious Software Delivery”
36mHow Good Is Your Software Product? (Evolving "Quality"Throughout The SDLC)