SAFe 6.0: A Game-Changer for Scaled Agile Organizations

Key Highlights

• SAFe 6.0 introduces significant changes to enhance business agility and improve the flow of value in scaled Agile organizations.
• The new version focuses on the Seven Core Competencies of SAFe, including agile leadership, Team and Technical Agility, Agile Product Delivery, Enterprise Solution Delivery, Lean Portfolio Management, Organizational Agility, and Continuous Learning Culture.
• The new version emphasizes Business Agility, Strategic Agility, and alignment between Business and IT to help organizations respond to market changes.
• SAFe 6.0 also covers the Business Agility Value Stream (BAVS) and the eight flow accelerators, which help organizations speed up value delivery and improve the flow of value.
• Organizations can use the SAFe 6.0 implementation roadmap to guide their transformation journey and overcome common implementation challenges.

Introduction

The Scaled Agile Framework (SAFe) is a framework for scaling Agile practices in large organizations. With the release of SAFe 6.0, significant changes have been introduced. SAFe 6.0 focuses on improving business agility, enhancing the flow of value, and aligning business and IT to deliver better outcomes.

SAFe 6.0 builds upon the success of previous versions and introduces key changes to address the evolving needs of enterprises in a rapidly changing marketplace. The new version emphasizes the Seven Core Competencies of SAFe, which are essential for organizations to become Lean-Agile enterprises. These competencies include Lean-Agile Leadership, Team and Technical Agility, Agile Product Delivery, Enterprise Solution Delivery, Lean Portfolio Management, Organizational Agility, and Continuous Learning Culture.

In this blog, we will explore the key highlights of SAFe 6.0, including the enhancements in business agility and the main changes. We will also discuss the implementation roadmap and how organizations can successfully transition to SAFe 6.0.

Unveiling SAFe 6.0: An Overview

SAFe 6.0 is the latest version of the Scaled Agile Framework, a comprehensive framework for scaling Agile practices in large organizations. It builds on the principles and practices of Agile methodologies and provides a structured approach to enable organizations to deliver value at scale. SAFe 6.0 introduces significant changes to enhance business agility, improve the flow of value, and align business and IT. It focuses on the Seven Core Competencies of SAFe and provides organizations with a roadmap for Agile transformation.

The Evolution of Scaled Agile Frameworks

Scaled Agile Frameworks, including SAFe, have evolved over the years to address the challenges of scaling Agile practices in large organizations. Agile methodologies, such as Scrum and Kanban, were initially designed for small teams and projects. As organizations started adopting Agile practices at a larger scale, the need for a framework that could facilitate the coordination and alignment of multiple Agile teams arose.

Agile frameworks, including SAFe, have undergone continuous improvement to address the complexities of scaling Agile practices. They provide a structured approach to enable organizations to deliver value at scale, improve collaboration, and enhance the flow of value. SAFe 6.0 is the latest version of the framework and introduces significant changes to further enhance business agility and align organizations with Lean-Agile principles. These changes reflect the ongoing evolution of Agile frameworks and the commitment to continuously improve and adapt to the changing needs of organizations.

Key Highlights of SAFe 6.0

• SAFe 6.0 focuses on enhancing business agility, enabling organizations to quickly respond to market changes and emerging opportunities.
• The new version introduces flow accelerators, which are specific practices and techniques to eliminate impediments to the flow of value.
• SAFe 6.0 emphasizes the importance of lean portfolio management, guiding aligning strategy, prioritizing investments, and optimizing the flow of value.
• The framework introduces the Business Agility Value Stream (BAVS), a way to map the steps from identifying an opportunity to delivering value to the customer.
• SAFe 6.0 keeps the focus on flow, including the eight flow accelerators.

How the 2023 Release Maps to the Five Disciplines

The seven core competencies described in this post belong to the 2023 Big Picture. The framework site now organises SAFe into five Disciplines instead. Two names carry over unchanged (Lean Portfolio Management, and Team and Technical Agility); the others were regrouped, and the pages we checked do not publish a one-to-one map from the old seven to the new five. The table lists each Discipline with the competencies the framework site shows for it. Scaled Agile releases competencies in small batches, so a Discipline page can list more than the ones already published in full.

