• Agile & Scrum Basics

SAFe: Scaled Agile Framework at Scrum Academy

The Scaled Agile Framework, also abbreviated to SAFe, is a body of knowledge based on Lean and the Agile way of working. SAFe provides patterns, principles and tools to successfully develop large-scale products.

Scaled Agile Framework is incredibly popular right now. Why? Because SAFe allows larger organizations to pry themselves away from slow bureaucratic processes and deliver value faster using Agile and Lean principles. Air France KLM, Philips and the Tax Office … all SAFe. But what exactly is SAFe? SAFe has a lot of jargon, but this basic article will get you started.

In this article, we discuss the following topics:

• What is SAFe?
• What are the benefits of SAFe?
• The 4 levels of SAFe
• Who is SAFe suitable for?

What is SAFe?

Scaled Agile Framework is a framework with Agile tools and principles for larger organizations. The basic idea is that the framework scales so well that hundreds of people can collectively work Agile on the defined objectives. The goal is to enable large organizations to smoothly and flexibly deliver customer value.

Scaling Agile work can be done in different ways. Of course, the Scrum method is one of them, but now we also have the SAFe method. In both cases, it’s about getting rid of structures that get in the way, so you can quickly deliver value for your customers. SAFe often works on a slightly different level and is very applicable within larger organizations.

SAFe introduces several new roles and events. In particular, the purpose of these new roles and events is to achieve a level of alignment among all stakeholders. SAFe is popular because this framework works with recognizable organizational layers. For each layer, responsibilities are distributed. And SAFe offers the possibility to keep scaling up. Incidentally, SAFe works optimally with organizations that are already familiar with the Scrum method.

What are the benefits of SAFe?

Extension for Agile

SAFe has expanded Agile working and does not use new techniques to do so, but rather deploys existing elements such as user stories and features.

Business-oriented

The SAFe framework focuses on the business level. Only later does it look at specific components, such as the user story.

Specifically

The framework enhances the Agile way of working within complex organizations and systems. The framework does offer developers enough flexibility so that it is and remains applicable.

Light framework

The framework is easy to master. This is because it is a logically designed framework. The simple explanations and graphics make it easy to learn and use.

Practically applicable

SAFe is not a complete strategy that can be implemented overnight. Rather, it provides the best approach to developing the process itself.

Insightful

The model also includes all the roles we see more often on larger projects. This makes it very recognizable and insightful.

The 4 levels of SAFe

1. Team

At this level, SAFe can be compared to a Scrum team. In fact, the team is also self-organizing. The associated roles are Product Owner, Scrum Master and the Development Team. They meet biweekly.

The backlog is the responsibility of the Product Owner. In a planning meeting, the user stories for the next two weeks are chosen. Every day there is a Daily Scrum. There is also a retrospective, supervised by a Scrum Master, to identify improvement opportunities. Then the cycle begins anew.

2. Program

At this level, 5 to 12 Agile teams work together in an Agile Release Train. We also abbreviate this to ART. To perfectly align the work, they have PI Planning (Program Increments) every 3 months. In PIs, Agile teams align future work and set the course. The Business Owners do this because they represent the customer. They provide the goals that teams will work toward over the next 3 months. At this level, the roles are as follows:

• someone responsible for the process (Release Train Engineer);
• someone responsible for the product (Product Manager);
• someone responsible for technology (System Architect).

3. Large Solution

Large Solution provides the method for multiple Agile Release Trains to work side by side. For example, a number of ARTs work together to develop the product. This involves hundreds of employees. This is what Microsoft does, for example. To manage this complexity, an additional layer is needed. At this level, the roles are as follows:

• someone responsible for the process (Solution Train Engineer);
• someone responsible for the product (Solution Management);
• someone responsible for technology (Solution Architect).

There will be a higher layer with Lean Agile Leadership. So with this you are still at the organizational level.

4. Lean Portfolio Management

There is often the idea of being able to respond to opportunities and changing markets as an entire organization. At this highest level, strategic themes are determined by Epic Owners, in collaboration with key stakeholders. Priorities are also set and Agile budgets allocated at this level.

You don’t have to move to SAFe as an entire organization all at once. It can be done incrementally and based on experience. That, of course, is true Agile working.

Who is SAFe suitable for?

Actually, SAFe is especially suited to large organizations where large groups of employees work together on complex products in environments that are changeable. Consider, for example, a company like Tesla. Technology and the market are constantly changing and people are working on a complex product.

Opportunities, problems, possibilities. Structure is needed. At the same time, you want rap to market at the moment of need. Think about updates, for example. SAFe provides that structure and is very valuable for large organizations, but can already be well deployed in organizations as small as 50 employees.