Some of the decisions that architects make are more consequential and higher impact than others and need to be preserved. This workshop session
* shares the motivation that led to trying Architecture Decision Records (ADRs) for preserving decisions
* shares experiences working with ADRs
* draws from experiences with multiple large-scale, global organizations and system architectures
* builds on established work with ADRs from other authors and practitioners
* presents a summary of experiences using ADRs with teams from three specific product lines
* shows examples of ADRs from each product line
* shares examples of challenges encountered when adopting and using ADRs
* provides participants with hands-on practice creating and reviewing ADRs
My experience of ADRs is with
* global teams in North America, Europe, and India
* architectures for large systems and code bases (multimillion LOC)
* large, complex, software-intensive systems that include software, hardware, and firmware design
* organizations dealing with architectures for multiple products and systems
## Learning Outcomes
* Get options for structuring and tailoring ADR templates, including some examples of how we have tailored ADRs with different teams
* Understand the types of decisions for which ADRs are appropriate and what decisions might be better suited to a different medium
* Learn factors to consider for creating, storing, and reviewing ADRs
* Foster a culture of valuing ADRs
* Learn factors to consider when working with distributed teams in multiple geographies
* Get pointers to other work in the area of ADRs
See the slides.Watch the video.