Core Values Transformation in SAFe 6.0

SAFe 6.0 brings a transformation in core values, emphasizing the importance of a culture of continuous improvement at the enterprise level. SAFe has four core values: Alignment, Transparency, Respect for People, and Relentless Improvement. These new core values reflect the need for alignment and collaboration across the organization, as well as the importance of continuous improvement in driving better outcomes. By embracing these core values, organizations can foster a culture of learning, innovation, and collaboration, which are crucial for success in a scaled Agile environment.

What’s New in the Core Values?

The core values in SAFe 6.0 are Alignment, Transparency, Respect for People and Relentless Improvement. The framework site describes them as the foundational beliefs behind SAFe’s effectiveness, guiding the behavior of everyone in a SAFe portfolio.
The framework site says leaders encourage the values by modelling them in their words and actions, and that SAFe practices are unlikely to deliver their intended business results without these beliefs behind them. Scaled Agile publishes the full description of each value only to members, so this post lists the four by name and does not paraphrase beyond that.

The Ten Lean-Agile Principles

The core values are separate from the ten SAFe Lean-Agile principles, which the framework site calls the foundation for its roles and practices. In short:

• Take an economic view: weigh risk, Cost of Delay and development, operating and other costs within an approved budget.
• Apply systems thinking: optimising one part does not optimise the whole, for the product or for the organization building it.
• Assume variability; preserve options: keep several requirement and design options open longer and narrow them with data.
• Build incrementally with fast, integrated learning cycles: short iterations give early customer feedback and show when to pivot.
• Base milestones on objective evaluation of working systems: use integration points to judge working solutions.
• Make value flow without interruptions: understand the properties of flow systems and remove what slows delivery.
• Apply cadence, synchronize with cross-domain planning: regular rhythms add predictability.
• Unlock the intrinsic motivation of knowledge workers: autonomy, purpose and few constraints engage people better than individual incentives that breed competition.
• Decentralize decision-making: push decisions to the people closest to the work, and keep strategic decisions central.
• Organize around value: structure around value streams, not functional silos, to reduce handoffs and delays.

These ten are the practical reason the rest of the release hangs together: value streams, cadence, working-system milestones and decentralised decisions show up again in the roles, events and roadmap below.

Enhancements in Quality and Flow

SAFe 6.0 introduces enhancements in quality and flow. The importance of quality is embedded as a dimension of the Team and Technical Agility core competency. SAFe 6.0 emphasizes the need for a culture of continuous improvement and building quality in every step of the development process. The flow of value is also a key focus in SAFe 6.0, through the eight flow accelerators, which are practices for removing impediments to flow.

Building Quality into Every Step

Building quality into every step of the development process is a key focus of SAFe 6.0. SAFe 6.0 emphasizes the importance of continuous integration and a continuous delivery pipeline. Continuous integration enables teams to integrate their work frequently, reducing the risk of integration issues and ensuring that the software is always in a releasable state. A continuous delivery pipeline provides an automated and streamlined process for delivering software to production. By building quality into every step, teams can ensure that the software is tested, validated, and ready for deployment at any point in time.

What Built-in Quality Means in Practice

The Team and Technical Agility Discipline describes built-in quality as quality designed into everything teams deliver rather than checked only before release. Practices that add quality during development reduce the effort and cost of fixing issues later. The page also stresses that the standard depends on context: a multiplayer game and a medical device have different requirements, so the right level of rigour differs. For high-stakes systems, teams balance working software against rigorous validation, and traceability links solution intent to components but should not add overhead in a DevOps setting. It is a long-term commitment that needs ongoing training, not a one-off activity.

Facilitating Flow in Value Delivery

SAFe 6.0 introduces value stream management and flow accelerators to facilitate the flow of value in organizations. Value stream management focuses on improving the flow of work across the entire value stream, from idea to delivery. It enables organizations to identify bottlenecks and remove impediments to flow. The eight flow accelerators are practices for speeding up the flow of value; Scaled Agile publishes them under the principle “Make value flow without interruptions”.

Measuring Flow with Measure and Grow

