Agile works well for a single team, but large products and organizations involve many teams that depend on one another. Scaling agile is about keeping the benefits of small, autonomous teams while coordinating planning, dependencies, and delivery across all of them.
You'll start with an overview of the main scaling frameworks and the problems they try to solve. Next you'll look at the Scaled Agile Framework (SAFe), the most widely adopted of them. You'll then compare LeSS and Nexus, two approaches that extend Scrum with minimal added structure, and finish with the Spotify model, a well-known example of organizing around squads, tribes, chapters, and guilds.
With these skills in place, you'll be ready for the final module, Metrics & Organizational Change, where you look at how to measure progress and guide a whole organization through lasting change.
An introduction to the challenges of scaling agile and a tour of the main frameworks, including Scrum@Scale, Nexus, LeSS, and SAFe, and how they differ.
The levels, roles, and events of SAFe, including Agile Release Trains and Program Increment planning, and the advantages and drawbacks of its more prescriptive approach.
How Large-Scale Scrum and Nexus extend Scrum to multiple teams working from one product backlog, and where the two frameworks are similar and different.
How Spotify organized autonomous squads into tribes, with chapters and guilds connecting people who share a craft, and what a coach can learn from it.