Abstract: Some architecture decisions are more consequential and higher impact than others, and need to be preserved. The right level of architecture documentation supports agility. Architecture Decision Records (ADRs) are a useful, lightweight approach for this. This hands-on session shares experiences with ADRs, giving you a set of tools to be successful in your team.
Some of the decisions made by architects are more consequential and higher impact than others, and need to be preserved. This 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 organisations and system architectures
- Builds on established work with ADRs from other authors and practitioners
- Presents a summary of experiences using ADRs with teams from around the world
- Shows examples of ADRs from each product line
- Shares examples of challenges encountered when adopting and using ADRs
- Provides participants with hands-on practice of creating and reviewing ADRs
Learning Outcomes: - Understand how Architecture Decision Records can support agility
- Options for structuring and tailoring Architecture Decision Record 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
- Factors to consider for creating, storing, and reviewing ADRs
- Fostering a culture of valuing ADRs
- Factors to consider when working with distributed teams in multiple geographies
- Pointers to other work in the area of ADRs