Measure and Grow is the framework’s approach for judging progress toward business agility and deciding what to improve. It rests on three measurement domains that apply at every level, from a portfolio down to a single Agile Team:

• Outcomes: do solutions meet the needs of customers and the business? KPIs, OKRs and employee engagement metrics belong here.
• Flow: how efficiently does the organization deliver value? The six flow metrics are flow distribution, velocity, time, load, efficiency and predictability.
• Competency: how proficient is the organization in the practices that enable agility? Assessments measure proficiency in the Disciplines.

The guidance adds a few cautions that experienced teams will recognise: use metrics together with other discovery methods, concentrate on metrics that drive decisions, think about how a metric will change behaviour, and interpret the numbers carefully. A worked example of the mechanism: if flow time is long but flow load is high, the usual first move is to limit work in process on the bottleneck before asking anyone to work faster. The Team and Technical Agility page says teams use the flow metrics to find inefficiencies and apply flow accelerators.

OKRs in SAFe

Objectives and Key Results are a collaborative way to set clear goals and measurable outcomes. In SAFe they support transparency and alignment between enterprise and portfolio strategy and the work of ARTs and teams, and they can also track the progress of a SAFe transformation. The Objective states the business outcome, and the Key Results are the measurable success criteria, typically two to five per Objective. Using OKRs is optional, except that SAFe strongly recommends them for describing portfolio Strategic Themes. They work best when planning and delivery are incremental, so an organization that commits to large upfront batches of work will struggle to benefit.

Roles and Events on an ART Today

The 2023 release changed how some roles and events are described, and the framework site continues to evolve. This is how the Team and Technical Agility Discipline lists them now.

Roles

• Scrum Master/Team Coach (SM/TC): a servant leader and coach who removes impediments, facilitates team events and builds an environment for high performance. The site expects SM/TCs to know several practice methods so each team can find the right blend.
• Product Owner (PO): the content authority for the team backlog, who defines stories and prioritises the backlog.
• Product Management: defines and supports products that are desirable, feasible, viable and sustainable.
• System Architect: defines the overall architecture, identifies non-functional requirements and shapes subsystems and interfaces.
• Release Train Engineer (RTE): servant leader and chief Scrum Master/Team Coach for the train, who keeps ART events and artifacts working well. See the RTE course.
• Business Owners: stakeholders responsible for fitness for use, governance and return on investment.

Events

• PI Planning: opens each Planning Interval. The whole ART, led by the RTE, aligns on a shared mission and the teams commit to PI Objectives. It is typically a two-day event held every 8 to 12 weeks, in the Innovation and Planning iteration so delivery is not interrupted, and it produces the PI Objectives and an ART planning board showing feature dates and dependencies. Remote planning works if every ART member takes part.
• System Demo: an integrated view of each iteration’s new features. The framework site still uses this name; for large solutions it also mentions solution demos on the shared cadence.
• Inspect and Adapt: the end-of-PI problem-solving workshop to evaluate the solution and improve processes.
• ART Sync, Coach Sync and PO Sync: recurring coordination events. Coach Sync is the coaches’ meeting.
• Innovation and Planning (IP) iteration: time for exploration, innovation, planning and learning.
• Team retrospectives and SAFe Scrum or SAFe Team Kanban: teams pick Scrum, Kanban or a hybrid to set their cadence; Kanban suits unpredictable workloads.

SAFe 6.0 and Business Agility

SAFe 6.0 emphasizes business agility and the ability of organizations to quickly adapt to changing market conditions. The introduction of the Business Agility Value Stream (BAVS) highlights the importance of aligning business outcomes with Agile practices. By embracing SAFe 6.0 and focusing on business agility, organizations can respond more effectively to market changes, and deliver better business outcomes.

The Business Agility Value Stream (BAVS) Explained

The Business Agility Value Stream (BAVS) is a key concept introduced in SAFe 6.0. It focuses on aligning business outcomes with Agile practices and enables organizations to quickly respond to market changes and emerging opportunities. The BAVS encompasses the entire value stream, from idea to delivery, and emphasizes the need for cross-functional collaboration and value delivery. The introduction of the Value Management Office (VMO) in SAFe 6.0 further supports the BAVS by guiding for managing multiple value streams and ensuring the flow of value across the portfolio.

