Scaling the Practice of Architecture

·

TL;DR: Π½Π°Π±ΠΎΡ€ ΠΏΡ€Π°ΠΊΡ‚ΠΈΠΊ для ΠΌΠ°ΡΡˆΡ‚Π°Π±ΠΈΡ€ΠΎΠ²Π°Π½ΠΈΡ software architecture Π² Ρ€Π°ΠΌΠΊΠ°Ρ… ΠΊΠΎΠΌΠΏΠ°Π½ΠΈΠΈ

  • One core element: Advice Process
  • Four supporting elements:
    • Architecture Advisory Forum
    • Lightweight ADRs
    • Team-sourced Principles
    • Your own Tech Radar

The Advice Process is the core element of this anarchist, decentralised approach to architecture. It’s greatest quality is it’s remarkably simplicity. It comprises one rule, and one qualifier:

  • The Rule:Β anyone can make an architectural decision.
  • The Qualifier:Β before making the decision, the decision-taker must consult two groups: The first is everyone who will be meaningfully affected by the decision. The second is people with expertise in the area the decision is being taken.

That’s it. That’s the Advice Process in its entirety.

Pasted image 20230905152326.png

The standing agenda typically begins as follows:

  • team representatives quickly share newΒ spikesΒ (giving early warning of probable future decisions and allow the attendees to share existing knowledge and experience)
  • discussions about each new β€œproposed” decision (presented by those making the decision, captured ahead of time in the form of an ADR)
  • a re-visit of other decision-statuses (we timebox these, both to limit the window for incoming advice, and also to allow us to revisit a decision which we made with imperfect information)
  • a look at our collective four key metrics, our cloud spend trends, and finally
  • any other business (aka β€œAOB”)

Link:: https://martinfowler.com/articles/scaling-architecture-conversationally.html