What is SAFe?
The Scaled Agile Framework (SAFe®) helps businesses address the significant challenges of developing and delivering enterprise-class software and systems in the shortest sustainable lead time. It is as an online, freely revealed knowledge base of proven success patterns for implementing Lean-Agile software and systems at enterprise scale.
SAFe synchronizes alignment, collaboration, and delivery for large numbers of Agile teams. Scalable and configurable, SAFe allows each organization to adapt it to its own business needs. It supports smaller-scale solutions employing 50–125 practitioners, as well as complex systems that require thousands of people.
An extensive body of knowledge, SAFe describes the roles, responsibilities, artifacts, and activities necessary to implement Lean-Agile development. To illustrate SAFe concepts, this website features an interactive Big Picture graphic, which is a visual overview of the framework and is the primary user interface to the knowledge base. Each icon of the image is clickable, offering access to an article on that topic, as well as links to related information.
Improving System Development Outcomes
Developed in the field, SAFe has evolved as a proven approach for developing complex systems and software in a Lean-Agile manner and draws from three primary bodies of knowledge: Agile development, systems thinking, and Lean product development. It helps enterprises answer the following types of questions:
- How do we align the enterprise toward common business and technical goals? How do we make better decisions to improve our economic outcomes?
- How do we deliver new value on a predictable schedule so that the rest of the business can plan and execute? How do we improve the quality of our solutions and delight our customers?
- How do we scale Agile practices from the team to the larger program and business unit, and across the enterprise, to deliver better results? How do we organize teams around value so that our programs deliver it effectively and avoid the delays and bureaucracy inherent in a traditional, hierarchical structure? How do we manage and minimize dependencies between teams, programs, and value streams?
- How do we create an environment that fosters collaboration, innovation, and relentless improvement? How do we unlock the intrinsic motivation of the people who do this work? How can we change our culture so that it tolerates failure and rewards risk-taking and continuous learning? How can we help our teams improve without getting in the way?
- How do we know that the new ways of working are more effective? How do we know what our Agile teams are doing and measure how well they’re performing?
By adopting SAFe— and applying its well-described set of values, principles, and practices— the enterprise can address these questions and realize greater business and individual benefits.
SAFe supports the full range of development environments with four out-the-box configurations, as illustrated in Figure 1.
- Essential SAFe
- Portfolio SAFe
- Large Solution SAFe
- Full SAFe
Together, the team and program levels form an organizational structure called the Agile Release Train (ART), where Agile teams, key stakeholders, and other resources are dedicated to an important, ongoing solution mission.
Essential SAFe consists of both the Team and Program levels, as shown in Figure 2. For more information, read the Essential SAFe guidance article here.
Portfolio SAFe configuration helps align portfolio execution to the enterprise strategy, by organizing agile development around the flow of value, through one or more value streams. It provides business agility through principles and practices for portfolio strategy and investment funding, Agile program guidance and Lean governance.
In the large Enterprise, there may be multiple SAFe portfolios. Learn more.
The Large Solution SAFe configuration is for developing the largest and most complex solutions that typically require multiple Agile Release Trains (ARTs) and suppliers, but do not require Portfolio-level considerations. This is common for industries like aerospace and defense, automotive, and government where the large solution—not portfolio governance—is the primary concern.
The Solution Train organizational construct of the Large Solutions level, helps enterprises that face the biggest challenges—building large-scale, multidisciplinary software, hardware and complex IT systems. Building these solutions require additional roles, artifacts, events, and coordination. Enterprises that build largely independent systems or those that can be built with a few hundred practitioners may not need this configuration. Learn more.
The Spanning Palette
The spanning palette contains various roles and artifacts that may be applicable to a specific team, program, large solution, or portfolio context. A key element of SAFe’s flexibility and configurability, the spanning palette permits organizations to apply only the elements needed for their configuration.
Figure 6 illustrates two versions of the spanning palette. The figure on the left is used for the Essential SAFe configuration and the one on the right is for all other configurations. However, since SAFe is a framework, enterprises can apply any of the elements from the larger spanning palette to Essential SAFe.
Below is a brief description of each spanning palette element:
- Metrics – the primary measure in SAFe is the objective measurement of working solutions. Moreover, SAFe defines a number of additional intermediate and long-term measures as well, metrics that teams, programs, and portfolios can use to measure progress.
- Shared services – represents the specialty roles that are necessary for the success of an ART or value stream, but that cannot be dedicated full time to any specific train.
- CoP – a Community of Practice (CoP) is an informal group of team members and other experts, acting within the context of a program or enterprise, that has a mission of sharing practical knowledge in one or more relevant domains.
- Milestones – a milestone is used to track progress toward a specific goal or event. These include fixed-date milestones, PI milestones and learning milestones.
- Roadmap the roadmap communicates planned ART and value stream deliverables and milestones over a time line.
- Vision – the vision describes a future view of the solution to be developed,
- reflecting customer and stakeholders needs, as well as features and capabilities, which are proposed to address those needs.
- System Team – this a special Agile team that provides assistance in building
- and using the Agile development environment, including continuous integration and test automation and automating the delivery pipeline.
- Lean UX – Lean UX is the application of lean principles to user experience design. It uses an iterative, hypothesis driven approach to product development, through constant measurement and learning loops (build – measure – learn). In SAFe, Lean UX is applied at scale, with the right combination of centralized and decentralized UX design and implementation.
Each foundation element, as shown in Figure 7, is briefly described below. oundation contains the supporting principles, values, mindset, implementation guidance and leadership roles needed to successfully deliver value at scale.
- Lean-Agile leaders – Management has the ultimate responsibility for business outcomes. To achieve that, leaders must be trained in, and become trainers of, these leaner ways of thinking and operating. To this end, SAFe describes a new style of leadership exhibited by the enterprise’s leaders.
- Core values – Four core values define the belief system for SAFe: alignment, built-in quality, transparency, and program execution.
- Lean-Agile mindset. Lean-Agile leaders are lifelong learners and teachers. They understand and embrace Lean and Agile principles and practices.
- SAFe Principles. SAFe practices are grounded in nine principles that synthesize Agile methods, Lean product development, systems thinking, and decades of field experience.
- Implementation Roadmap. Implementing the changes necessary to become a Lean-Agile technology enterprise is a substantial change for most companies. SAFe provides an implementation roadmap to help guide organizations on this journey.
- SPC – SAFe Program Consultants (SPCs) are change agents who combine their technical knowledge of SAFe with an intrinsic motivation to improve their company’s software and systems development processes.
Learn More Knaster, Richard; Leffingwell, Dean. SAFe 4.0 Distilled: Applying the Scaled Agile Framework for Lean Software and Systems Engineering.
Last update: 1 September, 2017