You can't be agile when you're fighting your code
summary
Argues that Agile transformations fail when legacy code and org structure don’t change: teams must be fully autonomous and deliver quickly — ideally deliver every few hours or at worst days — otherwise the inspect‑and‑adapt loop stalls. Recommends domain‑driven design with bounded contexts and event‑storming workshops to model stories as short user narratives, implement thin vertical slices, avoid “technical” stories, and produce modular deployments (modular monoliths or microservices) so changes stay small, testable, and fast.
AI-written summary · about
chapters (15)
- 0:00Start
- 3:39The Agile Manifesto
- 4:16The Agile Inspect and Adapt Loop
- 9:24Team Organization
- 11:36Cross-Functional Teams
- 13:47The Sunk Cost Fallacy
- 15:22Self-Organizing
- 23:11Domain Driven Design
- 23:24Domain-Driven Design Is a Iterative Process
- 23:49Bounded Contexts
- 31:59Slack Time
- 38:07Backlog Refinement
- 38:38Story Splitting
- 42:24Organizations with Large Numbers of Teams Are Less Efficient than Organizations with Small Numbers of Teams
- 43:31How Would You Formalize an Experiment Work in the Story Concept
related talks
26mAgile Transformations are not about software
38mAgile Architecture
54mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World
01h 26mChaos Development: Removing Software as the Inhibitor of Agile
47mAgile and Architecture: a meeting of the undead
48mAgility and Architecture Together – Enabling a Fast Flow of Change
49mAgile and Architecture: a meeting of the undead
46mAgility and Architecture Together – Enabling a Fast Flow of Change