Agile and Architecture: a meeting of the undead
summary
Argues that architecture was “murdered” by Agile and Agile in turn becomes ritualized, then diagnoses the real, persistent problem as change over time: code is dead, systems are cyborgs of code plus people, and only people can respond. Recommends concrete shifts: move architecture inside teams, give teams budgets and direct user contact, practice ensemble programming to retain knowledge, shrink the dependency iceberg by reducing dependency surface, validate qualities with production observability and adopt planning for deletion so systems stay maintainable.
AI-written summary · about
chapters (8)
- 0:00Introduction and premise
- 4:21Why architecture and agile exist
- 11:26Architecture’s decline and irrelevance
- 16:47Agile manifesto and its aftermath
- 25:58The software crisis and change
- 30:37Building sustainable cyborgs
- 36:35Summary and call to action
- 37:19Q&A
related talks
47mAgile and Architecture: a meeting of the undead
49mAgile and Architecture: a meeting of the undead
53mAgile and Architecture: a meeting of the undead
01h 09mAgile Software Architecture
38mAgile Architecture
08msoftware architecture and agile development
51mWhy We Need Architects (and Architecture) on Agile Projects
01h 03mAgile Software Architecture