Imagine several Scrum teams all racing toward one goal, but constantly tripping over each other due to conflicting requirements, mismatched knowledge, and tangled integration. Nexus is a framework designed to solve this very puzzle—uniting multiple teams as a powerful, synchronized force building a single product.
Nexus was created and is maintained by Scrum.org—the same organization that maintains the official Scrum Guide. Its practices are designed specifically for scaling Scrum in the real world.
Dependencies between teams working on the same product impede the kind of productivity single scrum teams usually experience without those dependencies. Nexus is a scaling framework focused on treating multiple teams as a single unit. Reduction of inter-team dependencies is key to scaling success.
Inter-team dependencies usually revolve around how teams structure requirements and the product backlog, the domain knowledge differences between teams, and the software and test artifacts. Dependencies are reduced by mapping requirements, team members’ knowledge, and test artifacts to the same scrum teams.
Nexus is a framework that describes how three to nine scrum teams — a Nexus — work together on the same product backlog under the guidance of a single product owner to deliver potentially shippable functionality to every sprint.
Reduction of inter-team dependencies is key to scaling success.
A scaling framework for Scrum that enables three to nine teams to work from a single product backlog under one product owner, targeting integrated, potentially shippable increments every sprint.
Situations where the work of one team relies on or affects another team, often causing delays and integration challenges in larger Scrum projects.
Nexus helps scrum teams working on the same product identify and resolve dependencies quickly and early, enabling each scrum team to move forward in their work unblocked and unimpeded. Inter-team dependencies are often created when product backlog items are not sufficiently refined or broken down into relatively independent items that a single scrum team can work on. Dependencies can also arise from differences in technical skills or domain knowledge between teams. Joint product backlog refinement helps teams identify dependencies and minimize them before they cause conflict.
- Nexus treats multiple Scrum teams as a single unit working from one backlog.
- Reducing inter-team dependencies is essential for scaling Scrum successfully.
Nexus integration team
Similar to the vertical slicing model’s integration team concept, the Nexus integration team ensures that an integrated product increment is produced at least every sprint for the Nexus. The scrum teams do the work, but the Nexus integration team remains accountable for the integrated product as a whole.
The Nexus integration team consists of people from the member scrum teams of the Nexus. It is a scrum team that consists of the following:
- Product owner: The product owner is accountable for ordering and refining the Nexus product backlog, so the maximum value is derived each sprint from work created by the Nexus.
-
Developers: Usually, developers are also members of scrum teams in the Nexus. The Nexus integration developers prioritize the Nexus integration team over the individual scrum teams, with the integrated product increment being the prime goal for each sprint.
REMEMBERDedicating scrum team members to one team eliminates the overhead of frequent cognitive demobilization and remobilization due to context switching. Always be aware of the risks of splitting team members’ focus across multiple teams.
- Scrum master: The scrum master is responsible for ensuring the Nexus framework is enacted and understood. This Nexus integration team scrum master may also be a scrum master in one or more of the other scrum teams in the Nexus.
What might go wrong if the Nexus integration team does not maintain a strong focus on the integrated product increment?
Nexus artifacts
Three additional artifacts provide transparency at the Nexus level for inspection and adaptation:
- Nexus goal: Having a clear, visible, common purpose for all scrum teams in the Nexus is key to keeping all teams in sync throughout the sprint, working toward the integrated product increment.
- Nexus sprint backlog: Each scrum team has its own sprint backlog of implementation and integration tasks. The Nexus sprint backlog is not an aggregation of these sprint backlogs; it exists to expose and map inter-team dependencies and how work flows across all scrum teams in the Nexus.
- Integrated increment: All integrated work completed by all the scrum teams in the Nexus during the sprint is the integrated increment.
At a fast-growing tech company, six Scrum teams use Nexus to deliver a new app. Thanks to a shared Nexus sprint backlog, they spot and resolve dependencies early, avoiding costly rework in integration.
How does the Nexus sprint backlog differ from simply combining all individual teams’ sprint backlogs?
Nexus events
Five additional events enhance inter-team coordination of dependencies at the Nexus level.
Want to go deeper? The science behind scaling teamwork
Research on team performance shows that coordination costs (the time and effort needed for teams to synchronize their work) increase rapidly with each additional team involved in a project. Frameworks like Nexus are designed to make these costs transparent and manageable, enabling large organizations to deliver value without becoming bogged down in bureaucracy.
Nexus sprint planning
During Nexus sprint planning, the product owner from the Nexus integration team provides priority and business context for the sprint and sets the sprint goal. The individual scrum teams select work for the sprint while highlighting and minimizing dependencies. Each scrum team then holds its own sprint planning to plan the execution of the work it has pulled from the Nexus sprint backlog.
Why is it important for each scrum team to hold its own sprint planning after the Nexus sprint planning event?
Nexus daily scrum
Nexus does not prescribe who should attend the daily scrum — the right people are members of individual scrum teams that understand how their work may affect, or be affected by, other scrum teams’ work. The questions addressed are similar to a single scrum team’s daily scrum but focus on cross-team integration, including the following:
- Did yesterday’s work get successfully integrated?
- What new dependencies have been discovered?
- What information needs to be shared across teams?
The Nexus daily scrum is held before each scrum team holds its own daily scrum to provide the scrum teams with input to better help them plan their day’s work.
Nexus sprint review
Similar to other scaling frameworks, the Nexus sprint review can replace individual scrum team sprint reviews because the focus is the integrated increment. You can use various techniques to maximize stakeholder feedback to conduct the meeting, but none are prescribed.
Nexus sprint retrospective
The Nexus sprint retrospective is a formal opportunity to improve the way the Nexus works through inspection and adaption. The Nexus sprint retrospective includes three parts:
- Representatives from Nexus scrum teams meet to identify cross-team issues and make them transparent across the Nexus.
- Individual scrum teams hold their own sprint retrospectives.
- Representatives from the scrum teams meet again to decide what to do to resolve Nexus-wide issues.
Scaling Scrum just means adding more Scrum teams—no special framework needed.
Without a scaling framework like Nexus, adding more teams creates complex dependencies and integration problems that can stall progress.
Practice visualizing and minimizing inter-team dependencies in a multi-team Scrum project.
- List three product backlog items assigned to different Scrum teams.
- Draw arrows between items that depend on each other.
- Identify ways to split or reassign items to minimize these dependencies.
Describe a team experience (real or hypothetical) where unresolved dependencies slowed progress. How could a Nexus-style approach have helped?
Practitioners often report that the hardest part of scaling Scrum is not the process mechanics, but the human factors—communication, trust, and willingness to adapt when dependencies are discovered.
Nexus enables multiple Scrum teams to collaborate efficiently on a single product by making dependencies visible and resolving them early, ensuring delivery of an integrated increment every sprint.
What is the primary purpose of the Nexus integration team in the Nexus framework?
What is the Nexus sprint backlog?
Tap to revealA tool at the Nexus level that exposes and maps inter-team dependencies and work flow across all Scrum teams, not just an aggregation of team backlogs.
Integrated increment (in Nexus): What does it mean?
Tap to revealAll completed and integrated work from all Scrum teams in the Nexus during the sprint, representing potentially shippable functionality.
What is the main goal of Nexus events?
Tap to revealTo enhance inter-team coordination and resolve dependencies effectively during the sprint.
How might Nexus events transform the daily workflow of a team used to working in isolation?
Reducing and managing dependencies is critical to the success of any scaled Scrum effort, and Nexus offers a structured approach to making this possible.