SAFe as a Second Operating System

The framework site frames business agility as the ability to compete and thrive in the digital age by responding quickly to market change. It notes that hierarchies grow up for efficiency and eventually collide with the fast, customer-focused networks that started the business. Its answer, following John Kotter, is not to discard the hierarchy. SAFe adds a second, virtual operating system organised around development value streams instead of functional departments. Each value stream creates one or more Agile Release Trains, which are teams that plan, build and deploy together. The full BAVS steps sit behind a Scaled Agile login, so this post stays with that overview.

Lean Portfolio Management and the Value Management Office

The Lean Portfolio Management Discipline is where strategy meets funding. As the framework site describes it:

• Value streams receive the portfolio budget directly rather than through project-based funding. These lean budgets follow strategy and current strategic themes, and guardrails supply the governance and spending policies that keep financial oversight in place.
• Strategic initiatives are epics, moved through a portfolio Kanban system by Epic Owners. The Lean Startup cycle tests a minimum viable product before full investment.
• The Value Management Office (VMO) is accountable for portfolio governance and day-to-day operations, and provides reporting and current insight to Portfolio Leadership.
• Investment horizons group solutions by stage. A value stream that spends only on its current-horizon solution may underinvest in future innovation.
• Progress is reviewed at least quarterly with financial data. The site prefers leading indicators over lagging ones such as profit and loss and ROI, which often arrive too late.
• The operating rhythm includes a Strategic Portfolio Review each quarter, at least a month before PI Planning, and a Portfolio Sync, usually monthly, covering epic progress, KPIs, dependencies and impediments.

The course that covers this ground is Lean Portfolio Management. In 2023 terms the shift was from functional silos and project funding to value streams and ARTs; from annual top-down budgets to budgets adjusted dynamically; from central intake to Kanban-managed demand; and from phase gates to milestones based on working solutions.

Accelerating Value Flow with Eight Flow Accelerators

Scaled Agile describes eight flow accelerators, which are practices for removing impediments to flow and enabling faster value delivery. It also notes that all flow systems share eight common properties. By embracing these properties, organizations can increase the speed and efficiency of their value delivery processes. The properties of flow focus on optimizing the value stream, removing bottlenecks, and improving collaboration and communication.

Implementing SAFe 6.0: A Roadmap

Implementing SAFe 6.0 requires a well-defined roadmap and a structured approach. The SAFe Implementation Roadmap provides organizations with a step-by-step guide to transitioning to SAFe 6.0. It covers key activities, milestones, and success factors that organizations need to consider during their transformation journey. The implementation roadmap helps organizations plan and execute their transition to SAFe 6.0 in a systematic and organized manner. By following the roadmap, organizations can ensure a successful implementation of SAFe 6.0.

Step-by-Step Guide to Transition

The step-by-step guide to transitioning to SAFe 6.0 provides organizations with a structured approach to implementing the framework. The SAFe Implementation Roadmap outlines key activities and milestones that organizations need to consider during their transition journey. These activities include establishing a guiding coalition, and forming Agile Release Trains (ARTs). The implementation roadmap also highlights the importance of continuous learning and improvement throughout the transition process. By following the step-by-step guide, organizations can navigate the complexities of implementing SAFe 6.0 and ensure a successful transition to the new framework.

The 13 Steps of the Implementation Roadmap

Scaled Agile says organizations rarely follow the steps in strict order, but the best results follow a path like this one. The roadmap draws on John Kotter’s change work and weaves his eight accelerators through the steps.

