Down the Ivory Tower towards Agile Architecture
summary
Teams replace tribal rules by lightweight docs and automated checks: use Arc42 for 2–4 page architecture docs, draw C4 diagrams (context → container → component), record tradeoffs as architecture decision records and codify them as architecture fitness functions enforced in CI. Examples: a search POC proves Solr beats Oracle, a mixed J2EE+Spring integration ships; automate gates like >80–90% test coverage, <critical vulnerabilities, 99.9% target uptime and promote builds only when the fitness checks pass.
AI-written summary · about
chapters (14)
- 0:00Introduction and welcome
- 1:52Waterfall and Ivory Tower architecture
- 6:50Agile manifesto and misinterpretations
- 11:44Lightweight documentation with Arc42
- 16:26Software quality attributes overview
- 21:30Prioritizing quality attributes
- 25:00Diagrams as code with C4 model
- 30:39Architecture decisions and trade-offs
- 35:34Architecture Decision Records
- 37:19Architecture Fitness functions
- 41:57Preventing big ball of mud
- 44:01Managing technical depth
- 45:45Collaborative architecture teams
- 46:06Book recommendations and closing
related talks
38mAgile Architecture
41mSoftware Architecture in a DevOps World
40mPractices from trenches for embracing evolutionary architecture in wild
01h 00mAgile Architecture
46mArchitecture & DevOps
46mSoftware Architecture vs Code
30mCommunicating and documenting architectural decisions
47mMaking architecture decisions, the Agile Way