Leading SAFe (SAFe 6.0)

“Every company is now a software company.” — Satya Nadella, CEO, Microsoft.

See Also:

Leading SAFe  equips leaders and change agents with the knowledge and tools to build a culture of agility, align strategy with execution,  improve productivity, and ultimately lead successful enterprise-scale change. It provides a high-level overview for those who are responsible for planning and making the changes necessary for an agile transformation.

The target audience is anyone leading or supporting a SAFe transformation initiative including executives, managers, and directors, change agents, coaches, RTEs, Product Managers, Solution and Systems Architects, program and project managers. 

The Leading SAFe course curriculum (version 6.0) is structured around six modules. These modules guide attendees through the knowledge and skills necessary to lead a Lean-Agile enterprise using the Scaled Agile Framework.

The six modules are:

1. Thriving in the Digital Age with Business Agility: Evaluates SAFe as an operating system for Business Agility and explores how the seven core competencies support this goal.
2. Leadership and Culture. Becoming a Lean-Agile Leader and stablishing a new way of working within the organization. How to apply a Lean-Agile mindset at scale and how to apply SAFe principles to enable business agility.
3. Establishing Team & Technical Agility: Accelerating value delivery. Focuses on forming cross-functional Agile teams and organizing Agile Release Trains (ARTs) around the flow of value.
4. Building Solutions with Agile Product Delivery: Covers applying customer centricity and design thinking, participating in PI planning, and building a Continuous Delivery Pipeline with DevOps.
5. Exploring Lean Portfolio Management: Agility at the strategy level. Defines and connects the SAFe portfolio to enterprise strategy, managing vision, funding value streams, and establishing portfolio flow.
6. Leading the Change: Focuses on navigating the transformation and leading the enterprise towards a Lean-Agile way of working.

1. The Digital Age & Business Agility

What this module covers:

• Why “operating at the speed of change” requires adaptable organizational structures, not just faster projects.
• SAFe as an operating system for Business Agility: the seven core competencies and how they connect.
• Flow as the leading indicator of value.

Core concepts & ideas:

• Business Agility: the ability to sense and respond continuously to change.
• SAFe Core Competencies – These are the enabling competencies for Business Agility:
  1) Team & Technical Agility, 2) Agile Product Delivery, 3) Enterprise Solution Delivery, 4) Lean Portfolio Management, 5) Organizational Agility, 6) Continuous Learning Culture, 7) Agile Leadership.
• Flow metrics: (time-to-learn, time-to-value, WIP, throughput, predictability) beat output metrics for guiding decisions.

How to use SAFe as an operating system:

1. Map your business value streams from idea→cash.
2. Align teams into ARTs around value (not functions).
3. Establish cadences (iterations, PIs) and synchronization (system demos).
4. Make work and policies explicit and visible; limit WIP.
5. Measure and improve flow, predictability, and customer outcomes.

Business Agility is the ability to engage and prosper in the digital era by adapting swiftly to market changes and new possibilities with creative, digitized business solutions. It involves a combination of technology, leadership, culture, and processes that allow businesses to quickly adapt to market changes and to continuously deliver value to customers. Key components include customer-centricity, iterative planning, cross-functional collaboration, and a focus on speed and learning.

SAFe leverages multiple bodies of knowledge, including agile delivery methods, lean, systems thinking, agile leadership, portfolio management and business strategy. SAFe continues to evolve, and since the release of SAFe 5, the framework has been redefined in terms of Seven Core Competencies and has been positioned as a solution to the broader challenge of Business Agility. The Seven Core Competencies are designed to support a shift from Scaled Software Delivery to a more comprehensive Business Agility and include topics like Organizational Agility and Lean Portfolio Management. SAFe provides a framework or reference model for scaling agile principles and practices across the entire organization.

Key aspects of business agility in the digital age

