Communicating and documenting architectural decisions - David Ayers |

Video sponsor: United States Digital Service (usds.gov)
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.
About David Ayers
David Ayers is a Group Vice President of Technology with Leslie's Poolmart. David has over twenty years of experience crafting elegant, simple solutions for complex problems. He has worked in consulting and industry, with a focus on retail, eCommerce, and the travel industry. Prior to joining Leslie's, David had a brief consulting stint with Credera, and prior to that, David was VP of Technology for The Container Store, where he led teams of technologists in varying areas supporting a speciality retail business, including supply chain, stores, eCommerce, enterprise reporting and analytics, operations, and support. He is passionate about software-as-craft and DevOps practices and helped instill those into the DNA of The Container Store's technologists.
Lead Dev is a community for technical leaders. We have a series of conferences and meetups designed with the needs and pain points of technical team leads in mind. We programme each conference around our three key themes of Team, Tech & Tools. The talks are designed to help very practically with common problems in these areas. To find out more about us, visit:
theleaddevelop...

[@robincarry1982]

The problem originate as no one consider architecture documents as living documents. I like the idea of breaking out the decisions into another doc and manage them locally within the project, but the human aspect which you initially said - hating to write the why, before jumping into what - is about habit. If someone doesn't have it - whether it is this process or any other - they will still suffer.
Good to learn about the concept...

[@Vovk101]

Glad to put 100 like here, underestimated in terms of likes video IMHO. Thank you

[@snowke5095]

Excellent presentation! I found myself coming to many of these same conclusions over time, and I appreciate the centralized talk of these different ideas.

[@TheUltimateGeminiHasSurvived]

Yeah, I'm going to pass on this.