Conway's law is an adage that states organizations design systems that mirror their own communication structure. 

https://martinfowler.com/bliki/ConwaysLaw.html

Conway’s law asserts that organizations are constrained to produce application designs that are copies of their communication structures. Your current organizational structures may not be optimally aligned to your desired solution approach. The inverse Conway maneuver may be applied to achieve isomorphism with the business architecture. Whatever the method used to decompose a problem into a set of bounded contexts, care should be taken to make sure that the coupling between them is kept as low as possible.

While bounded contexts ideally need to be as independent as possible, they may still need to communicate with each other. When using DDD, the system as a whole can be represented as a set of bounded contexts that have relationships with each other. These relationships define how these bounded contexts can integrate with each other and are called context map

Conway's Law is an observation made by computer programmer Melvin Conway in 1967.

▪ The design of a software system will reflect the organizational structure of the team that built

▪ If an organization has separate teams for different parts of a software system, the resulting

software will be divided into corresponding parts that communicate with each other.

Melvin E. Conway

● Any organization that designs a system (defined broadly) will produce a design whose

structure is a copy of the organization's communication structure.

● The way teams within an organization are structured and communicate will have a direct

impact on the architecture of the systems they build.

Martin Fowler

● It was initially described to me by saying that if a single team writes a compiler, it will be a

one-pass compiler, but if the team is divided into two, it will be a two-pass compiler.

● "Conway understood that human communication enables and encourages software coupling." -- Chris Ford