Delivery & Steering

Scaled Agile Frameworks Compared: SAFe, LeSS and Custom Models

Marin Niehues3 April 202511 min read

Two colleagues planning with sticky notes on a window

Whether SAFe, LeSS or a custom model is the right choice is decided by the degree of dependency between teams and the willingness to adapt structures. Scaled agile frameworks answer a delivery question: how can many teams work on one product without coordination consuming the speed? This article compares the well-known approaches. It names thresholds and costs and shows how to derive a model that fits your own organization.

What problem scaled frameworks solve

A single team coordinates through daily conversation. As soon as several teams work on one product, dependencies arise through shared components, the coordinated releases and shared priorities. Every dependency costs waiting time, and the sum of these waiting times determines how fast the organization delivers.

Scaled frameworks define how planning and roles as well as decisions are organized across team boundaries. They differ in how much they prescribe and how much they change the organization. Lead time and on-time delivery must improve measurably, otherwise the framework remains a shell of new terminology. The article characteristics and metrics of a high-performing organization describes how delivery capability and organization design connect.

From how many teams do you need a scaled framework?

A scaled framework pays off from about three teams that are tightly coupled on a shared product and regularly have to deliver together. Two teams usually coordinate without a dedicated framework, for instance through a joint review and a short alignment meeting of team representatives.

What matters is the coupling of the teams. Ten teams with separate products manage with sound portfolio management. Three teams working on the same code base or the same customer process, by contrast, need a shared planning rhythm. The frameworks set their own thresholds: Nexus is described for three to nine Scrum teams, LeSS for up to eight teams, and an Agile Release Train in SAFe comprises 50 to 125 people.

If three or more statements apply, a scaled framework pays off. If two or fewer apply, a better product cut reaches the goal faster than a new framework.

What is SAFe?

SAFe (Scaled Agile Framework, published by Scaled Agile, Inc.) is a comprehensive framework that connects agile teams across several levels up to portfolio management. Its central element is the Agile Release Train, a group of usually five to twelve teams with 50 to 125 people. It plans and delivers in a shared planning interval of eight to twelve weeks, the Planning Interval (called Program Increment up to SAFe 5). At the start of each interval, everyone involved plans together over two days.

Advantages of SAFe:

  • A ready-made framework with defined roles, processes and planning rhythms
  • Portfolio management and budgeting by value stream are included
  • A broad range of training and certified consultants
  • Compatible with the reporting obligations and regulation of large companies

Disadvantages of SAFe:

  • A large scope with many roles and terms, which in smaller organizations creates more coordination than the work requires
  • Existing hierarchies largely remain, and the structure changes little
  • Noticeable costs for training, the certification and implementation support
  • Criticism from the agile community of its prescriptive density, which leaves teams little room

SAFe fits when an organization with many coupled teams and high reporting needs is looking for a prescribed framework.

What is LeSS?

LeSS (Large-Scale Scrum, developed by Craig Larman and Bas Vodde) is a framework that extends Scrum to several teams with as little additional structure as possible. For up to eight teams, it provides one Product Owner, one Product Backlog and a shared Sprint; beyond that, LeSS Huge adds Area Product Owners for each requirement area.

The guiding principle is to simplify the organization instead of adding new layers. LeSS demands changes to roles and decision paths, especially in middle management, and favors teams that deliver complete customer features.

Advantages of LeSS:

  • Few additional roles, close to familiar Scrum
  • One backlog for all teams creates unambiguous priorities
  • Simplifies the structure and lowers coordination effort permanently

Disadvantages of LeSS:

  • Requires far-reaching changes to roles, the leadership and team design
  • Portfolio management and budgeting have to be added
  • A single Product Owner for up to eight teams needs considerable decision-making latitude

LeSS fits when several teams develop a shared product and the organization is prepared to reduce hierarchy.

What are Nexus and Scrum@Scale?

Nexus and Scrum@Scale are two further approaches that extend Scrum to several teams while remaining leaner than SAFe. Nexus comes from Ken Schwaber and Scrum.org and connects three to nine Scrum teams working on one product. A Nexus Integration Team ensures that a shared, integrated result emerges in every Sprint.

Scrum@Scale was developed by Jeff Sutherland and connects teams in groups of about five into a Scrum of Scrums, which can in turn be combined further. For priorities and impediments at leadership level, the model provides dedicated leadership forums. Both approaches suit organizations that already master Scrum and want a light framework.

The Spotify approach with squads and tribes goes back to a 2012 description by Henrik Kniberg and Anders Ivarsson. It captured a snapshot of a single company, was never intended as a framework and serves as inspiration for custom models.

What does a SAFe implementation cost?

A SAFe implementation costs above all the time of the people involved, plus training and certification as well as external support.

