I think, this article explains really well how not to scale an engineering team. I really liked this analogy. When a team only works and be responsible half of the product, everything else falls apart.
Especially introduction of microservices as an architecture and organisation pattern, to avoid above issues, it is also better to let go certain things like code duplication, utility libraries, single source of infrastructure management…
Mahmut Canga 
What do you think?