SAFe 6.0 at a Glance: How the Scaled Agile Framework Works for Large Organizations

What is SAFe 6.0?

SAFe (Scaled Agile Framework) is a comprehensive set of principles, roles, and practices for implementing Agile at scale across an entire organization. Version 6.0, released in 2023, places new emphasis on flow and OKRs (Objectives and Key Results) alongside existing core structures. SAFe is organized across different levels (Team, Program, Large Solution, Portfolio) and provides a blueprint for how to coordinate multiple Agile teams with strategy, budgets, and governance.

‍

Key Concepts

1. Agile Release Train (ART): A team of teams (typically 50 to 125 people) that work together in sprints to deliver value. They are synchronized in terms of sprint planning and work towards a shared PI (Program Increment).
2. Program Increment (PI): A period of approximately 10 weeks (often 5 sprints + 2 days of planning) during which the ART pursues a set of objectives. At the beginning of each PI, there is a PI Planningevent where all teams plan together.
3. Team Level: Where Scrum or Kanban teams work with a Product Owner and Scrum Master.
4. Program Level: Where the ART, with Product Management, an RTE (Release Train Engineer), and System Architect, manages the planning and roadmap.
5. Portfolio Level: Epics and Value Streams are managed here, with Lean Portfolio Management and strategic goals.
6. Lean-Agile Principles: SAFe employs 10 principles rooted in Lean thinking, systems thinking, and agile decision-making.
7. Continuous Delivery Pipeline: SAFe's DevOps approach for continuously integrating software and rapidly deploying it to production.
8. LeSS: SAFe 6.0 (mistake: you should describe SAFe 6.0, not LeSS) Sorry, ignoring.

‍

What's New in SAFe 6.0?

SAFe 6.0 places additional emphasis on:

• Flow Accelerators: A method to identify and resolve bottlenecks in your value streams.
• OKRs (Objectives and Key Results): A way to set clear goals and make them measurable at each SAFe level.
• Sustainability and continuous learning: Supports an organizational culture of continuous improvement without creating burnout.

‍

How does it work?

1. Team Level: Scrum teams work in sprints (or Kanban), deliver increments, and have their own backlog.
2. Program Level: The ART (Agile Release Train) bundles multiple teams. The Release Train Engineer (RTE) facilitates and coaches. Product Management manages features on the Program Kanban.
3. Large Solution Level (optional): For very large products that require multiple ARTs. There is a Solution Train, Solution Architect, etc.
4. Portfolio Level: Strategic epics and investment budgets are managed here. Lean Portfolio Management is responsible.

‍

Agile Release Train (ART)

The heart of SAFe is the Agile Release Train. All teams work in ‘Program Increments’ (PI), usually 10 weeks long. In the PI Planning everyone comes together (physically or virtually) to define goals and features for this period. The teams then roll this out in their sprints, with Demos, Inspect and Adapt sessions, etc.

‍

When should you choose SAFe?

SAFe is useful for larger enterprises that:

• Have dozens or hundreds of people working on the same (or closely related) products.
• Need clear portfolio and program coordination.
• Are looking for a blueprint to roll out Agile across multiple departments, including governance, budget, and role assignments.

‍

Criticisms

Some find SAFe cumbersome or bureaucratic, especially if you only have a few teams. It also requires a thorough cultural change: you can't simply add a few meetings and be done with it. Its added value lies in consistency and alignment, but it takes effort to keep the overhead minimal.

‍

Pitfalls in SAFe Implementation

• Too much focus on ceremony: If you only perform the events without a Lean-Agile mindset, you fall into 'mechanical SAFe'.
• Lack of management buy-in: SAFe requires support and investment from above.
• Overcrowded PI Planning: Trying to plan too many details (instead of providing direction).
• Lack of DevOps: SAFe relies on a Continuous Delivery Pipeline; this requires technical and cultural shifts.

‍

SAFe 6.0 is a comprehensive framework for implementing Agile at scale, with clear structures for planning, prioritizing, and coordinating teams. It introduces an overarching Program Increment rhythm, additional roles (RTE, System Architect), and portfolio layers to link strategy and execution. The latest version (6.0) particularly emphasizes flow and OKRs, ensuring large organizations remain agile without descending into chaos. Do you have many teams, complex products, and a need for consistency? Then SAFe 6.0 can be the cornerstone for successful Agile scaling.

‍

SAFe 6.0 Roles and Responsibilities: who does what?

