Conway’s Law suggests that an organisation’s design mirrors its communication structure. This principle is increasingly applied in IT, where teams are arranged to optimise software architecture. However, misinterpretations of the law can lead to ineffective team structures. A common misconception is that Conway’s Law implies a direct correlation between team and system design. Instead, it suggests that communication paths influence system design.
Another misunderstanding is the belief that applying Conway’s Law will automatically optimise team and software design. In reality, it’s a tool to understand the relationship between the two, not a blueprint for effective team topology.
The law also doesn’t suggest that teams should be static. Instead, they should evolve with the system design. Finally, Conway’s Law doesn’t imply that communication should be limited within teams. Cross-team communication is crucial for avoiding silos and fostering innovation.
Conway’s Law is a valuable tool for understanding the relationship between team and system design. However, it should be applied with a nuanced understanding to avoid ineffective team structures. Misinterpretations can lead to static teams, limited communication, and suboptimal system design. Instead, teams should evolve with the system, and cross-team communication should be encouraged.
Go to source article: https://medium.com/@fwynyk/conways-law-in-team-topolgies-did-you-really-get-it-69c1a4d702af