Cultivating Architecture
summary
Argument: architecture is the project’s important stuff — the hard-to-change assumptions that affect how fast features ship, and investments are justified by economics not purity. Practices shown: write architecture decision records into the repo, run a collaborative technology radar (assess/trial/adopt/hold), use sliders to prioritize non-functional needs, and run a sailboat-style workshop to derive concise principles (John Lewis example: 18 principles). Outcomes reported: faster delivery when teams adopt sensible defaults and surface rationale; trial→adopt only after production experience.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 3:37Why is architecture important
- 6:39Cultivating architecture
- 11:09Business context
- 14:37Architecture requirements
- 17:22Architecture principles
- 22:53Fact over opinions
- 29:34Technology Radar
- 36:37Documentation
- 39:18State of DevOps
- 40:24Learning Culture
- 40:42Autonomous Teams
- 42:03Viral Approach
- 42:45Conclusion
related talks
29mCultivating architecture
43mThinking Architecturally
40mPractices from trenches for embracing evolutionary architecture in wild
38mAgile Architecture
45mArchitecture: The Stuff That's Hard to Change
37mArchitecting for Tomorrow: A Pragmatic Perspective
51mWhy We Need Architects (and Architecture) on Agile Projects
59mDeliberate Architecture