SAFe

Developed by Anna Shevchenko

Agile methods of project management are becoming increasingly popular even outside their origins as methods to organize software development teams. While these methods cover the project management aspect, they do not provide guidance as to how to manage programs as a whole, and due to the particularities of agile project management, special methods of program management have been developed to handle project teams using an agile methodology. SAFe is one such method of Program Management focusing on synchronizing agile project teams while also following Lean principles ie. trying to deliver a maximum of value to the customer in the shortest sustainable lead time.

This article's purpose is to explain the SAFe methodology, its concept and its application in order to manage Programs composed of projects following Agile methods.

The SAFe method is articulated around four core values:

• Alignment of management and teams to a common mission,

• Built-in quality practices,

• Transparency,

• Program execution.

In order to pursue these values, SAFe organizes teams in stable teams of teams in the form of one or several Agile Release Train (ART). An ART is a networked organizational structure which relies on decentralized decision making for faster response times and higher reactivity.

SAFe is designed for scalability and is capable of supporting smaller scale programs involving less than a hundred team members as well as complex programs involving thousands of people. It is available in four different configurations depending on the needs of the user:

• Essential SAFe the basic version of SAFe upon which the other configurations build on;

• Portfolio SAFe to apply the SAFe methodology to Portfolio Management;

• Large Solution SAFe for complex solutions that involve multiple ARTs but do not need to consider Portfolio management;

• Full SAFe that is meant to apply the SAFe methodology at every level.

Concept

SAFe Principles

SAFe is based on nine main principles :

• Take an economic view

The main aim of SAFe is to make it possible for a company to deliver as much value as possible in the shortest sustainable lead time. SAFe achieves this through incremental value delivery and decentralized decision-making, which requires the creation of a strategy and an economic framework in the light of which decisions can be taken.

• Apply systems thinking

In order to fix problems, it is necessary to understand complex systems, which consist of multiples components related to each other. Focusing on one component of the system won’t make it possible to optimize the entire system. Moreover, it is important to be aware of the main goal of the system and to be committed to this goal. In order to apply SAFe, it is required to think of the system as a whole and not only of the organization which builds the system, but also to the systems under development.

• Assume variability; preserve options

SAFe follows a different approach for choosing design and life cycle practices from most practices. It keeps multiple design options and requirements for long time. SAFe uses empirical data to choose the right design and avoid excessively time consuming adjustments and suboptimal long-term design, which can result of a wrong design choice in early stages.

• Build incrementally with fast, integrated learning cycles

• Base milestones on objective evaluation of working systems

• Visualize and limit WIP, reduce batch sizes, and manage queue lengths

• Apply cadence, synchronize with cross-domain planning

• Unlock the intrinsic motivation of knowledge workers

Researchers proved that in order to achieve a high level of employee engagement it was needed to show purpose and give autonomy, and to put constraints at a minimum level. At the same time, individual incentive compensation will lead to internal competition and decrease cooperation, which will lead to longer times to achieve the goals of the system and will put both customers and the enterprise in an unfavorable position.

• Decentralize decision-making

The Essential SAFe

The Essential SAFe

Implementation

The SAFe Implementation Roadmap

The implementation of SAFe is done in three main phases:

• A preparation and planning phase
• A minimum application phase
• An expansion phase

During the first phase, key staff such as managers, leaders and change agents are trained in the SAFe method. ARTs and value streams are identified, and an implementation plan is created. Once this first phase is completed, the second phase starts by preparing for the ART launch and training the teams themselves in the SAFe method, then the first PI planning is organized and the ART is launched. A coaching in the SAFe ways is organized around that first ART, first focusing on the basics of SAFe but going deeper and deeper as the teams become more proficient. Once this first ART has been launched and a coaching team is organized around it, the third phase starts where SAFe is generalized and applied to more aspects of the company: more value streams and ARTs are launched, the method is extended to Portfolio management and the company globally tries to sustain and improve its processes.

The preparation and planning phase

Reaching the tipping point

The first phase's goal is to prepare the ground for the company to start using SAFe to manage a program consisting of projects that use Agile methods. This first step is usually taken after what SAFe calls Reaching the tipping point.

Every company tends to resist change in general and in particular to change in its way of working. However, change is sometimes needed and it becomes imperative for the company to achieve the change. In order to achieve such a massive change, it is needed to reach a tipping point where the required critical mass to enable rapid change is reached.

There are two main reasons why companies embrace change. The first is when the need for change is obvious: the performance of the company is dropping and the company needs to change its way of conducting business to survive, while the other is when leadership decided to achieve change proactively, believing implementing such a change will be beneficial for the future of the organization.

Train Lean-Agile Change Agents

