Changing software architecture by changing teams.
Many years after Melvin Conway published “How Do Committees Invent?”, he summarised his 45 paragraphs thesis into one sentence:
Any organization that designs a system (defined more broadly here than just information systems) will inevitably produce a design whose structure is a copy of the organization’s communication structure. — Conway’s Law
Conway’s Law suggested that the software architecture eventually copies the communication structure.
I’ve seen a common example of frontend and backend teams.
This is your desired architecture.
Then, you start to organize the teams based on expertise, frontend, and backend.
Eventually, the backend team works on the API and Back-office inside the same application code and deploys it as a single application.
It also proves the quote from Ruth Malan:
If the architecture of the system and the architecture of the organization are at odds, the architecture of the organization wins. — Ruth Malan
