Home/agile/Dean Leffingwell

Dean Leffingwellperson

safeenterprise-scalingscaled-agile-frameworkenterprise-adapter
2 min read · Edit on Pyrite

Dean Leffingwell is the creator of SAFe (Scaled Agile Framework), launched in 2011, and the most prominent architect of enterprise Agile scaling. SAFe is simultaneously the most widely adopted enterprise Agile scaling framework and among the most controversial, generating sustained critique from Agile traditionalists and post-Agile critics alike.

Path to SAFe

Leffingwell came to scaling Agile from an enterprise software background — specifically from work on requirements management and large-scale software development. His books before SAFe addressed the challenge of managing software requirements at scale, a problem that becomes acute when Agile's preference for lightweight, iterative requirements meets the planning and governance demands of large enterprises.

  • scaling-software-agility (2007) — addressed the problem of applying Agile practices in large organizations; established Leffingwell's framework for thinking about scaling
  • "Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise" (2010) — extended the scaling framework with a requirements-centric view; introduced concepts that would become formalized in SAFe

    • SAFe: The Scaled Agile Framework

    Leffingwell launched SAFe in 2011 through Scaled Agile, Inc. (scaled-agile-inc), the company he founded to develop and market the framework. The safe-launch-2011 marked the beginning of the enterprise-scaling-era as a distinct phase in Agile's development.

    SAFe addresses the coordination problem that pure Scrum doesn't solve: how do hundreds of teams, organized into programs and portfolios, align their work toward enterprise goals? SAFe introduces hierarchy — Team, Program, Large Solution, Portfolio levels — and coordination ceremonies (PI Planning, Agile Release Trains) designed to synchronize multiple Scrum teams.

    Why SAFe is controversial:

  • Critics argue SAFe recreates the planning and governance overhead of waterfall at a higher organizational level, defeating the purpose of Agile
  • The framework's size and complexity — SAFe's "Big Picture" diagram is famously dense — is seen as antithetical to Agile's value of simplicity
  • SAFe has been associated with the agile-industrial-complex critique: a large commercial enterprise selling certification, training, and consulting around a proprietary framework
  • SAFe is also criticized for being prescriptive in ways that conflict with teams' ability to inspect-and-adapt

    • Why SAFe persists and grows:

  • Large enterprises face real coordination problems that Scrum's team-level focus doesn't address
  • SAFe provides the governance vocabulary (portfolio management, program increments, value streams) that enterprise managers recognize
  • The SAFe certification industry has made it the default answer to "how does Agile work at scale" in enterprise contexts

    • Movement Role

    Leffingwell is the central figure of the enterprise-scaling-era — the period in which the Agile movement's primary challenge shifted from team-level adoption to enterprise-level scaling. His creation of SAFe is the defining framework event of that era, paralleling but contrasting with the emergence of less-large-scale-scrum and other scaling approaches. He represents the enterprise-adapter strand of Agile evolution — the attempt to make Agile work within, rather than against, existing enterprise structures.

    Linked from

    SAFe 1.0 Launch (2011) Scaled Agile, Inc. Scrum Dominance and Mainstream Adoption Enterprise Scaling Era SAFe (Scaled Agile Framework) Scaling Software Agility: Best Practices for Large Enterprises

    Links to

    Scaling Software Agility: Best Practices for Large Enterprises Scaled Agile, Inc. SAFe 1.0 Launch (2011) Enterprise Scaling Era Agile Industrial Complex Inspect and Adapt LeSS (Large-Scale Scrum)