At this point, the need for change has been recognized. A vision for this change must then be established. For an organization working in the Lean-Agile mindset, SAFe is one of the choices available to change their way of working and adapt to their evolving environment. To start preparing the implementation of this method, the first step is to Train Lean-Agile Change Agents. The purpose of this step is to establish a powerful coalition that will drive the implementation of the change throughout the organization.

Train Executives, Managers, and Leaders

Once change agents have been trained, the next step is to Train Executives, Managers, and Leaders. At its core, SAFe is a method used to manage a collection of projects along the Lean-Agile principles. Therefore, the principal stakeholders will be the program managers but also the project managers who manage the projects in the implicated programs. All those agents must be trained along with their leaders, those who will sponsor the change, and more generally all those who will be influencing or managing this change. This training occurs with the help of the change agents that were trained as part of the previous step.

Identify Value Streams and ARTs

After all the relevant stakeholders have been properly trained, the next step of the method is to Identify Value Streams and ARTs. This is done by first identifying the value streams: a value stream is basically a series of steps that are taken after some triggers the stream to achieve the production of value. For example, the trigger can be a customer ordering a product, the steps could be ordering raw materials, transforming them into the product that has been ordered, and delivering the product to the customer. The value produced is that of the final product, minus the costs incurred during the value stream. A value stream is of course identified by its trigger, its steps, and its value, but also by the people and systems it involves, as well as the time it takes to execute it.

After having identified the value streams, the organization needs to identify the ARTs that would enable it to execute those value streams as best as possible. An ART, standing for "Agile Release Train" is "a long-lived team of Agile teams, which, along with other stakeholders, incrementally develops, delivers, and where applicable operates, one or more solutions in a value stream." Depending on the value streams identified, each ART can either be responsible for multiple smaller streams, be responsible for a single value stream in its entirety, or collaborate with other ARTs to enable one larger value stream to be operated. The key for choosing how to affect teams to ARTs is that each ART must be designed to be big enough for its responsibilities but small enough to be reactive to its environment (the method recommends 50 to 125 people in each ART), and each ART must have as little dependency on other ARTs as possible, and must be able to release (ie. produce value) independently from other ARTs.

Create the Implementation Plan

Finally, the last step of this first part is to Create the Implementation Plan. According to Agile principles, incremental value delivery is key for maximum reactivity and adaptability. Therefore at this stage, only one value stream is selected. Once a value stream has been selected, the ART most suitable for executing this stream is selected along with it, and it is time to prepare for the first ART launch.

The minimum application phase

Prepare for ART Launch

Now that the implementation plan has been drafted, the next step in the implementation of SAFe is to Prepare for ART launch. During this step the definition of the ART is refined so as to better understand the context in which it will operate, its boundaries, its interactions with other systems, etc. After this, the launch date and the program calendar are set. The ART operates by cycles called Program Increment (PI), operating on a fixed cadence that can be set to any duration with eight to twelve weeks being recommended. Each PI includes a PI planning sessions at its start and can contain other items such as demos, introspective workshops, etc. Once this calendar is set, teams are reorganized into Agile teams if necessary, and should include a Scrum Master and a Product Owner along with the team members that directly create the value. At this point, Scrum Masters, Product Owners and Team managers receive training in SAFe, the launch readiness is evaluated, and once readiness is high enough the program's backlog is established. The program's backlog defines the scope of the Program by defining the various features that are to be developed, the non-functional requirements and the architectural work that define the future behavior of the system.

Train Teams and Launch the ART

The ART launch has now been defined. The next step at this point is to Train Teams and Launch the ART. At this point, all the team members receive SAFe training and, if necessary, Agile training as well. Each team must also establish its Team Backlog which identifies which features and requirements will be the responsibility of that team. Finally, the ART is launched with the first PI planning session.

Coach ART Execution

With the first ART having been launched, the preparatory work is now mostly finished and the next step is to Coach ART Execution to support the ART in its first iterations. Initially this coaching focuses on the individual teams to make them master their roles in the overall method. Coaching must also take place at program level, for example regarding PI planning sessions, demos, etc.

Limitations

SAFe's limitations pertain mainly to two categories. The first one is that it necessitates a lot of investment in training and coaching, or in the hiring of consultants in order to start applying it. The second one is that it takes away a lot of power from the individual teams in favor of a more centralized approach, which goes against the values of agile methodologies

• Heavy training required
• Less initiative left to the team members, less decision making occurs at the team level contrary to Agile principles
• Longer planning cycles than other methodologies based on Agile principles
• Requires relatively heavy administration, oversight and leadership layers

Bibliography

SAFe® 4.5 Introduction: Overview of the Scaled Agile Framework® for Lean Enterprises, Scaled Agile, Inc., August 2017

SAFe® 4.0 Reference Guide, Scaled Agile, Inc., August 2016