In 30 seconds
- Nexus scales Scrum for roughly 3 to 9 teams.
- A Nexus Integration Team owns integration across teams.
- Goal: one Integrated Increment every sprint.
The problem it solves
When several Scrum teams work on one product, the biggest risk is dependencies: work that doesn't fit together at the end. Nexus, introduced by Ken Schwaber and Scrum.org in 2015, focuses on exposing and resolving those dependencies every sprint.
What Nexus adds
- Nexus Integration Team: accountable for an integrated result
- Nexus events: Nexus Sprint Planning, Nexus Daily Scrum, Nexus Sprint Review and Nexus Sprint Retrospective
- Nexus Sprint Backlog and Integrated Increment
Teams still share one Product Backlog and one Product Owner.
When it fits
Nexus fits organizations already using Scrum that need a light way to coordinate a handful of teams. For many more teams, Nexus+ or other frameworks are options.
Myth vs reality
Myth · Nexus is a new process.
Reality · It's Scrum plus a thin integration layer.
Myth · The Integration Team does all integration work.
Reality · It coordinates and coaches; the teams do the work.
Myth · Nexus suits any number of teams.
Reality · It's designed for roughly 3 to 9.
FAQ
How does Nexus compare with LeSS?
Both stay close to Scrum; LeSS pushes harder on organizational change.
Who is on the Nexus Integration Team?
The Product Owner, a Scrum Master and members from the teams.
Is there a Nexus guide?
Yes, Scrum.org publishes a free Nexus Guide.