• 1. Reaching the Tipping Point: build a shared case for change and a vision, tie it to expected business benefits with baseline and target metrics, and send senior leaders to Leading SAFe.
• 2. Train Lean-Agile Change Agents: build a guiding coalition of SAFe Practice Consultants through the four-day Implementing SAFe course, pairing internal staff with experienced coaches.
• 3. Create a Lean-Agile Center of Excellence (LACE): a small dedicated team that drives the transformation, keeps a transformation backlog, baselines agility and tracks transformation OKRs.
• 4. Train Executives, Managers, and Leaders: so they sponsor the change, model the mindset and apply the ten principles.
• 5. Lead in the Digital Age: leaders who learned the framework now lead the change visibly.
• 6. Organize Around Value: set up value streams and ARTs as the backbone of the transformation.
• 7. Create the Implementation Plan: plan a little, execute and learn; usually start with one value stream and one ART, with a preliminary plan for the rest.
• 8. Prepare for ART Launch: define the ART, its launch date and cadence calendar; train ART leaders and stakeholders; form teams; prepare the backlog.
• 9. Train Teams and Launch the ART: train all teams at once in the two-day SAFe for Teams course, then run the first PI Planning.
• 10. Coach ART Execution: coaching by SPCs and Lean-Agile leaders after the first PI Planning. Knowledge does not equal understanding, so expect it to take several PIs.
• 11. Launch More ARTs and Value Streams: repeat the prepare, train and launch, coach cycle, and assess whether a value stream needs large-solution roles and events.
• 12. Enhance the Portfolio: make strategic initiatives visible, match demand to value stream capacity, and apply Lean thinking to funding and governance.
• 13. Accelerate: for organizations already on SAFe; refocus on value streams, measure flow, strengthen Kanban systems and extend agility to other portfolios and business areas.

The roadmap page was updated for the AI-Empowered course material in February 2026, so the course names in steps 2, 4 and 9 follow today’s catalogue.

How to Apply the 2023 Release Ideas

• Pick one value stream and one ART first, as step 7 advises, rather than planning every train up front.
• Set transformation OKRs for the LACE and use the Measure and Grow domains (outcomes, flow, competency) to baseline before you change anything.
• Map a value stream and read the six flow metrics for it. Start where flow time and load show the biggest wait.
• Write portfolio Strategic Themes as OKRs, then connect each epic to a theme through the portfolio Kanban.
• Move one value stream to a lean budget with guardrails as a pilot instead of changing all funding at once.
• Run PI Planning on a fixed cadence and use Inspect and Adapt to feed the next transformation backlog.

Overcoming Common Implementation Challenges

Implementing SAFe 6.0 can come with its own set of challenges. Some common implementation challenges include resistance to change, lack of alignment, and difficulties in adopting new practices such as continuous delivery. To overcome these challenges, organizations need to foster a culture of continuous improvement and learning. This involves providing training and support to teams, encouraging open communication and collaboration, and creating an environment that promotes experimentation and innovation. By embracing a mindset of relentless improvement, organizations can overcome implementation challenges.

Conclusion

SAFe 6.0 marks a significant shift in the world of Scaled Agile Frameworks, emphasizing Core Values, Quality and Flow. These changes are geared towards enhancing business agility and fostering a culture of continuous improvement. By implementing SAFe 6.0, organizations can streamline value delivery, improve collaboration, and navigate the evolving landscape of agile methodologies effectively.

Frequently Asked Questions

What Are the Benefits of Upgrading to SAFe 6.0?

The benefits depend on how an organization applies the framework. Scaled Agile has since dropped version numbers from its courses and certifications, so see the Updated October 2026 box at the top of this post for the current picture.

How Does SAFe 6.0 Differ from Previous Versions?

SAFe 6.0 introduces significant changes compared to previous versions. It includes updates in the Big Picture and enhancements in portfolio management.

Can I still take a SAFe 6.0 course?

No. Scaled Agile has dropped version numbers from its courses and certifications. The entry-level class is Leading SAFe, which leads to the AI-Empowered SAFe Agilist (SA) certification: 45 questions, 90 minutes, 80% to pass, with the first exam attempt included in AgileFever’s course fee if taken within 30 days of completing the course. See the course page for dates and fees. Additional discounts are available. Contact us to know more.

What replaced the seven core competencies?

Five Disciplines: Lean Portfolio Management, Team and Technical Agility, Product Development Flow, Large Solution Integration and Delivery, and Leadership and Culture. See the mapping section above.

Who should take Leading SAFe versus Implementing SAFe?

Leading SAFe (two days at AgileFever) suits leaders, managers and practitioners who need the framework and mindset. Implementing SAFe (four days) prepares change agents to launch ARTs and teach SAFe, which is steps 2 and 8 to 11 of the roadmap.