Add Scrum Team pattern(s) for successful scaling
In an ideal world, a team owns it dependencies. As a larger organization adopts Scrum and leverages across a complex product / services environment where many products are leveraging 10's to 100's of services, describe pattern(s) for how teams can effectively organize to ensure their service can scale to meet the need of its users. We have some complex services that require many Scrum teams to deliver the service. Complicating matters, there are many products consuming this service and the service teams delivering the service are always a bottleneck. We've tried various patterns and have one that works now, but took us a long time to get there. Would be great to define best practice.