Choosing a Scaling Framework: The Leadership Decisions Behind It

Most leaders first meet scaling frameworks as a slide of logos in a proposal. Learning what each framework contains is the easy part. The hard part is deciding what your organization is willing to change: who decides what gets built, where executives sit, how money moves and how much coordination overhead is worth carrying.

This guide is not another side-by-side summary of the Scaled Agile Framework (SAFe®), Large-Scale Scrum (LeSS), Nexus and Scrum@Scale. Instead, it works through the leadership decisions that choosing among them forces, and shows how each framework's own official material answers them. It does not rank the frameworks or make claims about their results.

Decision 1: do you need to scale at all?

Check the premise first. The U.S. Government Accountability Office's Agile Assessment Guide (GAO-24-105506) notes that many projects incur dependencies and require several agile teams to collaborate, and that frameworks exist to help in those circumstances. But it also advises that if an agile approach is not working for a single team, the organization should address the organizational impediments that prevent teams from working in an agile way instead of scaling that approach up. Even when individual teams are healthy, GAO says, the organization should expect growing pains in scaling.

If your real problem is too many projects, unclear priorities or one team that cannot release, a scaling framework will not fix it. Fix that first.

Decision 2: how far will you redesign the organization?

The frameworks differ most in how much structural change they expect, and that is a leadership call rather than a team one.

• LeSS describes itself as "deliberately simple" but says Scrum and LeSS "form an organizational design system." Its rules call for one Product Owner and one Product Backlog for the whole product, long-lived cross-functional feature teams, and, for the product group, establishing the complete LeSS structure "at the start." For LeSS Huge, the rules switch to an evolutionary approach and warn that such adoptions "take months or years, infinite patience, and sense of humor."
• SAFe organizes teams into Agile Release Trains, which the SAFe site says are generally made up of 50 to 125 people, supported by roles such as Product Management, a System Architect, a Release Train Engineer and Business Owners, and aligned through Planning Intervals.
• Nexus extends Scrum "only where absolutely necessary" for a group of roughly three to nine Scrum Teams working on one product, adding a Nexus Integration Team.
• Scrum@Scale groups teams into a Scrum of Scrums that operates as if it were a Scrum Team, and repeats that pattern for larger networks.

The question for the leadership team is plain: are you prepared to restructure teams around customer value, or are you looking for coordination on top of today's structure? Both are possible starting points, but they point toward different frameworks and different costs, and the answer should be explicit before anyone signs a contract.

Decision 3: where will executives sit?

Every framework gives leaders a job. They are different jobs.

• Scrum@Scale puts executives inside its structure. Its Executive Action Team "fulfills the Scrum Master accountabilities for an entire agile organization" and must include people empowered, politically and financially, to remove impediments. Its Executive MetaScrum is the forum where leaders and stakeholders set strategic priorities with the Chief Product Owners.
• SAFe defines Business Owners as key ART stakeholders with primary business and technical responsibility for return on investment, governance and compliance, and places portfolio decisions in Lean Portfolio Management.
• LeSS says managers are optional, and that where they exist their focus shifts from managing day-to-day product work to improving the product development system, through practices such as Go See and "experiments over conformance."
• Nexus focuses on one product and its Product Owner, so leaders using it still need to decide how decisions above that product are made.

Ask each executive which of these roles they are prepared to take on personally, and how much of their calendar it will need.

Decision 4: how will money and portfolio decisions flow?

Funding usually outlasts any framework choice, so look at it early. SAFe describes Lean Portfolio Management as aligning "strategy and execution by applying Lean and systems thinking approaches to strategy and investment funding, Agile portfolio operations, and governance." Scrum@Scale's guide describes the Executive MetaScrum as the place where leaders can alter budgets or realign teams, at least once per Sprint. LeSS and Nexus center product decisions on one Product Owner and one Product Backlog, which leaves leaders to decide how portfolio funding reaches each product.

None of these replaces your finance, audit and governance functions. GAO notes that organizations may need clearly defined guardrails within which teams decide, plus a fast-moving governance process for decisions outside them. Whichever framework you choose, design that interface on purpose.

Decision 5: how will you run the adoption?

Frameworks also differ on how change itself should be managed. The SAFe Implementation Roadmap is a 14-article series based partly on John Kotter's eight accelerators of change, and SAFe's article on the Lean-Agile Center of Excellence says small teams of four to six dedicated people can support a few hundred practitioners. Note that many full SAFe articles require a login to read. LeSS takes a different stance on change initiatives, as covered in Building an Agile Transformation Roadmap That Can Change.

GAO's guidance applies whichever framework you pick: it describes using a pilot to discover problems and mature processes before adopting them across the organization.

Questions to ask before you choose

Imagine, as a hypothetical, a 45-person product group with five teams building one customer-facing application. Size alone would put it within the ranges described for LeSS and Nexus, but size is rarely the deciding factor. These questions usually matter more:

• How many teams truly work on one product, with one backlog?
• Are we redesigning team structure, or adding coordination on top of it?
• Which executive roles described above are we willing to fill, and with whom?
• How will funding and governance decisions reach the teams, and how fast?
• Can our teams integrate their work continuously? GAO calls frequent continuous integration a critical success factor for large and complex programs.
• Where will we pilot first, and what must the pilot prove?

Key takeaways

• Fix single-team agility first; GAO advises addressing organizational impediments rather than scaling an approach that is not working.
• The biggest choice is how much you will redesign the organization, not which logo you adopt.
• Each framework gives executives a different role; decide who will fill it before you commit.
• Plan how funding and governance will connect to teams, whatever framework you use.
• Choose on structure, governance needs and leadership roles, and read each framework's own guide before relying on secondhand summaries, including this one.

Sources

• U.S. Government Accountability Office, Agile Assessment Guide: Best Practices for Adoption and Implementation, GAO-24-105506 (reissued with revisions December 15, 2023)
• Scaled Agile, Inc., Agile Release Train
• Scaled Agile, Inc., Business Owners
• Scaled Agile, Inc., Lean Portfolio Management
• Scaled Agile, Inc., SAFe Implementation Roadmap (updated April 8, 2025)
• Scaled Agile, Inc., Create a Lean-Agile Center of Excellence
• The LeSS Company, What is LeSS?
• The LeSS Company, LeSS Rules (November 2024)
• Scrum.org, The Nexus Guide (January 2021)
• Jeff Sutherland and Scrum Inc., The Scrum@Scale Guide, Version 2.1 (February 2022)