Software Architect Evolution in Growing Teamfleeting
software architect evolution in growing team
At first, you can have one guy that discusses the problem and tries to find a solution.
Then, when the product grows and people get into the team, each person ends up focusing on only per part of the system. They finally have interface contract with each other to integrate their works.
People needs to still have the high level picture and check that the sum of those contracts actually solve the problem that needs to be solved. This is not necessarily a title dedicated to only one person. The whole team can fulfil that role together. As long as at some point people steer the ship, that’s ok.
When people have interface contracts, they create unit and integration tests to check those contracts. The high level picture needs as well measures to ensure the promise is fulfilled.