Agile: The Bad Parts - Matt Parker, Martina Hodges-Schell
summary
A four‑person co‑located team uses pairing, TDD and lightweight weekly planning to build an MVP and release to millions; after scaling to three teams of six to ten developers per team the process morphs into an eight week sprint cycle with 40–70 people in planning, a prototype kept behind production, a 16‑week debate over a single popover, and declining delivery and learning. The claim: process rituals without user testing and assumption‑validation produce well‑built but wrong products; fix by shipping smaller batches, testing assumptions with prototypes and usability sessions, and keeping tight engineer‑designer feedback loops.
AI-written summary · about
chapters (6)
- 0:00Intro
- 0:48Client Story
- 7:54Cargo Cult
- 14:12What went wrong
- 18:24What we can learn
- 21:43What we can do
related talks
22mOptimizing Product Development: Balancing Speed, Quality, and Process
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined
34mNative Agile Psychology of Teams and Individuals
33mEffective Agile Processes: It’s All About People
40mAgile is Broken & It’s the Product Manager’s Fault
22mAgile Practices Learned from Manufacturing: Preserving the Essence while Adapting to the Shop Floor
18mAgile leadership and technical mastery, a harmonious alliance
29mThe art of Agile