• Customer-centricity: Agile businesses prioritize understanding and responding to customer needs quickly, aiming to create superior experiences.
• Rapid Response: The ability to quickly develop and launch new digital products and services is crucial for staying competitive, as market disruption is the norm.
• Strategic Adaptability: Strategic agility involves continuously reassessing priorities and adapting long-term vision based on market feedback and emerging opportunities.
• Operational Agility: Operational agility means extending agile principles beyond software teams to other functions like HR, finance, and marketing, often using cross-functional teams and adaptive budgeting.
• Cross-functional Collaboration: Breaking down silos to foster closer ties between departments allows the entire organization to focus on delivering value rather than on functional goals.
• Continuous Delivery: Regularly delivering value to customers through frequent, incremental outcomes and shortening feedback loops is a hallmark of agile organizations.
• Dynamic Workforce: Cultivating a workforce that is ready to adopt new digital technologies is essential for successful and sustained digital transformation.

Benefits of business agility

• Increased innovation: The ability to bring new ideas to market more quickly.
• Improved productivity: Enhanced collaboration and adaptability in work practices.
• Greater efficiency: More efficient processes allow for a faster response to market changes.
• Higher success rates for digital transformation: A more dynamic and adaptable workforce makes digital transformation strategies more likely to succeed.
• Stronger competitive advantage: The ability to learn and adapt faster than competitors is a key competitive currency.

Challenges in achieving business agility

• Leadership and culture: The biggest challenges often lie in leadership’s ability to manage change and in the overall company culture.
• Organizational structures: Unsuitable structures, practices, and processes can hinder agility.
• Mindset: A resistance to change and adopting new ways of thinking can be a significant obstacle.

The Seven Core Competencies

The Seven Core Competencies of SAFe constitute a framework for the broader goal of Business Agility – not just for scaling software delivery. Each core competency has 3 dimensions that define Key Practices, Roles & Responsibilities, and Values & Principles that support that competency area. Here’s a summary:

• The Lean-Agile Leadership Core Competency is the foundation of the entire framework. This competency area comprises the Lean-Agile Principles plus additional SAFe-specific  Principles and emphasizes the necessity for an organization’s leadership to exemplify these principles in their leadership behaviors.
• Team & Tech agility: Accelerating value delivery. Small cross-functional teams, with the ability to deliver working increments of a product or solution as the output of every iteration – using the important principle of building quality in.
• Agile Product Delivery – defines a delivery model using teams-of-teams – known as Agile Release Trains (ARTs), operating in fixed-width timeboxes (PIs) to plan and deliver solutions. DevOps and the Continuous Delivery Pipeline creates the foundation that enables enterprises to release value, in whole or in part, at any time it’s needed
• Enterprise Solution Delivery provides an additional layer of governance for creating large solutions requiring the capacity of multiple Agile Release Trains.
• Lean Portfolio Management – agility at the strategy level. This is where we connect strategy to execution. It also covers topics like Lean Budgeting – Lean Budgeting is an adaptive approach for investment funding among multiple value streams in a portfolio.
• Organizational Agility: the ability of an organization to sense and quickly respond to threats and opportunities in the fast-changing business environments of today. Everyone delivering solutions has received training in lean and agile methodologies and adheres to its principles, values and practices.
• Continuous Learning Culture: is about how Organizations must embrace continuous improvement as a way of life, and where everyone in the organization must be involved in change & continuous improvement. This is accomplished through establishing a learning organization committed to continuous improvement and development, fostering a culture of innovation.

The Seven Core Competencies:

The Seven Core Competencies are designed to support a shift from Scaled Software Delivery to a more comprehensive Business Agility and include topics like Organizational Agility and Lean Portfolio Management. Scaled delivery using teams-of-teams remains at the foundation with Agile Product Delivery and Team and Technical Agility competencies.

2. Lean-Agile Leadership

What this module covers:

• The role of leaders in enabling agility (not supervising it).
• Lean-Agile mindset at scale; SAFe Principles as decision heuristics – simplified rules and frameworks to guide choices in complex development environments.
• Psychological safety and decentralized decision-making.

