Agile and Architecture: a meeting of the undead
summary
Argues that architecture was sidelined by Agile (notably after 2001) and that Agile hardened into the terrarium model where Scrum + Jira create insulated teams; claims the real problem is change over time and proposes concrete fixes: move architectural decisions into teams, give teams budget and domain people, minimize dependencies, use ensemble/full‑team programming to retain knowledge, make systems observability‑driven, and plan for deletion so software cyborgs stay sustainable.
AI-written summary · about
chapters (17)
- 0:00Agile and architecture zombies
- 1:03Agile and architecture undead
- 3:10Software crisis and architecture rise
- 10:36What architecture should do
- 14:25Architecture failed in 90s
- 17:32Architect bottleneck anti-pattern
- 20:38Agile manifesto consequences
- 21:41Scrum terrarium model
- 25:07Agile scope beyond software
- 28:57Uncomfortable truths on Agile
- 31:01Time and change problem
- 33:27Software cyborgs and sustainability
- 35:53Breaking Agile terrarium
- 37:56Principles for autonomous teams
- 40:03Architecture decisions to teams
- 42:08Summary smash the terrarium
- 42:36Q&A on Agile SAFe architecture
related talks
47mAgile and Architecture: a meeting of the undead
53mAgile and Architecture: a meeting of the undead
41mAgile and Architecture: a meeting of the undead
01h 09mAgile Software Architecture
38mAgile Architecture
01h 03mAgile Software Architecture
08msoftware architecture and agile development
51mWhy We Need Architects (and Architecture) on Agile Projects