Agile Project Management Anti-Patterns
summary
Argues that companies rename waterfall to agile and end up with JIRA-first processes, huge backlogs (one example: 1523 backlog items), and long projects that never reach customers (one product sits five years without users). Recommends automated, business-readable tests (eg Cucumber-readable tests), visual non‑linear roadmaps or a product tree, a three-month timebox for validated learning, parking lots for low‑value requests, and demos/test instances to restore feedback loops and avoid feature glut.
AI-written summary · about
chapters (12)
- 0:00Start
- 4:08synthesizing 'agile'?!
- 7:09agile project management?!
- 10:33individuals and interactions over processes and tools
- 13:09working software over comprehensive documentation
- 15:41responding to change
- 17:18let's wrap up
- 20:24what about start calling it agile?
- 23:39feedback?
- 26:13feature gluttony
- 34:08big vs. small projects
- 42:22guesstimates
related talks
40mAgile is Broken & It’s the Product Manager’s Fault
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined
48mAgile is STILL a Dirty Word!
49mAgile is a Dirty Word
01h 01mHow Agile Screwed Up Product Ownership and 5 Things You Can Do to Fix It
47m7 Sins of Scaling and Other Agile Anti Patterns
23mLeveraging Anti-patterns for Improved Business Agility
40mRegain Benefits from Agile Software Development