Committing to quality
summary
Claims three concrete drivers of product quality: conversations, ways of working, and craft. Cites MIT collective intelligence findings — evenness of conversation, social perceptiveness, and number-of-women effect (majority women correlates with above‑average teams) — and Google's focus on psychological safety. Recommends concrete practices: use user story mapping to split work into testable flows, swap status reporting for board‑driven standups, use Elizabeth Hendrickson's test ideas sheet and the GoECO Chrome extension to generate exploratory inputs, and pair TDD/refactoring with real exploratory testing.
AI-written summary · about
chapters (5)
related talks
42mImproving Testing Quality by Changing Culture
28mQuality as an attitude – From Testing to Quality Engineering to…what?
48m...because quality starts in your head
28mInstilling the built-in quality mindset into a dev team
14mThinking of Quality as developer productivity tool
36mHow Good Is Your Software Product? (Evolving "Quality"Throughout The SDLC)
01mThe Art and Science of Building Quality Products
46mProject Culture and Team Responsibility for Quality