last updated 22 April 2017 by Kevin Trethewey

Origin

Dean Leffingwell describes the origin of SAFe as follows…

Over the last few years, I’ve worked extensively with a number of other professionals (including Drew Jemilo, Colin O’Neill, Alex Yakyma, Mauricio Zamora) in the implementation of a number of large enterprise lean|agile transformations. This collaboration has resulted in many back and forth discussions around implementation of the Scaled Agile Framework™. To date, this framework has been elaborated primarily in my books Agile Software Requirements, Scaling Software Agility, and blog).

Recently, we decided to formalize our collaboration with the intent of making the framework public-facing and more readily available to a larger audience, and we have also committed to developing certain extensions and enhancements to the framework that have presented themselves as the marketplace, agile enterprise maturity, and our thinking and experiences have evolved.

To that end, we will offer the Scaled Agile Framework (SAF) as a “proven, publicly available, framework for applying Lean|Agile practices at enterprise scale, presented in a structured, interactive, web format.”

Source: Dean Leffingwell, Introducing the Scaled Agile Framework™

Learning It

Our recommended way of learning about SAFe is through…

* the best way to get properly informed about any Archetype is to find people who are actively using it and to ask them about their experiences.

SAFe Spine

From the perspective of prospective users of SAFe…

Need (Where might it be used?)

To Do

Values (What does it optimise for?)

  1. Alignment
  2. Code Quality
  3. Transparency
  4. Program Execution

Principles (What is it based on?)

  1. Take an Economic View
  2. Apply Systems Thinking
  3. Assume Variability; Preserve Options
  4. Build Incrementally With Fast Integrated Learning Cycles
  5. Base Milestones On Objective Evaluation Of Working Systems
  6. Visualize and limit WIP, reduce batch sizes, and manage queue lengths
  7. Apply cadence, synchronize with cross-domain planning
  8. Unlock the intrinsic motivation of knowledge workers
  9. Decentralize decision-making

Practices (What does it suggest you do?)

To Do

Tools (What does it suggest you use?)

To Do


blog comments powered by Disqus

last updated 22 April 2017 by Kevin Trethewey

Origin

Dean Leffingwell describes the origin of SAFe as follows…

Over the last few years, I’ve worked extensively with a number of other professionals (including Drew Jemilo, Colin O’Neill, Alex Yakyma, Mauricio Zamora) in the implementation of a number of large enterprise lean|agile transformations. This collaboration has resulted in many back and forth discussions around implementation of the Scaled Agile Framework™. To date, this framework has been elaborated primarily in my books Agile Software Requirements, Scaling Software Agility, and blog).

Recently, we decided to formalize our collaboration with the intent of making the framework public-facing and more readily available to a larger audience, and we have also committed to developing certain extensions and enhancements to the framework that have presented themselves as the marketplace, agile enterprise maturity, and our thinking and experiences have evolved.

To that end, we will offer the Scaled Agile Framework (SAF) as a “proven, publicly available, framework for applying Lean|Agile practices at enterprise scale, presented in a structured, interactive, web format.”

Source: Dean Leffingwell, Introducing the Scaled Agile Framework™

Learning It

Our recommended way of learning about SAFe is through…

* the best way to get properly informed about any Archetype is to find people who are actively using it and to ask them about their experiences.

SAFe Spine

From the perspective of prospective users of SAFe…

Need (Where might it be used?)

To Do

Values (What does it optimise for?)

  1. Alignment
  2. Code Quality
  3. Transparency
  4. Program Execution

Principles (What is it based on?)

  1. Take an Economic View
  2. Apply Systems Thinking
  3. Assume Variability; Preserve Options
  4. Build Incrementally With Fast Integrated Learning Cycles
  5. Base Milestones On Objective Evaluation Of Working Systems
  6. Visualize and limit WIP, reduce batch sizes, and manage queue lengths
  7. Apply cadence, synchronize with cross-domain planning
  8. Unlock the intrinsic motivation of knowledge workers
  9. Decentralize decision-making

Practices (What does it suggest you do?)

To Do

Tools (What does it suggest you use?)

To Do