Scrum Nexus Framework

Nexus is a framework that helps three to nine Scrum Teams work together on one product. Ken Schwaber and Scrum.org created it as a light layer on top of Scrum. Nexus keeps Scrum's rules and adds a few elements that handle dependencies and integration between teams.

The Problem Nexus Solves

Multiple teams working on the same product create overlap. Two teams change the same code. One team waits for another. Separate Increments fail to fit together at the end of the Sprint. Nexus targets these problems with one extra team, one shared backlog, and a few added events.

Structure of a Nexus

                  Product Owner
                       │
               One Product Backlog
                       │
   ┌───────────┬───────┴─────┬───────────┐
 Scrum       Scrum         Scrum       Scrum
 Team 1      Team 2        Team 3      Team 4
   │           │             │           │
   └─────┬─────┴──────┬──────┴─────┬─────┘
         │   Nexus Integration Team │
         └──────────────┬──────────┘
                        ▼
              One Integrated Increment

Nexus Integration Team

The Nexus Integration Team coordinates, coaches, and supervises the application of Nexus. It includes a Product Owner, a Scrum Master, and members who serve as Nexus Integration Team Members. Members often come from the Scrum Teams and rotate over time. The team does not do all the integration work. It ensures that the Scrum Teams integrate their work successfully.

Nexus Artifacts

Nexus Events

• Refinement spreads across teams and finds dependencies early.
• Nexus Sprint Planning aligns the teams on the Nexus Goal.
• Nexus Daily Scrum lets representatives inspect integration issues.
• Nexus Sprint Review shows the full Integrated Increment.
• Nexus Sprint Retrospective examines problems that affect many teams.

Example: Online Learning Platform

Four teams build an online learning platform. Team one builds video lessons, team two builds quizzes, team three handles payments, and team four manages student profiles. In refinement, they discover that quizzes and profiles share the same database table. The Nexus Sprint Backlog marks the dependency, and teams two and four agree on one change owner. At the end of the Sprint, the Integrated Increment shows students enrolling, paying, watching a lesson, and taking a quiz in one smooth path.

Nexus Daily Scrum

Each team holds its own Daily Scrum first. Representatives then meet for the Nexus Daily Scrum. They check whether the current Sprint plan still produces an integrated Increment, share new dependencies, and decide actions. The meeting lasts fifteen minutes.

Benefits

• Small addition to Scrum that is easy to learn
• Strong focus on integration and dependencies
• One backlog and one goal for several teams

Challenges

Nexus works best with three to nine teams. Beyond that range, the coordination load grows. Teams that depend on each other heavily may reorganize around features so that dependencies shrink. Technical practices such as continuous integration and automated testing form the foundation, because late integration defeats the purpose of Nexus.

Shared Definition of Done

Every team in a Nexus must meet one Definition of Done for the Integrated Increment. Teams may add stricter rules for their own work, but they never fall below the shared standard. A common definition removes arguments about what finished means and makes the combined Increment trustworthy. When the teams cannot produce a Done Integrated Increment, the Nexus Sprint Review shows only what is finished and the teams plan how to close the gap.

Getting Started

1. Confirm that every team understands Scrum well.
2. Form a Nexus Integration Team.
3. Merge backlogs into one ordered list.
4. Run refinement with several teams together.
5. Define a shared Definition of Done for the Integrated Increment.