Architecture Decision Records
summary
Architecture Decision Records are a set of numbered short text files kept next to the code that capture the actual why, the chosen decision and its consequences; they use statuses like proposed / accepted / superseded and stay forever to preserve history. The format insists on context, a one‑sentence decision and consequences, links to alternatives, and small focused docs in markdown files tracked in source control. A visualization server structu by Simon Brown publishes them and this approach proves useful as a discussion basis and unblocks new teammates.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:21Waterfall to agile docs
- 1:50Why docs matter
- 3:17Balanced docs view
- 4:45What are ADRs
- 6:10ADR format and lifecycle
- 8:44ADRs in greenfield and legacy
- 10:36Practical tips for using ADRs
- 11:40Tool recommendation for ADRs
- 13:27Q&A
related talks
14mArchitecture Decision Records: Make Peace with Your Docs
54mHow'd we get here? A guide to Architectural Decision Records
43mWorking Efficiently with Architecture Decision Records (ADRs)
49mArchitecture as Knowledge
45mArchitecture and the Architect AD2022
47mMaking architecture decisions, the Agile Way
37mArchitecture Decision Records - How not to get lost in the past
43mGetting Started with Architectural Decision Records