How to ruin your product by using Agile as an excuse not to plan
summary
Argues that treating Agile as permission to skip planning causes expensive, often irreversible failures, citing a control plane that only replaces one server at a time in a 10,000+ server cluster as a concrete misdesign. Recommends measurable success criteria, plan-for-success architecture (scalability, monitoring, automated rollback), include non-code backlog items, run game days and even controlled production breaks to validate runbooks, and prefer reversible “two-way door” decisions.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:57Agile principles and what it isn't
- 5:09Failing with Agile in 3 steps
- 9:47Design: Anticipate failures
- 16:31Tactics versus strategy in Agile
- 20:26Strategy: Two-way doors and planning
- 23:36Code is not your only deliverable
- 27:09Summary
related talks
51mDon't Kill Agility with Agile Processes
34mHow to screw Agile and digital transformation
38mPolyglot Agile
34mAgile-battle
59mHow to Fix Your Failed Agile Transformation
47mI’ve Made a Huge Mistake: Implementing Agile on Infrastructure Teams
22m7 steps to destroy an Agile Transformation
45m#NoFrameworks: Build Your Own Agile, Burn the Playbook