| title | toc | categories | |
|---|---|---|---|
AD Practices |
true |
|
The lists on this page point at ADR capturing practices and related advice but do not necessarily endorse all of them. {: .prompt-info }
Timing Architectural Decisions, a presentation given at the annual Swedish IT architect conference ITARC features many of the practices collected on this page.
The Design Practice Repository on GitHub and the Design Practice Reference, a corresponding LeanPub e-Book, feature an AD making and capturing activity, which is positioned as one of the essential activities in DPR.
Decision-making ADRs: weightings are a work-around is a blog post by Jacqui Read that offers some tips on how to make better architectural decisions.
- Definition of Ready for Architectural Decisions, suggesting five criteria abbreviated as START.
- Architectural Significance Test and Some Core Decisions
- How to create ADRs — and how not to collects good practices and anti-patterns.
- The Markdown ADR (MADR) Template Explained and Distilled
- A Definition of Done for Architectural Decision Making proposes five criteria and a checklist to decide when it is time to set the status of a single decision to "done": evidence, criteria and alternatives, agreement, documentation, and realization/review plan. Here, we focus on the 'D' in ecADR.
- Context, background and examples of good and bad justifications can be found in this blog post.
- How to review ADRs — and how not to has good practices, anti-patterns, review check list
- An Adoption Model for Architectural Decision Making and Capturing
Most of the material referenced above is also available on Medium.
- Documenting Architecture Decisions, blog post by Fabian Kleiser
- More will be featured in future versions of this page, suggestions are welcome!
- to be continued
From Architectural Decisions to Design Decisions and ADR = Any Decision Record? are two blog posts proposing to extend the scope of ADRs.