Saved by Hagen Peters and
bliki: Conway's Law
Conway’s Law:
‘For any organization that builds systems, the systems they produce reflect the communication structures of that organization.’
If your organization is inefficient and disjointed, or dictatorial and myopic, it shows in your products.
‘For any organization that builds systems, the systems they produce reflect the communication structures of that organization.’
If your organization is inefficient and disjointed, or dictatorial and myopic, it shows in your products.
James Rosen-Birch • Tweet
"Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure."–Marvin Conway
Wikipedia • Conway's law
Conway’s law tells us that an organization’s structure and the actual communication paths between teams persevere in the resulting architecture of the systems built.
Matthew Skelton, Manuel Pais • Team Topologies: Organizing Business and Technology Teams for Fast Flow
Conway’s Law doesn’t leave anyone guessing about how to make organizational communication structures work for the greater good. As the conclusion of Conway’s paper states: We have found a criterion for the structuring of design organizations: a design effort should be organized according to the need for communication.
Vaughn Vernon • Strategic Monoliths and Microservices: Driving Innovation Using Purposeful Architecture (Addison-Wesley Signature Series (Vernon))
Mythical Man-Month, Anniversary Edition, The: Essays On Software Engineering
amazon.com
I conclude that there are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult. It demands the same skill, devotion, insight, and even inspiration as the disco... See more