Scaled Agile Framework

Software development process
Core activities
Paradigms and models
Methodologies and frameworks
Supporting disciplines
Tools
Standards and BOKs

Scaled Agile Framework (or SAFe) is an Agile software development framework designed by Scaled Agile, Inc.

The Scaled Agile Framework (SAFe®) is a freely-revealed knowledge base of integrated patterns for enterprise-scale Lean-Agile development. It is scalable and modular, allowing an organization to apply it in a way that suits its need. The SAFe website provides comprehensive guidance for scaling development work across all levels of an enterprise. SAFe's interactive "Big Picture" provides a visual overview of the framework. Each icon on the website is selectable, navigating the user to an article which provides extensive guidance on the topic area, along with links to related articles and further information.

Introduction

SAFe synchronizes alignment, collaboration, and delivery for large numbers of agile teams. It supports both software and systems development, from the modest scale of under 100 practitioners to the largest software solutions and complex cyber-physical systems; systems that require thousands of people to create and maintain. SAFe was developed in the field, based on helping customers solve their most challenging scaling problems. SAFe leverages three primary bodies of knowledge: Agile development, Lean product development, and systems thinking.

SAFe was initially developed in the field and was elaborated in Dean Leffingwell's books and blog. Version 1.0 of SAFe, the first official release, was published in its current web site form in 2011. The latest version, renamed "SAFe 4.0 for Lean Software and Systems Engineering", was released in January of 2015.

SAFe has its critics among the Agile community for example Ron Jeffries (one of the three creators of XP (Extreme Programming) and one of the 17 original signatories of the Agile Manifesto) has stated that:

The structure and teaching of SAFe is relentlessly top down ... SAFe’s strength is that it appeals to large organizations who are not Agile. It confirms that the Big Guys know the stuff and that all that’s needed is for the Little Guys to rush around doing what they’re told. SAFe is trying to build a framework enterprises will buy.[1]

while Ken Schwaber (who worked with Jeff Sutherland to formulate the initial versions of the Scrum development process) wrote:

The boys from RUP (Rational Unified Process) are back. Building on the profound failure of RUP, they are now pushing the Scaled Agile Framework (e) as a simple, one-size fits all approach to the agile organization. They have made their approach even more complicated by partnering with Rally, a tools vendor. Consultants are available to customize it for you, also just like RUP.[2]

and David J. Anderson (who was among the first to formulate the Kanban methodology for application to IT and software development), stated:

It is assumed that the collected set of successful practices [which comprise SAFe] will also be successful in aggregate. I would compare this assumption to individually testing the 300,000 components in a modern passenger jet aircraft and then declaring that as all the components are tested the entire plane composed of those parts is SAFE![2]

Principles

SAFe is based on Lean and Agile principles.[3] The nine SAFe principles are:

  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

Levels

There are two different types of SAFe 4.0 implementation, 3-Level SAFe and 4-Level SAFe. 3-Level SAFe is for smaller implementations with 100 people or less, or multiple such programs that do not require significant collaboration. 4-Level SAFe is for solutions that typically require many hundreds of practitioners to develop, deploy and maintain.

The levels in 3-Level SAFe are Team, Program & Portfolio.

Team

A SAFe team is an agile team —most SAFe teams apply XP (Extreme Programming) of 7-9 people that has the skills they need to define, develop, test and deliver value.

Program

Together, 5-10 SAFe teams create an "Agile Release Train", with typically 50 to 125 persons, including the development teams and other stakeholders. They synchronize their iteration boundaries and deliver integrated, working systems every two weeks.

The Program Increment is a larger, quantum measuring point, which typically occurs on a cadence of 3-5 development iterations, followed by one Innovation and Planning (IP) Iteration. Each PI concludes with a demo of all the functionality that has been developed through the course of the PI. This is accompanied by an Inspect and Adapt session that includes root cause analysis and identification of systematic improvements.

The Innovation and Planning iteration supports the dedicated time for PI system demo, innovation and face to face PI planning. This describes the basic development cadence, which synchronizes teams to a common mission and cadence, and focuses on the frequent integration of the full system. However, Teams and Programs can release functionality at any time the market demands, including continuous delivery.

Portfolio

A portfolio is a collection of value streams which are budgeted via lean-agile budgeting mechanisms. The portfolio is connected to the enterprise strategy by a set of strategic themes. A portfolio kanban system is used to capture and analyze epics - large,cross-cutting initiatives that affect multiple Agile Release Trains.

Value Stream

4-level SAFe includes a new Value Stream level. This level is designed for those organizations which are building large systems, although any enterprise can benefit by incorporating from various value stream constructs in there implementation.

Certifications

There are a number of different SAFe certifications which provide the training, knowledge and necessary tools for various levels of the Scaled Agile Framework.[4]

  1. SAFe Agilist (SA)
  2. SAFe Practitioner (SP)
  3. SAFe Program Consultant (SPC)
  4. SAFe Product Manager / Product Owner (SPMPO)

See also

Notes

  1. ↑ Bloomberg 2014, p. 2.
  2. 1 2 Elssamadisy 2013.
  3. ↑ "SAFe Lean-Agile Principles". Retrieved 19 February 2016.
  4. ↑ "Certification". Scaled Agile. Retrieved 19 February 2016.

References

Further reading

External links

This article is issued from Wikipedia - version of the Tuesday, April 12, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.