Learn how Nexus scales Scrum across 3–9 teams working on one product, with the Nexus Integration Team and a small set of added events designed to surface cross-team dependencies and integration problems early. Understand how to map a real multi-team initiative onto Nexus and stop discovering conflicts only at release time.
Watch the free preview
Why scaling Scrum is hard — dependencies and integration — free to watch, no account needed.
What you'll learn
- Explain why cross-team dependencies and integration are the core problems that scaling Scrum must solve
- Describe Nexus as a minimal extension of Scrum for 3–9 teams building one product from one Product Backlog
- Describe the Nexus Integration Team's composition and its accountability for a done, integrated Increment
- Map a real multi-team scenario onto Nexus's added events and artifacts to surface dependencies early
- Produce a Nexus Framework Mapping Template that lays out teams, events, roles and integration points
Syllabus
The Scaling Problem and What Nexus Is
Why scaling Scrum is hard — dependencies and integrationFree preview
What Nexus is — a minimal extension of Scrum
Inside Nexus — the Integration Team, Events and Artifacts
The Nexus Integration Team and its accountability
Nexus events and artifacts in depth
Applying Nexus to Real Multi-Team Work
Mapping a real multi-team scenario onto Nexus
Case study — integration conflicts found only at release time
Making Nexus Stick
Building your Nexus Framework Mapping Template
Common traps in scaling with Nexus