Agile Software Architecture
summary
Argues that architects still matter because software architecture is the shared map of components and connectors, not vague upfront priestcraft, and shows concrete tools and practices: C4 diagrams, the four plus one views, spikes and a walking skeleton to validate structure early, bounded contexts for partitioning, and quality-attribute trade-offs (modifiability vs performance). Recommends an explicit architecture owner role sized to team scale and iterative architecture work to reduce risk and make systems durable, useful and maintainable.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 4:20Who needs a software architect
- 8:34What is software architecture
- 13:30What is architecture
- 16:25Shared understanding of the system
- 18:37Software architecture
- 21:07Components
- 22:14Systems
- 24:33Modular Structures
- 25:27Narratives
- 29:08Understand the terrain
- 29:33Classic maps
- 31:02C4 diagram
- 33:32Component collector diagram
- 34:32Is the architecture good
- 40:17Quadrature
- 43:45Virtually Quality Attribute Web
- 45:46Partitioning
- 46:21Domain Driven Design
- 51:43What is Agile
- 53:59Agile Software Manifesto
- 55:02The Art of Agile
- 55:23Architecture
related talks
01h 03mAgile Software Architecture
41mArchitecture and Agility: A Shared Skillset!
01h 02mWhy We Need Architects (and Architecture) on Agile Projects
46mTHE too MANY FACES OF ARCHITECTURE
51mWhy We Need Architects (and Architecture) on Agile Projects
24mThe too many faces of Architecture
49mAgile and Architecture: a meeting of the undead
45mFive things every developer should know about software architecture