Scaling Agile: SAFe, LeSS, Nexus and Scrum@Scale Compared

Scrum and most agile methods were designed around a single small team. Sooner or later, many organizations face a harder question: what happens when one product needs five, twenty or a hundred teams? Teams step on each other's work, dependencies pile up, and integration becomes the bottleneck.

Several frameworks offer answers. Four of the best known are the Scaled Agile Framework (SAFe), Large-Scale Scrum (LeSS), Nexus and Scrum@Scale. They are often discussed as if they were competing brands of the same thing, but they rest on quite different ideas about how much structure large-scale work needs.

This guide compares them using each framework's own official material. It does not rank them or assess claims about results; the aim is to show what each one actually asks of you.

SAFe: A Comprehensive Operating Model

SAFe is maintained by Scaled Agile, Inc. Its central building block is the Agile Release Train (ART), which SAFe defines as "a long-lived team of Agile teams" that incrementally develops, delivers and often operates one or more solutions. SAFe says ARTs are generally made up of 50 to 125 people.

Work is organized into Planning Intervals (PIs). SAFe describes a PI as a timebox of 8 to 12 weeks, most commonly four or five development iterations followed by one Innovation and Planning (IP) iteration. Each PI starts with PI Planning, which SAFe describes as typically a two-day event for the entire ART, led by the Release Train Engineer, where teams create a plan and commit to a set of PI objectives.

SAFe adds a number of roles beyond team level, including the Release Train Engineer, Product Management, the System Architect and Business Owners, and it extends upward into portfolio management. It also changes frequently. Its "What's new" page, which the framework team says it updates monthly, describes the introduction of AI-Native SAFe in June 2026 alongside what it now calls Core SAFe. Much of the detailed guidance on the official site sits behind a login.

What to weigh: SAFe gives large organizations a detailed, ready-made structure with defined roles, events and cadences. The trade-off is size. There is a lot to learn, and adopting it means adding coordination roles and events rather than removing them.

LeSS: Scrum Scaled Up, With Less

Large-Scale Scrum comes from Craig Larman and Bas Vodde, who have published three books on it. The official site describes two organizational design systems: LeSS, for up to eight teams of eight people each, and LeSS Huge, for up to a few thousand people on one product.

LeSS deliberately stays close to single-team Scrum. According to the LeSS site, there is one Product Backlog, one Definition of Done for all teams, one potentially shippable Product Increment at the end of each Sprint, one Product Owner, many complete cross-functional teams with no single-specialist teams, and one Sprint.

The main additions are in the events. Sprint Planning is split into a shared first part and a team-level second part. Coordination between teams relies on practices the site lists as Just Talk, Communicate in Code, Travelers, Open Space and Communities. An Overall Retrospective, which the site says can last at most 45 minutes per week of Sprint, looks at the whole system rather than one team.

What to weigh: LeSS asks for deep organizational change, such as feature teams organized around the whole product and a single Product Owner, rather than new layers. The site states plainly that neither Scrum nor LeSS should be treated as merely a practice; they are an organizational design system. That is demanding, especially where teams are currently organized by component or specialty.

Nexus: A Minimal Extension of Scrum

Nexus was developed by Ken Schwaber and Scrum.org. The Nexus Guide, dated January 2021, defines a Nexus as "a group of approximately three to nine Scrum Teams that work together to deliver a single product." There is a single Product Owner and a single Product Backlog.

Nexus adds one new accountability, the Nexus Integration Team, made up of the Product Owner, a Scrum Master and appropriate members from the Scrum Teams. It is accountable for ensuring that a done Integrated Increment is produced at least once every Sprint. Nexus also adds or extends events: Cross-Team Refinement, Nexus Sprint Planning, the Nexus Daily Scrum, the Nexus Sprint Review and the Nexus Sprint Retrospective.

The guide says Nexus extends Scrum "only where absolutely necessary" and adds a pointed observation: scaling the value delivered does not always require adding people, and reducing the number of people working on something can be an important practice.

What to weigh: Nexus is light and familiar to anyone who knows Scrum, and its focus on dependencies and integration targets a common pain point. Its scope is deliberately narrow: one product and a handful of teams.

Scrum@Scale: A Network of Scrums

Scrum@Scale comes from Jeff Sutherland and Scrum Inc. Its official guide (version 2.1, February 2022) describes it as a lightweight organizational framework in which a network of teams operating consistently with the Scrum Guide can address complex problems.

Teams are grouped into a Scrum of Scrums, which operates as if it were a Scrum Team; the guide suggests four or five teams per Scrum of Scrums. A Scrum of Scrums Master facilitates the scaled Daily Scrum and Retrospective, while a Chief Product Owner guides a Product Owner Team. Larger networks repeat the pattern as a Scrum of Scrum of Scrums.

At the top sit two leadership groups that the guide calls a minimum viable bureaucracy: an Executive MetaScrum focused on what is produced, and an Executive Action Team focused on how to get it done faster, including removing impediments the teams cannot. The framework is organized into a Scrum Master Cycle (the how) and a Product Owner Cycle (the what). The guide is blunt about prerequisites: "If an organization cannot Scrum, it cannot scale."

What to weigh: Scrum@Scale is built from components, so the guide says an organization can target the areas most in need of change first, and it explicitly involves executives. The guide also says specific tactics for implementing each component are not described in it, so organizations need to work out much of the detail themselves.

Comparing Them Side by Side

Some practical contrasts, drawn from each framework's own description:

• Starting point: LeSS, Nexus and Scrum@Scale all build directly on Scrum. SAFe uses Scrum and Kanban at team level within a much larger model.
• Scope: Nexus targets one product with roughly three to nine teams. LeSS and LeSS Huge also focus on one product. Scrum@Scale and SAFe both describe structures above the product level, such as executive forums or portfolio management.
• Added structure: Nexus adds one accountability. LeSS keeps Scrum's roles and leans on informal coordination between teams. Scrum@Scale adds scaled roles and two executive forums. SAFe adds the most roles, events and levels.
• Planning rhythm: SAFe plans in 8- to 12-week PIs. LeSS and Nexus keep everyone in a common Sprint.

Questions to Ask Before Choosing

1. Do we need more teams, or fewer dependencies? The Nexus Guide's point about scaling down applies to every framework.
2. Can our teams already deliver a done Increment every Sprint? The Scrum@Scale guide and the LeSS site both start from solid team-level Scrum.
3. How much organizational change are we prepared to make? LeSS asks for restructuring; SAFe asks for new roles and events.
4. Who will own the change? Every framework requires leadership involvement, not just team training.

Key takeaways

• SAFe is a comprehensive, frequently updated operating model built around Agile Release Trains of about 50 to 125 people and 8- to 12-week Planning Intervals.
• LeSS keeps single-team Scrum's rules at scale and asks for deep structural change rather than new layers.
• Nexus minimally extends Scrum for roughly three to nine teams on one product, adding a Nexus Integration Team.
• Scrum@Scale links Scrums of Scrums with executive forums for the what and the how.
• No framework substitutes for strong team-level practice and reducing dependencies.

Sources

• Scaled Agile, Inc., Agile Release Train
• Scaled Agile, Inc., Planning Interval (PI)
• Scaled Agile, Inc., PI Planning
• Scaled Agile, Inc., What's New in SAFe?
• Large-Scale Scrum (less.works), LeSS Framework
• Large-Scale Scrum (less.works), Books
• Ken Schwaber and Scrum.org, The Nexus Guide (January 2021)
• Jeff Sutherland and Scrum Inc., The Scrum@Scale Guide, version 2.1 (February 2022)