Module 4: Roles and Responsibilities in SAFe

4.1 Who Does What? Navigating the SAFe Organization

Welcome to Module 4. Now that you understand the core principles of SAFe and the structure of the Agile Release Train (ART), it’s time to meet the people who make it all work. One of the most common sources of confusion when scaling Agile is understanding who is responsible for what. SAFe addresses this challenge by providing a clear, well-defined set of roles and responsibilities that span from the individual Agile team all the way up to the enterprise portfolio.

Think of it as moving from a small boat (a single Scrum team) to a large naval fleet (an ART). On the small boat, roles are few and well-understood. But in a fleet, you need captains, navigators, engineers, and an admiral to coordinate the movement of all the ships. SAFe provides this organizational structure, ensuring that every function, from daily execution to long-term strategy, has a clear owner.

This module will provide a detailed breakdown of these roles, clarifying their duties and how they interact. Understanding these roles is critical for you as a Business Analyst or Project Manager, as you will collaborate with every one of them.

4.2 The Foundation: Team Level Roles

The Team Level is the bedrock of SAFe, where value is directly created. The roles at this level will be the most familiar to you, as they are scaled up from Scrum. The Agile Team: This is the fundamental unit of execution in SAFe. An Agile Team is a cross-functional, self-organizing group of 5-11 individuals who have all the skills necessary to define, build, test, and deliver an increment of value in a short iteration. The team as a whole is responsible for the quality and delivery of the work.

• Product Owner (PO): The Product Owner is the content authority for the Agile Team. They are responsible for the Team Backlog, which consists of User Stories. Their primary duties include defining and prioritizing stories, ensuring the team understands the requirements, and accepting completed stories into the baseline. The PO acts as the customer proxy for the team, ensuring that the team delivers the maximum possible value.
• Scrum Master / Team Coach: This role is the servant leader and coach for the Agile Team. In SAFe 6.0, the title was updated to “Scrum Master / Team Coach” to emphasize their responsibility beyond just facilitating Scrum events. They are responsible for ensuring the team follows its chosen Agile process, removing impediments, and fostering an environment of continuous improvement and high performance.

4.3 The Conductors: Program Level (ART) Roles

The Program Level is where SAFe truly begins to scale. These roles are responsible for coordinating the “team of teams” and ensuring the Agile Release Train (ART) runs smoothly.

• Release Train Engineer (RTE): The RTE is the servant leader and chief Scrum Master for the entire Agile Release Train. This is a critical leadership role focused on facilitating ART events and processes, such as PI Planning, the System Demo, and the Inspect & Adapt workshop. The RTE escalates impediments, manages risk, helps manage dependencies between teams, and drives relentless improvement at the program level. They are the ultimate owner of the ART’s process.
• Product Management: While the Product Owner focuses on the team’s backlog of stories, Product Management is responsible for the ART’s backlog of Features. They are the content authority for the ART, defining the vision and roadmap, understanding customer needs, and prioritizing features to ensure the train is building the right solution to meet business objectives. There is a critical partnership between Product Management and the Product Owners to ensure alignment from features down to stories.
• System Architect/Engineering: This role provides the technical vision and leadership for the ART. They are responsible for defining the overall architecture of the system, identifying non-functional requirements, and ensuring the system is robust and scalable. They collaborate with the Agile Teams to define the “architectural runway” — the necessary technical foundation to support upcoming features.
• Business Owners: These are the key stakeholders who have the ultimate business and technical responsibility for the value delivered by the ART. Typically a group of 3-5 individuals, they are active participants in ART events, helping to align the train with business outcomes and approve PI Objectives.

4.4 The Strategists: Portfolio Level Roles

The Portfolio Level connects the organization’s strategy to its execution. The roles at this level ensure that the ARTs are working on the initiatives that provide the most value to the enterprise.

• Lean Portfolio Management (LPM): This is typically a function or team, rather than a single individual. LPM has the highest level of decision-making and financial accountability for a SAFe portfolio. Their responsibilities include managing investment funding for value streams, applying lean governance, and aligning portfolio execution with the overall enterprise strategy.
• Epic Owners: Epic Owners are responsible for championing large-scale initiatives, known as Epics, through the Portfolio Kanban system. ⁵ They collaboratively define the epic, articulate its business case and benefits, and facilitate its implementation once approved.
• Enterprise Architect: The Enterprise Architect works at the portfolio level to provide strategic technical direction. They drive architectural initiatives for the portfolio, ensuring that the technology strategy enables current and future business capabilities across all value streams.

4.5 Visual Aid: Role & Responsibility Matrix

To help clarify these roles, the following matrix provides a high-level summary of their primary responsibilities across the different levels of SAFe.

Level	Role	Primary Responsibilities
Team	Agile Team	Defines, builds, tests, and delivers value in short iterations. Responsible for the quality of their work.
	Product Owner (PO)	Owns and prioritizes the Team Backlog (Stories). Acts as the customer proxy for the team and accepts completed work.
	Scrum Master / Team Coach	Servant leader who coaches the team, facilitates events, removes impediments, and fosters continuous improvement.
Program (ART)	Release Train Engineer (RTE)	The chief servant leader for the ART. Facilitates ART events, manages dependencies and risks, and optimizes the flow of value.
	Product Management	Owns and prioritizes the ART Backlog (Features). Defines the product vision and roadmap for the ART.
	System Architect/Engineering	Provides the technical and architectural vision for the solution being built by the ART.
	Business Owners	Key stakeholders responsible for the business outcomes of the ART. Participate in planning and approve PI Objectives.
Portfolio	Lean Portfolio Management (LPM)	Governs portfolio strategy and investment funding. Manages portfolio operations and aligns execution to enterprise strategy.
	Epic Owner	Champions Epics from identification through the Portfolio Kanban system to implementation.
	Enterprise Architect	Drives the overall technology strategy and architectural initiatives for the entire portfolio.