Scaling Scrum with Nexus

A Framework to Help Organizations Scale Scrum

Why Scale Scrum with Nexus?

Scrum is a simple framework for delivering products using an empirical approach in which teams deliver value in small increments, inspect the results, and adapt their approach as needed based on feedback. It consists of a small set of events, accountabilities, and artifacts, bound together by practices, and enlivened by values that are the key to making it work.

Nexus extends Scrum to guide multiple Scrum Teams on how they work together to deliver working product in every Sprint. It considers the journey these teams take as they come together, how they share work between teams, and how they manage and minimize dependencies.

The Nexus GuideThe Nexus Guide

Nexus is based on the Scrum framework and augments Scrum minimally.  The Nexus framework was created by Ken Schwaber, co-creator of Scrum, and was released by Scrum.org, along with a body of knowledge, the Nexus Guide, in 2015 and updated in 2018 as well as 2021.

The Nexus Framework for Scaling Scrum 

The NexuScaling Scrum with Nexus Book Covers Framework for Scaling Scrum: Continuously Delivering an Integrated Product with Multiple Scrum Teams

 

The Nexus Framework for Scaling Scrum is a concise book that shows how Nexus helps teams to deliver a complex, multi-platform product in short, frequent cycles, without sacrificing consistency or quality, and without adding unnecessary complexity or straying from Scrum’s core principles. Using an extended case study, the authors illustrate how Nexus helps teams solve common scaling challenges like reducing cross-team dependencies, preserving team self-management and transparency, and ensuring accountability. 

The Nexus Framework

Forming A Nexus

Like Scrum, it is easy to get started with Nexus, however, the Nexus framework does first and foremost presume Scrum experience. Organizations that are already familiar with Scrum will be able to benefit from their existing Scrum knowledge. In addition to using Nexus, organizations should establish, promote, and steward technical excellence as a foundation for growth. To start a Nexus, organizations should first: 

  • Identify the teams in their Nexus 
  • Form an initial Nexus Integration Team
  • Have a single Product Backlog 
  • Have a Definition of Done 
  • Identify a Sprint cadence 

Implementing Nexus

As with Scrum, Nexus alone isn’t enough for success, but it helps drive to the heart of the scaling issue – continually identifying and removing dependencies created by increased complexity.  You will also need several techniques to bind the work of the Scrum Teams in your Nexus and that is why we have developed and reformulated over 50 practices to help you launch and sustain a Nexus predictably. Find a list of suggested practices here.

Listen to Ken Schwaber and his thoughts on "What is Scaled Scrum?"

 

Resources

Learn more through our Scaled Professional Scrum workshops and take the free Nexus Open assessment and when you are ready, the Scaled Professional Scrum assessment for certification, where Nexus is the cornerstone.

Asian Airline Nexus Case Study Terminales (TPP) Nexus Case Study Security Software Company Nexus Case Study
How Net Health Scales Scrum with the Nexus Framework HVAC Manufacturer Implements Nexus

 

 

"logmein"

 

"avanade cs"

 

"LolaTechCS"

 

Where to Find More

There are many resources including videos, blog articles and more related to Nexus. Go to the Resource Center and to find more.