---
title: "Nexus Framework Scrum at Scale Training Guide"
description: "Learn how the Nexus framework scales Scrum across multiple teams, what roles it adds."
url: "https://agile-training.co.uk/nexus-framework-scrum-scale-training/"
---

# Nexus Framework - Training Guide for Scrum at Scale

Scaling Scrum beyond a single team is where most organisations hit friction. Dependencies pile up, integration work gets missed, and sprint reviews start feeling disconnected from real product progress. The Nexus framework, developed by Ken Schwaber and Scrum.org, addresses exactly these problems by adding a thin layer of coordination on top of standard Scrum without replacing it.

## What Is the Nexus Framework in Scrum at Scale?

**Nexus is a scaled Scrum framework that connects three to nine Scrum teams working on a single product, with shared accountability for delivering an Integrated Increment every Sprint.** The word "Nexus" refers to the connection between the teams rather than any single component. At its core, Nexus keeps everything that works in Scrum and adds only what is strictly necessary to manage cross-team dependencies and integration.

The framework introduces one new structural element: the Nexus Integration Team (NIT). This small group, which includes the Product Owner, a Nexus Integration Team Scrum Master, and optional specialists, is responsible for ensuring the combined work of all teams integrates into a working product at the end of every Sprint. It does not manage the individual Scrum Teams but coordinates the integration effort.

The artefacts and events mirror standard Scrum with some additions. There is a single Product Backlog shared across all teams, a Nexus Sprint Backlog that makes dependencies visible, and a Nexus Sprint Goal that aligns effort. Additional events, such as Nexus Sprint Planning and a Nexus Sprint Review, give teams a shared space to coordinate and inspect the integrated work.

## When Should I Use the Nexus Framework for Scaling Scrum?

**Nexus is the right choice when a single Scrum Team can no longer deliver a product increment on its own and you need multiple teams working from the same Product Backlog.** This typically happens when a product grows complex enough that one team of eight to ten people cannot handle the full scope within a Sprint.

It suits organisations that already have solid single-team Scrum in place. Applying Nexus on top of a weak Scrum foundation amplifies existing problems rather than solving them. If your teams are still struggling with writing clear Product Backlog Items, running effective Sprint Retrospectives, or producing a Done Increment, fix those first.

Nexus works best when teams share a common codebase, a shared Definition of Done, and a continuous integration pipeline. Without technical practices that support frequent integration, the Nexus Integration Team will spend most of its time firefighting rather than preventing problems.

## How Does Nexus Framework Differ from Other Scaling Approaches?

**Nexus stays deliberately minimal, which sets it apart from frameworks such as SAFe, LeSS, or Scrum@Scale.** SAFe introduces a large number of roles, events, and artefacts across multiple levels, making it comprehensive but also heavyweight to adopt. LeSS shares some of Nexus's minimalism but restructures the organisation more fundamentally, often removing middle management layers.

Nexus does not prescribe organisational restructuring. It sits on top of existing Scrum Teams and adds the Nexus Integration Team as a coordination mechanism. This makes the initial adoption faster and less disruptive for most organisations.

The framework is also owned and maintained by Scrum.org, which means it is kept closely aligned with the Scrum Guide. Changes to the Scrum Guide are reflected in the Nexus Guide, so practitioners working in Nexus environments are always working with current Scrum thinking. The Nexus Guide itself is freely available and runs to fewer than 20 pages.

## What Are the Roles in a Nexus Framework Team?

**Nexus adds one new accountability structure, the Nexus Integration Team, while all standard Scrum roles remain unchanged inside each individual Scrum Team.** Every team still has a Product Owner, Scrum Master, and Developers. The difference lies in how some of those people also contribute to the Nexus Integration Team.

The Product Owner in Nexus holds the same accountability as in standard Scrum but operates across all teams. There is one Product Owner for the entire Nexus, not one per team. This single point of product ownership is essential for maintaining a coherent Product Goal and prioritised backlog.

The Nexus Integration Team Scrum Master is a dedicated role focused on cross-team impediments, integration health, and coaching the teams on how to reduce dependencies. Members of the Nexus Integration Team may come from the individual Scrum Teams, particularly specialists in areas like DevOps, architecture, or testing. These people continue their regular work but carry an explicit responsibility for integration.

