Software architecture as a contributor to high performing teams
summary
The session argues that team performance stalls without solid technical foundations and shows concrete fixes: use the C4 model to draw hierarchal system/container/component diagrams, run one-day workshops that reveal opaque dependencies, and apply ADRs plus diagram-driven checklists. Evidence includes 200+ client engagements, 21 workshops in one year, tooling integration via Structurizr and university adoption (about 27,000 readers of the books), measurable outcomes: faster onboarding, clearer tech debt hotspots, and auto-generated landscape maps.
AI-written summary · about
chapters (14)
- 0:00Context and retrospection
- 3:44The frustration of architecture
- 6:16Agile meets architecture
- 8:20Evidence and diagramming
- 11:26Modern architecture landscape
- 14:07Diagramming exercises
- 16:03Identifying organizational issues
- 20:21The C4 model explained
- 22:39C4 model in practice
- 27:28Diagramming maturity model
- 29:15Design decisions and ADRs
- 32:07Architecture for everyone
- 36:07Conclusion and takeaways
- 39:00Q&A session
related talks
03h 08mSoftware Architecture for Developers (3-hour workshop)
02mHigh-performance teams
37mSoftware Architecture for Humans!
45mTeam and Software: Making an Impact as an Architect
51mSoftware Architecture for Humans!
48mDown the Ivory Tower towards Agile Architecture
41mSoftware Architecture in a DevOps World
45mSoftware Architecture for Humans!