The Scaled Agile Framework — SAFe — is a body of knowledge, a set of principles, and a collection of practices designed to help large organisations work in an agile way. At the level of an individual team, agile is relatively well understood. SAFe addresses what happens when you need dozens or hundreds of teams to work in a coordinated, aligned, and genuinely agile way at the same time.

What problem SAFe solves

Team-level agility and enterprise-level agility are genuinely different problems. A small team can adopt Scrum or Kanban and be delivering well within a few months. A large organisation with multiple products, hundreds of developers, complex dependencies, and a variety of legacy processes faces challenges that team-level frameworks were not designed to address.

SAFe provides a structured approach to these enterprise-level challenges: coordinating multiple teams working on a shared product, aligning delivery with strategic priorities, managing dependencies across programmes, and maintaining quality at scale. It is comprehensive — sometimes exhaustively so — and that comprehensiveness is both its main strength and its most common criticism.

The core values

SAFe is built on four core values: alignment, built-in quality, transparency, and programme execution. Alignment means that planning and reflection happen at all levels of the organisation, with information flowing in both directions. Built-in quality means that quality is an expectation at every stage, not a checkpoint at the end. Transparency means that progress, plans, and problems are visible across the organisation. Programme execution is the practical heart of SAFe — the discipline of delivering working software and business value on a regular, predictable cadence.

The key structural elements

The Agile Release Train (ART) is SAFe's primary coordination mechanism. An ART is a long-lived team of agile teams — typically 50-125 people — that works on a shared value stream, delivers value on a regular cadence, and plans and executes together. The ART replaces the project as the primary unit of delivery in SAFe organisations.

Programme Increment (PI) Planning is the event that brings an entire ART together — in person if possible — to plan the next 8-12 weeks of work. It is an intensive, two-day event that produces a shared plan, identifies dependencies, surfaces risks, and creates genuine cross-team alignment. For many organisations adopting SAFe, PI Planning is the single most impactful change they make — because it creates coordination that had previously been absent or informal.

How it relates to other frameworks

SAFe incorporates elements from Scrum, Kanban, Lean, DevOps, and system thinking. It is not a replacement for these — it is a structure within which they can be applied consistently at scale. Teams within an ART typically use Scrum or Kanban for their own work; SAFe provides the coordination layer above them.

Other scaling frameworks — LeSS, Nexus, Disciplined Agile — take different approaches to the same problem. SAFe tends to suit larger, more complex organisations with significant existing process and governance structures. Lighter frameworks may be more appropriate for organisations that are smaller, more homogeneous, or that are starting from a cleaner slate.

Choosing whether SAFe is right for you

The honest answer is that SAFe works well in organisations that genuinely need the coordination it provides and are prepared to invest in the cultural change it requires. It is not a solution for small organisations, and it is not a solution for organisations that adopt the mechanics without the culture. The framework is a tool. Like any tool, what you get out of it depends significantly on whether you are using it for the right job.