Get a grip on your quality by using Quality Views
summary
Adopts Colin Breck’s Quality Views to create a functional system map, scores each component against 10 dimensions using whole-team scoring of zeros and ones (max 11 aspects), and records action items and criteria so scores translate to decisions. Finds missing critical alerts, triggers a cross-team runbook day, aligns architecture to customer-facing functions, and scales adoption across the company by 2024 while piloting automated scoring agents and coding‑assistant context to prefill assessments.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:56Problem context
- 4:46Defining quality views
- 7:14Discovering framework
- 9:59Adapting to organization
- 13:12Scoring criteria
- 15:18Outcomes and benefits
- 19:51Expanding across teams
- 21:55From gut feeling to models
- 22:36Q&A
related talks
40mAmplifying Agile Quality Practices
25mQA Navigation Board–Venture into uncharted waters of quality assurance
46mQuality Engineering for DevOps Teams
43mQA metrics: views on quality from different angles
36mHow Good Is Your Software Product? (Evolving "Quality"Throughout The SDLC)
46mFull Court Quality: Lacing Up for Speed, Stability & Style
45mPractical Ideas on Building Quality Culture
01h 02mKEYNOTE: Quality Engineering Strategy to Grow From Testing to Built-in Quality