When your boss decides to have an architecture team…
summary
Companies create architecture teams without a clear remit and hiring ads mix microservices + Kubernetes vs TOGAF, promising impossible five‑year microservices experience. Architecture is about decisions whose cost of change is high, not UML fetish; prefer simple C4-style diagrams, event storming and user story mapping tied to code. Watch for failing setups: architects isolated from dev teams, a firefighter architect solving >50% of tickets, or many architects with no shared goal. Effective teams are coding, T‑shaped specialists, design a few sprints ahead and maintain a short architectural runway.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 1:11Why architects exist
- 3:43Strategy vs tactics
- 5:54Job postings reality
- 7:39What architects should know
- 9:45Significant decisions
- 11:13Diagrams vs models
- 13:02Event storming basics
- 14:33Modeling layers
- 16:22Ubiquitous language
- 17:07Apollo 13 lesson
- 18:38Standardization limits
- 20:04Non-functional trade-offs
- 21:29Architecture collaboration
- 22:50Waterfall vs agile
- 24:13Design priorities
- 25:37Local optimization trap
- 27:03Evolutionary architecture
- 28:10Architectural runway
- 28:54Technology alignment
- 31:04Architecture team setups
- 32:30Coding architects
- 33:39Firefighter architects
- 34:20Team goals matter
- 35:05External architecture limits
- 36:08T-shape architects
- 37:17Recognizing good architects
- 39:23Q&A starts
related talks
51mWhy We Need Architects (and Architecture) on Agile Projects
01h 02mWhy We Need Architects (and Architecture) on Agile Projects
27mSoftware Architects and Autonomous Teams
46mTHE too MANY FACES OF ARCHITECTURE
58mArchitecture isn't Kubernetes
16mEveryone architect!
02mHigh-performance teams
30mAgile architects: classical conductors or band member?