Berlin

November 4 & 5, 2024

New York

September 4 & 5, 2024

London

June 16 & 17, 2025

Documenting and communicating architectural decisions

As technologists and technology leaders, we live in an interesting and chaotic time. The days of ivory-tower enterprise 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.

Speakers: David Ayers

Register or log in to access this video

Create an account to access our free engineering leadership content, free online events and to receive our weekly email newsletter. We will also keep you up to date with LeadDev events.

Register with google

We have linked your account and just need a few more details to complete your registration:

Terms and conditions

 

 

Enter your email address to reset your password.

 

A link has been emailed to you - check your inbox.



Don't have an account? Click here to register
July 21, 2020

As technologists and technology leaders, we live in an interesting and chaotic time. The days of ivory-tower enterprise 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