How do we scale Scrum for a large product with 10+ different teams?

All answers to this question.

Scaling requires a "Framework for the Framework." "Scrum of Scrums" is usually the first step, where ambassadors from each team meet daily to discuss cross-team impediments. However, for 10+ teams, you need something more robust like "Nexus" (which adds a Nexus Integration Team) or "LeSS" (Large Scale Scrum). These frameworks emphasize a "Single Product Backlog" to ensure everyone is pulling from the same priority list. SAFe is very popular in traditional corporations because it adds a layer of "Program Management," but be careful—it can feel very "Waterfall" if not implemented with a true Agile mindset.

   Answered 2025-09-24 by Margaret Moore

With 10 teams, how do we handle "Shared Resources" like a single UX Designer or a DBA who is needed by everyone at the same time?

   Answered 2025-09-26 by Brian Allen

• This is where "Cross-functional Teams" are tested, Brian. Ideally, you should hire or train enough UX/DBA skills so they are "Embedded" in the teams. If that’s not possible, you treat the shared resource as a "Service Team." They have their own Kanban board. During "Big Room Planning" (a SAFe technique), you identify these dependencies weeks in advance. The goal is to move away from "Component Teams" (the DBA team, the API team) and toward "Feature Teams" that have everything they need to take a user story from "Backlog" to "Done" independently.

     Commented 2025-09-28 by Kevin Scott

"Refinement" is the key to scaling. If the 10 teams spend time together refining the backlog, 80% of the dependency issues are caught before the Sprint even starts.

   Answered 2025-09-30 by Nancy King

• Exactly, Nancy. Scaling isn't about more meetings; it’s about better "Alignment." Thomas, start with Nexus if you want to stay close to pure Scrum; it’s much less bloated than SAFe.

     Commented 2025-10-02 by Thomas Anderson