“In the company I work there is an architecture team that needs to support 8 squads where each one has its priorities. That is, the architecture is being a bottleneck… Do you have any tips to help us? Thanks in advance. ”By Aline Dias


This was a question received in a group about Lean Inception & MVP.


Here are some of the excellent answers given in the group:


  • Multifunctional team (with a team architect)
  • Use STATIK to make bottlenecks visible
  • Create an integration team (NEXUS style)
  • Calculate the architects’ current capacity and hire more to meet desired capacity
Adding to this conversation… I would venture to say that:
The bottleneck is not in the architect role, but in the architecture itself.


It is (or it was, depending on your context) very common to have a centralised architecture and database. That is the main reason the architects become a bottleneck. It’s required a lot of alignment between them to make sure things remain working properly.


But things are changing. The architectures now have: Micro Services, Bounded Context (fromDomain Driven Design ), and Data Mesh (a style of data organisation driven by domain-specific teams, typically organised around the business capabilities).


And it changes the game. Squads are now organised by business capabilities, responsible for their micro-services, data and architecture. This greatly reduces the bottleneck of architects.


Architecture becomes a high-level master plan; day-to-day dependencies and decisions are made in squads, without going through the architecture bottleneck.


For legacy digital products with semi or monolithic architectures, a hybrid scenario will be needed. On it, the legacy should coexist with the new. And the new must start with an architecture in the new style, definitely more lean.


The bullet points above do help with this transition period, roving good guidelines o how to organize the squads.


Not only the Inception has to be lean, the engineering as well!


For new products, those that start with Lean Inceptions, with release plan and incremental product evolution based on the MVP concept: Do not create monoliths! Once there is no monolith, there will not be a architectural bottleneck anymore.