Communicating and documenting architectural decisions
summary
Three practical techniques present concrete outcomes: adopting lightweight architectural decision records stored as Markdown files in Git captures the why and status of each decision; forming a Technical Architecture Guild and short‑lived SIGs coordinates cross‑team choices and reviews via pull requests; and shipping reference implementations (Java Spring Boot, Ruby on Rails, Node) that bake in Docker Vault Consul integration and CI/CD proves approaches, speeds onboarding, and reduces deployment friction—cloning, one build, deployed.
AI-written summary · about
chapters (13)
- 0:00Start
- 5:00ADRs (Architectural Decision Records)
- 12:40Re-use existing code review processes
- 14:26Free Reign!
- 16:21Form Short-Term SIGS
- 17:14Long Running SIGS
- 18:00Review Board ?
- 19:16The Guild helped with one of the hardest problems: Socializing Decisions
- 22:20Reference Application Baked In Best Practices
- 23:09Static Code Analysis
- 24:20Other Reference Implementations
- 24:51Implicit Commitment to Maintain
- 27:07Bonus Technique: Tracer Bullet/Steel Thread
related talks
47mMaking architecture decisions, the Agile Way
48mDown the Ivory Tower towards Agile Architecture
45mSW Design, Architecture & Clarity at Scale
47mBeyond Boring Text: Treating Your Architecture Documentation Like a Product
40mPractices from trenches for embracing evolutionary architecture in wild
14mArchitecture Decision Records
34mShortening the Architectural Feedback Loop
14mArchitecture Decision Records: Make Peace with Your Docs