You won’t believe it – this law is over 75 years old! And still so relevant and important. Conway’s Law is a principle in software development that suggests that the structure of an organization influences the design of the systems it produces. Coined by computer scientist Melvin Conway in 1968, this law highlights the interconnected relationship between organizational dynamics and software architecture.
Conway said: “Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization’s communication structure.“
At its core, Conway’s Law emphasizes that communication patterns, power dynamics, and organizational hierarchies within a company are reflected in the structure and design of its software products. For example, if a company’s development teams are organized into separate departments based on functional areas (e.g., frontend, backend, database), the resulting software architecture may consist of distinct modules or components corresponding to these departments.
A classic example of Conway’s Law in action is evident in the development of large-scale enterprise software. Companies with distributed teams across different geographical locations often produce software systems with distributed architectures, mirroring the communication and coordination challenges inherent in their organizational structure.
Understanding Conway’s Law can help organizations make strategic decisions about their structure and processes to better align with their desired software outcomes. By fostering collaborative and cross-functional teams, companies can break down silos and promote cohesive software designs that reflect the organization’s goals and values.
In conclusion, Conway’s Law serves as a reminder of the intricate relationship between organizational structure and software architecture. By recognizing and leveraging this principle, companies can optimize their development practices and create software systems that align with their organizational objectives.
Links:
Sources:
- Conway, M. E. (1968). “How Do Committees Invent?” Datamation, 14(5), 28–31.
- McConnell, S. (2004). “Afterword: It’s Not Just for Architects.” In “Conway’s Law and Other Essays.” Apress.
Albrecht Günther 