## Nexus Framework Scrum at Scale Training - What to Expect

Scrum.org offers the Scaled Professional Scrum with Nexus (SPS) course as the primary certified training path. The course typically runs over two days, blending instruction with simulation-based learning where participants work through a multi-team Sprint together. This hands-on format is deliberate: Nexus challenges are most visible when you experience the coordination problems yourself.

The SPS course covers the Nexus Guide in depth, common dependency patterns, how to structure the Nexus events, and how the Nexus Integration Team operates in practice. Passing the online assessment after the course earns the Scaled Professional Scrum (SPS) certification from Scrum.org.

### Who Should Attend Training

The course targets Scrum Masters who will facilitate Nexus events, Product Owners managing a large backlog across multiple teams, and Developers who will sit on the Nexus Integration Team. It also suits Agile coaches and consultants advising organisations on scaling decisions.

Organisations often send a mixed group from an existing product team, which mirrors real working conditions. Attending as a group rather than as isolated individuals means participants can apply what they learn to actual problems on their product immediately after the course.

### Self-Study and Free Resources

The Nexus Guide is the definitive reference and costs nothing to download from Scrum.org. Scrum.org also publishes a free Professional Scrum with Nexus open assessment, which is a useful diagnostic before attending formal training. Working through it reveals the areas where your understanding of Nexus or underlying Scrum is thinner than you realise.

Several Scrum.org practitioners publish case studies describing how specific organisations introduced Nexus, the dependency patterns they encountered in the first few Sprints, and how the Nexus Integration Team's composition evolved over time. These are more practically useful than theoretical overviews because they describe the friction of real adoption rather than the ideal state.

## Making Nexus Work After Training

The most common failure mode after Nexus training is treating the Nexus Integration Team as a management or governance layer. It is not. Its job is to ensure integration happens continuously, not to approve or oversee the Scrum Teams.

Organisations that succeed with Nexus invest early in automated integration and testing pipelines. When integration is manual and slow, teams batch their work and create the same big-bang integration problems that Nexus is designed to prevent. The technical foundation matters as much as the process knowledge.

The Nexus Sprint Retrospective deserves particular attention. It runs in two parts: first, the Nexus-level retrospective identifies cross-team issues, then individual teams run their own retrospectives and address the items raised at the Nexus level. Teams that treat the Nexus Retrospective as optional or cosmetic miss the primary mechanism for improving coordination over time.

## Frequently Asked Questions

### What Is the Nexus Framework in Scrum at Scale?

**Nexus is a scaled Scrum framework developed by Scrum.org that connects three to nine Scrum Teams working on a single product.** It adds a Nexus Integration Team and a small set of additional events and artefacts to manage cross-team dependencies and ensure a fully integrated product increment is delivered every Sprint.

### When Should I Use the Nexus Framework for Scaling Scrum?

**Use Nexus when a single Scrum Team can no longer deliver a product increment on its own and you need multiple teams working from the same Product Backlog.** It works best when teams already practise solid single-team Scrum and share a common codebase with continuous integration tooling in place.

### How Does Nexus Framework Differ from Other Scaling Approaches?

**Nexus is deliberately minimal compared to SAFe or LeSS.** It adds only the Nexus Integration Team on top of existing Scrum Teams without restructuring the organisation. Because it is maintained by Scrum.org alongside the Scrum Guide, it stays tightly aligned with current Scrum thinking and the full guide runs to fewer than 20 pages.

### What Are the Roles in a Nexus Framework Team?

**All standard Scrum roles, Product Owner, Scrum Master, and Developers, remain inside each Scrum Team.** Nexus adds the Nexus Integration Team, which includes a single Product Owner for the whole Nexus, a Nexus Integration Team Scrum Master, and optional specialists drawn from the individual teams to manage integration work.

### How Long Does It Take to Get a Nexus Certification?

**The Scaled Professional Scrum with Nexus (SPS) course from Scrum.org runs over two days and includes simulation-based exercises.** After the course, participants complete an online assessment to earn the SPS certification. Prior experience with standard single-team Scrum is recommended before attending.
