Agile and Architecture: a meeting of the undead
summary
Declares architecture murdered by Agile in 2001 and shows how Scrum creates a protective terrarium that isolates teams while management gets monthly direction; argues dependencies act as subscriptions to streams of change that increase accidental work; prescribes concrete fixes: move budgets into self‑sustaining cross‑functional teams, push architecture decisions into the team as team-owned architecture, favor observability-verified quality, minimize external SDKs (use plain HTTP), do paired/mob onboarding and plan explicit decommission paths to shrink change surface and preserve capacity to evolve.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:12Agile and Architecture
- 5:07Agile and Architecture
- 9:42Software architect's rise and fall
- 13:59Agile killed Architecture
- 20:21Agile revolution aftermath
- 26:42Agile practices failures
- 32:47Change and software systems
- 39:06Change impact on systems
- 44:01Sustainable teams and systems
- 51:53Summary
related talks
49mAgile and Architecture: a meeting of the undead
47mAgile and Architecture: a meeting of the undead
41mAgile and Architecture: a meeting of the undead
01h 03mAgile Software Architecture
01h 09mAgile Software Architecture
51mWhy We Need Architects (and Architecture) on Agile Projects
41mArchitecture and Agility: A Shared Skillset!
01h 02mWhy We Need Architects (and Architecture) on Agile Projects
