Scaling Frameworks — Scrum of Scrums & LeSS

One team, one backlog, one product — Scrum handles this beautifully. Now multiply that by five. The same ceremonies, the same artifacts, but now you have five Scrum Masters trying to coordinate, five QAs discovering that "integration testing" suddenly means testing five teams' work together, and a Product Owner wondering why the backlog has 847 items.

This module explores the two most popular lightweight scaling approaches: the pragmatic Scrum of Scrums and the principled Large-Scale Scrum (LeSS). Both reject the idea that more teams means more bureaucracy. Both have different ways of proving it.

Lessons in This Module

1. Scrum of Scrums — When Teams Talk to Teams — The ambassador model, dependency tracking, and multi-team synchronization
2. LeSS — One Product, Many Teams, One Backlog — The LeSS principles, shared backlog, and the surprisingly radical idea that teams should be feature teams
3. QA at Scale — Cross-Team Testing Coordination — How testers navigate integration boundaries, shared environments, and cross-team bugs

What You'll Master

By the end of this module, you'll understand the tradeoffs between Scrum of Scrums and LeSS, know how to represent your team in cross-team coordination ceremonies, and have a toolkit for managing testing dependencies when multiple teams touch the same codebase.

The badge you're working toward: The Scale Navigator badge goes to those who can find their bearing when the map shows more than one team. In multi-team environments, the ability to coordinate is as valuable as the ability to execute.