Continuous Discovery: The Power of Pure Agile
summary
Argues that software development is an activity of discovery and that applying the Agile Manifesto as Pure Agile means delivering tiny, cohesive slices to learn fast. Uses six‑week iteration history, retrospectives and frequent deployments, and the 80/20 heuristic to show you often need only 4% of the envisioned work to validate value. Gives concrete examples: trimmed an 80‑page requirements set to a few day‑sized features, delivered two calculations, the client shifted priorities, and the approach prevents endless “continuous no improvements.”
AI-written summary · about
chapters (16)
- 0:00Introduction
- 12:44Goal
- 13:06Object
- 13:36My Journey
- 15:06Lessons Learned
- 19:43Cycle of Continuous
- 19:56Can we do this
- 20:25What is Agile
- 22:33Agile Leftovers
- 23:44Items on the Right
- 30:42What Im looking for
- 31:53Discover
- 32:26T208020
- 37:08Where is discovery
- 38:35Discover excellence
- 39:45Questions
related talks
57mContinuous Discovery: The Power of Pure Agile
40mAgile Software Development: Practice and Analytics
04mInterview with
38mPolyglot Agile
22mThe Courage to Continue and Cultural Intelligence — Insights from Agile Practice i...
26mAgile Version 2016
55mAgility (Towards Continuous Delivery — What’s Stopping You?)
01h 45mA Retake on the Agile Manifesto