Leadership moves that matter:

• Lead by example: model transparency, limit WIP, attend system demos, ask for evidence.

• Decentralize decisions: push control to those closest to the work; clarify the guardrails (budgets, architectural runway, NFRs).
• Grow people & teams: coaching, pairing, multi-learning, communities of practice.

Applying SAFe Principles (practical lens):

• #1 Take an economic view → Use WSJF & cost-of-delay in prioritization.
• #6 Visualize and limit WIP, reduce batch sizes → Improve flow reliability.
• #9 Decentralize decision-making → Faster local decisions within clear constraints.

Anti-patterns to avoid:

• “Agile by announcement” without leader behavior change
• Measuring people by utilization instead of outcomes
• Centralized approvals that disrupt flow.

Lean-Agile leadership is a core competency that drives organizational change by empowering individuals and teams by leaders embodying a Lean-Agile mindset, principles, and practices. Leadership is most effective when actions align with words. The most effective approach for driving cultural change is for leaders to lead by example and to demonstrate the behaviors and mindsets needed to succeed so others can follow. Only leaders have the authority to change the organization such as enabling organizing around value, and creating an environment that fosters continuous improvement and innovation. Change must be inspired, not mandated. Effective leaders provide vision, mobilize teams, and swiftly remove obstacles.

By combining Lean and Agile principles and methods, organizations can streamline processes while staying responsive to customer needs, ultimately driving better outcomes and continuous improvement:

• Lean focuses on eliminating waste, optimizing processes, and maximizing value with minimal resources. It drives efficiency by continuously identifying and removing non-value-adding activities in all work areas, from product development to delivery.
• Agile emphasizes adaptability, collaboration, and delivering working solutions frequently. It helps teams respond to change quickly, ensuring that products meet evolving customer needs and that feedback loops drive continuous improvement

Key components of Lean-Agile leadership

• Embracing the Mindset and Principles: Leaders need to internalize and consistently apply Lean-Agile values and principles in their own beliefs and actions.
  • Lean-Agile Mindset
  • SAFe Core Values
  • SAFe Lean-Agile Principles
• Leading by Example: Leaders must model Lean-Agile behaviors, demonstrate a growth mindset, and be accountable for their actions and the system’s outcomes.
• Guiding and Empowering Teams: The role is to facilitate, coach, and motivate teams, creating a decentralized decision-making environment where those closest to the work can make choices.
• Focusing on Value Flow: Leaders are responsible for organizing and reorganizing around value streams, continuously identifying and reducing bottlenecks, queues, and excess Work in Progress (WIP).
• Driving Continuous Improvement: This involves eliminating demotivating policies, inspiring others, and creating a culture of relentless improvement and innovation.
• Creating a Supportive Environment: Leaders must create the necessary conditions for teams to thrive, providing the space for them to learn, innovate, and experimen

3. Team and Technical Agility

What this module covers:

• Cross-functional Agile Teams
• Built-in Quality
• Organizing around value with ARTs
• Technical practices that enable frequent integration and quality

The aim of the Team and Technical Agility competency is to form value-stream-aligned cross-functional teams that are capable of creating customer value consistently and repeatably as the output of every development iteration. Agile teams are cross-functional and self-organizing and embrace the SAFe principle of Building Quality In. This principle is supported by DevOps practices like Trunk-Based Development, Continuous Integration, Test Automation, and delivering in small, frequent batches. See this companion article on ART Design – Organizing Around Value.

Team practices:

• • Trunk-based development, CI, automated tests, feature toggles
  • Definition of Done, shared, testable, and enforced.
  • Small slices: most stories completed in 1–3 days; acceptance criteria explicit.

Starting playbook

1. Form stable, cross-functional teams (<10 people).

2. Create shared DoD + quality gates (build→test→scan).

3. Establish CI in a shared repo; integrate daily.

4. Visualize WIP and limit it; swarm to finish.

Metrics to watch

