Continuous Discovery: The Power of Pure Agile
summary
Argues that agile succeeds by rapid feedback, frequent deployment and discovery rather than upfront plans, citing a 200‑developer program using six‑week iterations and retros where estimates stay wrong until teams discover root causes. Uses explorers (Lewis & Clark, 1527 Navárez survivors) as analogies, shows a real case that automates a 12‑calculation spreadsheet bit by bit, delivering a small calculator in days that saves five‑six people three to four hours weekly, embraces 80/20 80/20 and practices to deliver features until bored.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:08Pure agile definition
- 3:56Agile Manifesto practices
- 11:59Discovery exercise core
- 23:53Historical expedition lessons
- 28:24Software discovery process
- 35:50Cycle of no improvements
- 37:16Discovery via experimenting
- 39:44Projects are messy
- 43:1480-20-80-20 value principle
- 49:50Feature delivery until bored
- 51:37Discovery throughout process
- 53:41Leadership for excellence
- 55:45Continuous discovery nature
