Scrum works well for one team of seven or so people. Big companies, though, have dozens of teams that depend on each other, plus portfolios of work that executives need to steer. The Scaled Agile Framework (SAFe), introduced in 2011 by Dean Leffingwell, is a popular attempt to answer that problem, and more of our clients are asking about it.

Why it appeals

SAFe organizes agile work into three levels: team, program, and portfolio. Its appeal is that it gives large organizations a recognizable structure for each level, so executives can see where agile fits with budgets, roadmaps, and governance.

Three ideas stand out:

• Teams of teams. Several agile teams work toward a shared goal and deliver together on a common schedule, often called a release train. The teams plan, build, and integrate in step.
• Shared planning. Everyone involved gathers in one place for a planning event that can last a couple of days. Teams see each other’s dependencies, agree on commitments, and leave with a plan they all understand. Anyone who has watched six teams discover a conflict in month five will see the value.
• Alignment. Work at the team level connects to program priorities, which connect to portfolio priorities. Fewer teams build things nobody asked for.

For a company that has run Scrum in pockets and now wants agility across a department of a few hundred people, this is a real help.

The cautions

We’re excited, and also careful. A few things worry us.

First, a framework can become the new bureaucracy. SAFe comes with a catalog of roles, artifacts, and meetings. Adopted wholesale, it can swap one heavy process for another with different names. If your teams spend more time on ceremonies than on customers, something went wrong.

Second, renaming isn’t changing. We’ve seen organizations relabel project managers as something else and phase gates as something else, then wonder why delivery looks the same. A new vocabulary on top of the old habits is the most common failure we worry about.

Third, tools and training can substitute for thinking. Buying the framework doesn’t give you the culture of trust, small batches, and fast feedback that makes agile work.

How we’d approach it

Treat SAFe as a menu, not a mandate. Start with the pieces that solve a problem you have today: perhaps shared planning for teams that keep colliding, or a clearer link between portfolio priorities and team backlogs. Add roles and events only when someone can explain what pain they remove.

Apply one test to every element you adopt: does it help teams deliver working software sooner, or does it help us feel organized? Keep the first kind. If you’d like help deciding which pieces fit your organization, we’re glad to talk.