Conway’s Law: Why your architecture looks like your team structure

The communication structures in your organisation influence your software architecture. We explore some examples of this and explain how it relates to Domain-Driven Design (DDD) and Microservices.
0:00 Definition
0:31 Layered teams example
2:04 Lifecycle teams example
3:07 Cross-functional teams & DDD
4:22 Inverse Conway Manoeuvre
Conway's Law: www.melconway.com/Home/Conway...
Inverse Manoeuvre: jonnyleroy.com/2011/02/03/deal...

[@nadzhafox]

Again; great explanation; Now I understand why big company divide teams like that;

[@haraldbackfisch1981]

I just stumbled on this after writing an abstract on societal structures with an outlook on how to construct them in the first place. This is great food for thought as it also applies to forming governmental bodies/institutions. Thanks a lot, may the views be with you!

[@drawingboxes]

Thanks! Melvin Conway noted that the idea has "much broader utility" than just software engineering. He even mentions governments specifically. Worth checking out www.melconway.com/Home/Committees_Paper.html

[@haraldbackfisch1981]

@@drawingboxes Thanks a bunch! I will definitely check that out ❤

[@nifalconi]

Wondeful video as always! Eager for the next one

[@drawingboxes]

Thanks very much :) Next one is in progress!

[@allesklarify]

You definitely have a talent! Another great video to use in class :)

[@drawingboxes]

Thank you! Glad to hear you're getting good use from these videos

[@caseyspaulding]

Thanks!

[@tamasszebenyi5942]

Nice!

[@TimJSwan]

“Ok everyone organize yourself into lambda calculus structure. No killing/eating of each other when iterating. No, Tommy, you’re not going to be the universally inhabited type in calculus of inductive constructions, again.”

[@drawingboxes]

"Great job everyone, now our Loop Enablement Team have built the YCombinatorService so other teams don't have to worry about the complexity of recursion". What could possibly go wrong...