Most Teams Adopting Scaling Frameworks Do Not Need Them
The scaling agile industry — SAFe, LeSS, Nexus, Scrum@Scale, and their variants — exists to solve a real problem: how do you coordinate multiple agile teams working toward a shared product without recreating waterfall planning at the portfolio level? The problem is genuine. The solution is frequently applied to organizations that do not have it.
The typical trigger for a scaling framework adoption is not coordination failure between teams — it is discomfort at the leadership level with the absence of a visible, organization-wide plan. Scaling frameworks provide that visibility. They produce PI planning events, program backlogs, feature roadmaps, and dependency boards. The artifact density is high. The sense of coordinated control is restored. Whether the teams are actually delivering faster or more coherently is a separate question that tends not to be asked with the same urgency.
The practical test for whether a scaling framework is warranted is whether the coordination problems the framework is designed to solve actually exist. Do multiple teams regularly block each other on shared dependencies? Do teams produce work that conflicts at the integration point? Is there a product-level roadmap that requires explicit ordering across teams that cannot be handled through team-level backlog management? If the honest answer to these questions is no, the framework is overhead looking for a problem.
The alternative for organizations with two to five teams working on related products is not a scaled framework — it is disciplined single-team agile practices combined with a lightweight coordination layer: a shared product backlog ordered by a product manager with authority to make priority decisions, regular cross-team integration points, and explicit agreements about shared services and interfaces. This is less impressive as an organizational diagram and significantly more functional as a delivery system.
Scaling frameworks are appropriate when coordination failure is real, measurable, and not addressable by simpler means. Adopting them preemptively, or in response to executive anxiety about visibility, typically produces the coordination overhead of a scaled framework without the coordination benefit. The teams slow down. The reporting improves. These outcomes are not the same thing.