In a large-scale Agile environment (SAFe), you need more than just team-level functions like the Scrum Master and Product Owner. SAFe 6.0 introduces or formalizes various roles at different levels (Team, Program, Portfolio). Below is an overview of the key roles and their responsibilities.

‍

Team Level: familiar from Scrum, but slightly more formal

Scrum Master & Product Owner

• Scrum Master: Just like in a 'regular' Scrum team, the SM coaches the team in Agile principles and facilitates events (Daily, Retro, etc.). In SAFe, extra coordination is required, as the Scrum Master consults with the Release Train Engineer (RTE) about impediments that go beyond the team.
• Product Owner: Is responsible for the Team Backlog, refines user stories, and sets priorities for that specific team. In SAFe, POs often report to Product Management at the Program level. The PO is closer to the team, while Product Management is positioned slightly higher in the hierarchy.

‍

Development Team

• Works in sprints to deliver increments. In SAFe, Kanban is sometimes used, sometimes Scrum, but the approach remains “Agile”. The team communicates with the Product Owner and Scrum Master, and often also with technical advisors (such as the System Architect) for integration issues.

‍

Program Level: focus on one Agile Release Train (ART)

Product Management

• Program Backlog: Manages the ‘features’ on this backlog, defines the vision and roadmap for the entire ART.
• Collaboration with Product Owners: Consults with each team PO on how features are split into user stories.
• Vision and roadmap: Communicates the product vision and strategy to the teams and stakeholders.

‍

Release Train Engineer (RTE)

• The ‘chief Scrum Master’ of the Agile Release Train (ART). Facilitates and coaches multiple teams.
• Responsible for PI Planning: Organizes the Program Increment Planning (usually a two-day event every 10-12 weeks). Ensures that teams anticipate and resolve obstacles.
• Scrum of Scrums: Organizes the daily/weekly alignment between the teams' Scrum Masters.
• Impediment resolution: Handles impediments that are beyond the team level.

‍

System Architect/Engineer

• Technical vision: Defines the architecture and technical roadmaps at the program level.
• Coach for teams: Monitors consistency in the technical approach and assists teams with architectural decisions.
• Responsible for integration: Oversees cross-cutting concerns such as security, performance, and ops.

‍

Business Owners

• Key stakeholders who represent business or customer interests in the ART.
• During PI Planning: Determine and validate priorities. Assess the delivered value at the end of each PI.
• Monitoring business value: Ensure that the ART focuses on work that has the most impact.

‍

Portfolio level: strategic and organizational

Epic Owners

• Large Epics: Working on extensive initiatives that can impact multiple ARTs.
• From idea to implementation: They create business cases, validate hypotheses, and help teams realize the epic.
• Collaboration with LPM: Lean Portfolio Management reviews and funds these epics.

‍

Lean Portfolio Management (LPM)

• Strategy and funding: Responsible for budget allocation across Value Streams. They determine how resources are utilized.
• Value Stream coordination: Direct epics and larger initiatives to the appropriate ART(s).
• Governance: Ensure that strategy and actual progress remain aligned.

‍

Enterprise Architect

• Cross-ART alignment: Defines technology and infrastructure standards for the entire organization.
• Strategic: Works with System Architects at the program level to ensure consistent technical choices.

‍

Leadership and Culture: Lean-Agile Leaders

SAFe emphasizes that leaders at every level must embody and facilitate Lean-Agile principles. From team leads to C-level, all should embrace "servant leadership" and foster continuous improvement.

‍

Relationship and Interconnection between Roles

• From Team to Program: The Scrum Master and PO at the team level report back to the RTE and Product Management at the program level. This creates a vertical line of communication and prioritization.
• Program to Portfolio: The RTE, Product Management, and System Architect escalate larger epics or portfolio issues to the portfolio level. Epic Owners and LPM make decisions there.
• Overarching: All levels operate based on the same Lean-Agile principles, each with its own focus and scope.

SAFe 6.0 introduces a range of roles, each with its own focus and scope, from developing user stories (Team level) to defining strategic epics (Portfolio level). The goal is to enable large-scale Agile organizations to work consistently and adaptably, without teams getting in each other's way or losing sight of the strategic direction. Successful SAFe requires clarity on who does what: while we may already be familiar with Product Owners and Scrum Masters, new roles such as Release Train Engineer, Product Management, and Epic Owners deserve extra attention and clear integration into the organization.

‍