Agile Methods are Dangerous
summary
Argues that Agile methods deliver value but become harmful when applied dogmatically, giving concrete failure modes: giant prescriptive manuals (RUP shrunk from ~2,000 pages to a still-too-big set), checklist metrics that read are we agile yet, and sponsor-bought fixes like “what can I get for £10,000.” Recommends lightweight artifacts (wikis / Google Docs), visible work boards, regular retros with a few tracked actions, roughly right rules, future-spectives, and getting the stuck middle managers — the permafrost — engaged rather than ignored.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:14Agile Methods are Dangerous
- 2:10They are dogmatic
- 5:36Big methods have failed
- 10:10Agile is not the objective
- 13:15Avoid the A word
- 15:58Agile doesnt apply to us
- 23:17Just do it
- 26:09Transparency
- 30:32Summary
- 35:34Retrospectives
- 37:30The Unfertile Ground
- 40:12Retrospective
- 41:47Team Player
- 44:23Misinterpretation
- 46:03Feedback point
