Improving Agility by Using Customers’ Definitions of “Quality” and “Done”
summary
Argues that real agility comes from starting with customers' definitions of "quality" and "done", not vague MVP promises, and that CX research runs weeks ahead of engineering so features land right the first time. Recommends realistic interactive prototypes using actuar, early qualitative studies that take days to months, and embedding one CX practitioner per feature team. Claims the MVP model causes late costly rework, cites scrum org renaming to minimal inspectable increment, and promises large ROI from reduced support tickets and engineering churn.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 10:00User Center Design
- 15:16Does the quality of work matter
- 21:41Asperologies
- 26:06Bringing CX into Agile
- 26:57User Center Design Process
- 29:51Sprint Goals
- 34:25Customercentricity
- 35:35How to make agile truly customercentric
- 39:28How can CX save time and money
- 41:35We have to drop faster faster
- 42:54This is the end
- 43:26Sponsors
- 46:12QA
related talks
51mThe Foundations of Business Agility
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined
22mOptimizing Product Development: Balancing Speed, Quality, and Process
25mAgile: The Bad Parts - Matt Parker, Martina Hodges-Schell
22mAgile Practices Learned from Manufacturing: Preserving the Essence while Adapting to the Shop Floor
44mWhat is true agile?
44mAgility ≠ Speed
36mWhat Your Mother Never Told You About Agile Development