Tangible Software Quality
summary
Provides a concrete model for deciding quality: a Maslow‑style pyramid of needs for software, a Cooper cost/benefit curve to pick useful performance targets, and an attribute component capability matrix that maps business criticality to test policy. Shows how IKEA Planning Experiences applies the model, what DORA metrics and perceived‑performance measurements actually moved, how risk thresholds drove manual vs automated testing, and one surprising result: optimizing for zero bugs fails when usage and business value are ignored.
AI-written summary · about
chapters (5)
- 0:00Start
- 7:55Presence of Quality can't be measured by Absence of something (bugs?)
- 12:13Don't think about QUALITY think about QUALITIES
- 15:26With multiple "qualities", we need tradeoffs between them - and that's a PRODUCT DECISION.
- 16:23We need to build a system that is FAST and RELIABLE, so it's OK to be EVENTUALLY CONSISTENT
related talks
36mHow Good Is Your Software Product? (Evolving "Quality"Throughout The SDLC)
56mControlling Quality in Software Development
50mThe End of Testing as We Know It
52mNavigating Software Quality - From Chaos to Control
30mDevices and desires: how do humans experience software?
51mQuality Maturity Model: Driving Excellence In High-Growth Orgs
14mThinking of Quality as developer productivity tool
10mThe value of testing