• • Flow time (idea→production), % stories completed in 1–3 days, escaped defects, lead time for change

4. The SAFe Agile Product Delivery Model

What this module covers:

• Customer centricity + design thinking
• The ART Backlog: Ready features sized to a PI; ranked by WSJF
• PI Planning essentials and creating a Continuous Delivery Pipeline
• Develop on Cadence, Release on Demand

Enterprise software delivery requires the capacity of multiple development teams, multi-sprint delivery cycles and solid alignment between product strategy, planning and execution. SAFe is an agile delivery system for enterprise-scale software development. It is designed to address the limitations of single team-based delivery. The SAFe framework defines a set of organizational and workflow patterns for scaling agile delivery beyond single teams.  Specifically, SAFe addresses:

• Scaling delivery capacity with multiple delivery teams.
• Multi-sprint planning increments.
• Organizing delivery teams around products vs. short-term temporary projects.
• Scaling Agile methods beyond software teams (financial governance and strategic alignment).

SAFe delivery is based on a Develop-on-Cadence, Release-on-Demand model. To support this approach, planning and delivery occurs within fixed width timeboxes of 4-6 sprints known as Planning Increments (PIs). Many organizations plan in quarterly increments (6 sprints). Within each Planning Increment, multiple delivery teams, organized into Agile Release Trains (ARTs), plan and execute against an ART Backlog, producing potentially releasable product increments every 2 weeks. Actual releases to production are based on business demand. In this way the process of releasing is decoupled from the development cadence. Each team within an ART is a standard Scrum Team (or sometimes a Kanban Team), and an ART may comprise up to a dozen teams. Additional roles are employed to coordinate planning and execution across the ART. Specifically, a Product Manager owns and manages the overall ART Backlog, which is the single source of work for all teams in the ART, and a Release Train Engineer (RTE), facilitates all ART-level events, including PI Planning and execution governance events within each PI.

Teams produce features incrementally via short iterations that deliver production-quality code. Most teams use the scrum framework to accomplish this. Additional engineering practices like Continuous Integration and Test Automation, supported with DevSecOps tools are used to ensure that quality and security is built into every iteration. At the end of each sprint, the combined work of all teams is integrated to produce a working system increment which can be demonstrated to stakeholders at System Demo events.

• Organizational Model: Value Stream-Aligned Agile Release Trains (ARTs). Up to 12 Teams per ART. An ART has all skills to create working increments of the Product or Solution. Each team on an ART cam independently create value. See this article on ART Design.
• Customer Centricity and Design Thinking: Customer centricity and design thinking inform the ART backlog by using design thinking to validate customer needs, and then by feeding the prioritized features and capabilities into the ART backlog for development. This is a continuous process where the mindset of customer centricity ensures the backlog is always aligned with customer value, while design thinking provides the iterative methods to validate solutions before they are committed to the backlog. This flow ensures that what is built in the backlog is what the customer actually desires, feasible, and economically viable. Validated features from the design thinking process become the starting point for the backlog. As features are developed and released, customer feedback is continuously gathered during events like the System Demo. This feedback is used to refine the backlog, making the process cyclical and ensuring continuous alignment with customer needs. 
• Planning Model: Based on time-boxed Planning Increments (PIs). Timeboxes of 4-6 sprints (8-12 weeks). More on PI Planning in this article.
• Execution Model: Teams operate with a common sprint cadence and common definition of done. Solution increments demonstrated every sprint.
• Strategy Alignment: ART Backlog traceable to Portfolio Backlog and business strategy. More on Lean Portfolio Management concepts here.

5. Lean Portfolio Management (LPM)

What this module covers:

• Connecting strategy to execution without command-and-control.
• The Portfolio Kanban, epic hypothesis statements, and guardrails.
• Funding value streams, not projects.

