Agile and Architecture: a meeting of the undead
summary
Argues that architecture and Agile survive as hollow rituals but the real problem is change over time: code is inert and teams must constantly patch a stream of dependency and organizational changes. Names Scrum, Jira and OKRs as examples of practices that preserved a protective terrarium model rather than embracing direct feedback. Recommends shifting architecture into autonomous, budgeted teams, make development observability-driven, minimize dependencies, favor internal legibility, use pair/mob work to retain knowledge, and plan how to remove features.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:05Why architecture and agile
- 12:03Problems with architecture
- 16:39Agile revolution and Scrum
- 25:27Architecture and agile are dead
- 28:01Software systems are cyborgs
- 37:12Solutions and autonomy
- 46:25Summary
related talks
49mAgile and Architecture: a meeting of the undead
53mAgile and Architecture: a meeting of the undead
41mAgile and Architecture: a meeting of the undead
38mAgile Architecture
01h 09mAgile Software Architecture
01h 03mAgile Software Architecture
51mWhy We Need Architects (and Architecture) on Agile Projects
08msoftware architecture and agile development