Communicating and Documenting Architectural Decisions
A talk about communicating and documenting architectural decisions (duh).
Making, documenting, and communicating architectural decisions is one of the hardest things to do, especially in this new age of "agile" architecture and two-pizza teams building and supporting their own software. This talk will go over three techniques to help solve these communication and decision making processes.
As technologists and technology leaders, we live in an interesting and chaotic time. The days of ivory-tower enteprise architects doling out treatises on approved technologies are over; instead we have agile, two-pizza teams building using emerging architecture techniques and the latest languages. How do we get a handle on this environment and make sure what's being done is documented and communicated out to the larger organization?
In this talk, I'll discuss three techniques that can be used to help:
- Lightweight Architectural Decision Records
- Technical Architecture Guilds
- Building Reference Implementations
All of these may not be right for everyone, but taken together, they can be a powerful force to help document and communicate the decisions that your teams are already making every day.
There are two versions of the talk, one that's 30 minutes (I presented this at The Lead Dev NY, 2019), and one that's 60 minutes (I'm presenting this at the Phx DevOps Meetup in August).
The following links are referenced in the presentation:
- Original Blog Post about ADRs:
- Michael Nygard: http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions
- Picture of Michael taken from his public github profile: https://github.com/mtnygard
- Real world examples of ADRs:
- Article about Architecture Guilds & ADRs at scale @ Comcast
Lead Dev New York 4/30/2019