While the ability to deploy each microservice independently is really a key element of the system, this doesn't mean that no coordination should be required.
First, there are still some features that need to be deployed in multiple microservices. We've already looked at how we can work on the development process, including details such as handle versioning and checking dependencies explicitly. So what now?
In these situations, coordination between teams is required to ensure that the dependencies are implemented and that the different deployments are executed in an adequate order.
While some coordination can be helped by the leading architect, the architecture role should be focused on long-term goals and not short-term releases. A good tool to allow self-coordination by teams is to inform the other teams in a meeting about releases...