Lean Portfolio Management (LPM) is a discipline within SAFe that applies Lean principles to align strategy with execution and optimize the flow of value across an organization’s portfolio. It focuses on connecting strategic themes with the agility of portfolio and program execution through three core components: Strategy and Investment Funding, Agile Portfolio Operations, and Lean Governance. Key practices include using a Portfolio Kanban to manage flow, participatory budgeting to allocate funding, and establishing a clear portfolio vision and roadmap. 

Core Components

• Strategy and Investment Funding: Connects the portfolio to the enterprise’s broader business strategy, establishes budgets for value streams, and sets a clear portfolio vision and roadmap.
• Agile Portfolio Operations: Involves managing the portfolio Kanban, coordinating value streams, and supporting the execution of agile teams across the organization.
• Lean Governance: Incorporates practices like participatory budgeting, which is more flexible than annual budgeting, and uses metrics to measure portfolio performance and ensure compliance. 

Key Practices and Tools

• Portfolio Kanban: A system for visualizing and managing the flow of work (such as epics) through different stages, helping to identify and eliminate bottlenecks.
• Participatory Budgeting: A lean approach to funding that allocates budgets to value streams instead of individual projects, allowing for more flexibility and autonomy.
• Lean-Agile Principles: The entire LPM process is built on Lean and Agile principles, emphasizing speed, adaptability, and continuous value delivery to customers.
• Connecting Strategy to Execution: A central goal is to ensure that the work being done at the team level directly supports the company’s strategic objectives. 

Benefits

• Improved Alignment: Ensures that the entire organization is working toward the same strategic goals.
• Increased Agility: Allows for flexible responses to market changes by adapting budgets and priorities as needed.
• Faster value delivery: Optimizes the flow of work to deliver value to customers more quickly and efficiently.
• Reduced waste: Prevents resources from being wasted on non-prioritized or low-value initiatives.
• Higher ROI: Improves the return on investment by ensuring that resources are focused on the most impactful work. 

6. Leading the Change

What this module covers:

• Leading the change
• SAFe Implementation Roadmap
• Inspect & Adapt (I&A) as the engine for improvement

The leadership team owns the change and the resulting outcomes. They provide strategic oversight and executive sponsorship. This is why the first Core Competency – Lean-Agile Leadership – is the foundation of the entire framework. As Deming put it: “It is not enough that top management commit themselves for life to quality and productivity. They must know what it is that they are committed to – that is, what they must do. These obligations cannot be delegated. Support is not enough; action is required.”

Leaders must be not only be committed but engaged. They play an active role as mentors, coaches, impediment removers/problem solvers, and must invest time and resources accordingly. To do this, they must understand what needs to be done and how to get it done.

SAFe has recommended a series of steps for adoption. This approach has proven to be effective across many organizations, and can be summarized as follows:

Details will vary by organization based on their needs, but essential steps include:

• Make the Go SAFe decision.
• Train internal change agents and organizational leaders needed to own and actively support the transformation.
• Identify Value Streams. These are the products and/or services that the organization provides. For IT organizations that exist to support business operations, identify the fundamental business processes that must be supported, for example hiring/onboarding, payroll, supplier contracts, and so on. Identify the systems and teams needed to support these value streams. Setting up ARTs based on Value Streams is one of the most consequential actions that can be taken by an organization for successful delivery at scale. (See Chapter 2 of the eBook for more).
• Start with one or a small number of ARTs. Ensure ART roles (Product Managers and RTEs) are in place and trained. Train the ARTs in PI Planning and PI Execution.
• Provide coaching for the ARTs as they plan and execute their first PI.
• Learn, and make any necessary adjustments to the basic framework, then launch more ARTs.

SAFe provides a framework, or reference model, that must be tailored and evolved by each organization beyond its baseline patterns. This takes time but it is important to leverage the built-in Inspect & Adapt mechanisms to learn from experience and continuously improve.

Further Reading and Resources

Download the Leading SAFe 6.0 Guide for Change Agents — a practical, no-fluff handbook for mastering Lean-Agile leadership, flow, and value delivery.

Download the Leading SAFe eBook!