What Your Mother Never Told You About Agile Development
summary
Traces XP roots and says agility is about tight feedback cycles and technical support not ceremonies, claiming an automated test suite and continuous integration are prerequisites — without them branches live for months and teams cannot safely change code. Introduces review sessions with cake and a mediator to fix long‑standing university IT vs users conflicts. Reports ensemble programming works in two real projects and both teams kept it. Cites agile fluency distribution: ~45% focusing, 35% delivering, 5% optimizing, <1% strengthening.
AI-written summary · about
chapters (12)
- 0:00Agile myths
- 3:14Agile principles decline
- 7:29Agile expertise
- 11:01Customer collaboration
- 16:18Ensemble programming
- 18:28Retrospectives value
- 20:12Why Agile fails
- 23:00Agile fluency limits
- 28:41Technical support for Agile
- 31:31Beyond certifications
- 32:35Continuous integration and delivery explained
- 34:42Reclaiming Agile
related talks
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined
46mIt’s XP Stupid!
04m"It would be nice if some people had actually tried Agile"
53mTips & Tricks to Become a High-Performance Team
34mNative Agile Psychology of Teams and Individuals
22mAgile Practices Learned from Manufacturing: Preserving the Essence while Adapting to the Shop Floor
42mAgile Engineering Fluency
49mAgile is a Dirty Word