On the market, the two-day entry training for leaders (Leading SAFe) typically costs around 1,300 to 1,900 euros per participant plus VAT, including the exam. The four-day course to become a SAFe Practice Consultant, who supports the implementation internally, is around 3,000 euros. Certifications have to be renewed annually for a fee. According to the fee study of the German Association of Management Consultants (BDU), external support is billed at around 1,000 to 2,500 euros per consultant day.

The fourth item is the one most often overlooked. A release train with 100 people and five planning intervals a year commits around 1,000 person-days annually to the joint planning days alone. Before any expansion, a pilot shows whether this time reduces waiting and rework.

Five questions that decide the choice

First: how tightly are the teams coupled? The analysis shows what share of the work can be delivered without coordination. With tight coupling, teams need a shared backlog or a shared planning rhythm. With loose coupling, a light coordination framework is sufficient.

Second: how is the product cut? In 1968, Melvin Conway described how organizations design systems that mirror their own communication structure. Teams organized around components create dependencies. Teams organized around value streams reduce them.

Third: where do decision rights sit? A framework only takes effect when Product Owners can actually enforce their priorities and teams determine their own way of working. Where approvals still pass through several hierarchy levels, speed remains unchanged.

Fourth: what steering needs does leadership have? Portfolio and budget, regulation and reporting obligations create requirements that a framework must cover or that must be added. SAFe brings components for this, while LeSS requires an answer of your own.

Fifth: how much change can the organization absorb, and over what period? Many programs stall because the redesign was chosen too large.

Custom models built from components

Many organizations develop a custom model from the approaches. Typical components are Scrum teams, a quarterly planning rhythm, a product cut along value streams and the four team types defined by Matthew Skelton and Manuel Pais (Team Topologies, 2019): stream-aligned teams, platform teams, enabling teams and complicated-subsystem teams.

A custom model needs the same discipline as a framework. It requires clear principles, a minimal set of roles with defined decision rights, a fixed rhythm and metrics that show its effect. A named function maintains the model and develops it further. The framework for this is set by the operating model, which defines how the organization works before structures are drawn.

How Niehues Consulting supports the choice of model

Niehues Consulting supports selection and implementation through delivery management and organization design. The approach follows the Niehues Delivery Model with the phases Understand, Build and Implement. In the Understand phase, a dependency analysis and a measurement of delivery performance establish the baseline. In the Build phase, the target structure with roles and decision paths follows, together with a pilot with the first teams. In the Implement phase, processes and responsibilities move into regular operation, along with the enablement of leaders.

Three of the model's assessment questions matter most when choosing a framework. Who decides, who delivers, who uses? Which roles, decision paths and interfaces does operation require? Which metric shows after 90 days that the solution is taking hold? Marin Niehues works from the delivery perspective and builds organizations that deliver. Depending on the situation, he takes on the role of delivery manager, project manager or product owner and steers the implementation through to measurable impact. The entry point is the free 30-minute initial consultation via contact.

Frequently asked questions

What is the difference between SAFe and LeSS?

SAFe is a comprehensive framework with defined levels and roles plus a shared planning interval, whereas LeSS extends Scrum to several teams with as little additional structure as possible. SAFe adds steering components to existing processes. LeSS simplifies the organization and in return demands more change to roles.

What company size is SAFe suitable for?

SAFe suits organizations in which at least 50 people in five or more tightly coupled teams work towards a shared outcome and leadership has high reporting needs. This corresponds to the size of one Agile Release Train. With a few loosely coupled teams, a leaner model such as Nexus or a custom framework is sufficient.

What are the disadvantages of SAFe?

The main disadvantages of SAFe are its large scope of roles and terms, the limited change to existing hierarchies and the cost of training and certification. In organizations with loosely coupled teams, the framework creates more coordination than the work requires. This criticism can be answered when a pilot demonstrates the effect on lead time and on-time delivery.

Is a custom agile model worthwhile?

Yes, if roles and rhythm as well as metrics are clearly described and a named function maintains the model. It can then be tailored to the actual delivery problem and avoids elements the organization does not need. Without this maintenance, it becomes a collection of local habits.

How long does a SAFe implementation take?

A first Agile Release Train is established after the preparation phase and two to three planning intervals, that is after around six to nine months. Measuring the effect on lead time and on-time delivery before further release trains follow has proven effective. Expanding to a whole portfolio takes correspondingly longer and proceeds in stages.

Does the Spotify model work?

The Spotify model works as inspiration and is unsuitable as a template to copy. The 2012 description captured a snapshot of one company with its own culture and conditions. Introducing squads and tribes also requires clarified decision rights and metrics.

Let’s talk about your initiative.

In 30 minutes we clarify where your organization stands and which step will pay off most now.

Request a consultation

30 minutes · free · no obligation