Scrum Master / Team Coach Roles SAFe 6.0

Side-by-side comparison of Agile Team — Iteration Level vs. Train (ART) — Program Increment (PI) Level responsibilities.

Exam-ready reference: ordered by stage, color-coded for quick scanning.
Stage Agile Team — Iteration Level Roles Train (ART) — PI Level Roles
Preparation

Backlog Refinement

  • Facilitate refinement with PO and team
  • Ensure Definition of Ready is met
  • Support estimation and identify dependencies
  • Coach clarity, slicing, and testability

Preparation for PI Planning

  • Refine team backlog for PI readiness
  • Ensure features/enablers are understood
  • Align on capacity, holidays, availability
  • Coordinate dependencies with other SMs
Planning

Iteration Planning

  • Facilitate planning and set iteration goals
  • Help craft realistic commitments
  • Surface risks, dependencies, and capacity limits
  • Align planned work to PI Objectives

PI Planning (Day 1 & 2)

  • Facilitate team breakouts
  • Define clear, testable PI Objectives
  • Support risk ROAMing
  • Collaborate in Scrum of Scrums; document dependencies
Daily Coordination

Daily Stand-ups

  • Facilitate or coach self-facilitation
  • Remove impediments quickly
  • Keep focus on collaboration (not status)
  • Adapt plan based on inspection

ART Sync (Scrum of Scrums & PO Sync)

  • Represent team; share progress and blockers
  • Coordinate cross-team impediments
  • Support PO in PO Sync to align priorities
  • Cascade ART updates back to the team
Execution

Iteration Execution

  • Shield the team from disruptions
  • Encourage collaboration and swarming
  • Reinforce technical practices and Definition of Done
  • Monitor WIP limits and flow
  • Coordinate dependencies with other teams

Iteration Execution within the PI

  • Guide delivery aligned to PI Objectives
  • Collaborate with the RTE on progress and risks
  • Promote consistent Agile practices across ART
  • Synchronize work for integrated delivery
  • Champion built-in quality and continuous delivery
Review

Iteration Review

  • Facilitate review or support the PO
  • Demonstrate only completed (Done) work
  • Capture stakeholder feedback and learnings
  • Emphasize delivered value

System Demos (each iteration)

  • Ensure the team integrates frequently
  • Coordinate integrated testing with other teams
  • Promote stakeholder participation
  • Capture feedback for subsequent iterations
Improvement

Iteration Retrospective

  • Facilitate a safe, constructive retro
  • Apply root-cause and problem-solving tools
  • Track actionable improvements
  • Ensure follow-through in the next iteration

Inspect & Adapt (end of PI)

  • Prepare for the PI System Demo
  • Review metrics and PI Objective completion
  • Join the Problem-Solving Workshop
  • Document systemic improvements in Program Backlog
  • Adopt at least one measurable improvement next PI
Cross-cutting responsibilities: Servant leadership, impediment removal, coaching & mentoring, collaboration within team and across the train, and modeling the Lean-Agile mindset.

Team Structure Comparison

Differences across Agile Team, Agile Release Train, and Solution Train.

Agile Team

Size
5–11 people (cross-functional)
Duration
Iteration cadence: 1–2 weeks
Roles
Product Owner, Scrum Master/Team Coach, Developers/Engineers/QA
Framework
Scrum/Kanban practices; Built-in Quality at team level
Requirements
User Stories, small Enablers; DoR/DoD
Events
Iteration Planning, Daily Scrum, Review, Retrospective

Agile Release Train (ART)

Size
~5–12 teams (≈50–125 people)
Duration
Program Increment (PI): 8–12 weeks
Roles
RTE, Product Management, System Architect/Engineering, Business Owners, POs & SMs
Framework
SAFe Program Level (synchronized teams on a common cadence)
Requirements
Features & Enablers (split into Stories across teams)
Events
PI Planning, ART Sync (SoS/PO Sync), System Demo, Inspect & Adapt

Solution Train

Size
Multiple ARTs (often hundreds) + suppliers
Duration
Aligns ART PIs (8–12 weeks); Pre-/Post-PI Planning
Roles
STE, Solution Management, Solution Architect/Engineering, RTEs, Product/System Mgmt
Framework
SAFe Solution Level (coordinates multiple ARTs and suppliers)
Requirements
Capabilities & Enablers, Solution Intent, Non-functional Requirements
Events
Pre-/Post-PI Planning, Solution Demo, Solution I&A

Agile Team — Iteration Level Events

Events, Facilitator, Attendants, and Timebox

Events Facilitator Attendants Timebox
Iteration Planning Scrum Master / Team Coach Entire Agile Team, Product Owner ~2–4 hrs (for 2-week iteration)
Daily Stand-up Scrum Master / Team (self-facilitated) Entire Agile Team 15 min
Backlog Refinement Product Owner (with SM) PO, Developers, SM ~1–2 hrs/week
Iteration Review PO & Scrum Master Team + Stakeholders ~1–2 hrs
Iteration Retrospective Scrum Master / Team Coach Entire Agile Team ~1–1.5 hrs

Program Increment (ART) — Events

Events, Facilitator, Attendants, and Recommended Timebox

Events Facilitator Attendants Recommended Timebox
PI Planning (Day 1–2) Release Train Engineer (RTE) All teams, POs/SMs, Product Mgmt, System Arch/Eng, Business Owners 2 full days
ART Sync (SoS & PO Sync) RTE (SoS), Product Mgmt (PO Sync) Scrum Masters, Product Owners, RTE, Product Mgmt 30–60 min; 2–3×/week
System Demo RTE (or delegate) ART teams, Stakeholders 60–120 min / iteration
Inspect & Adapt RTE ART teams, Business Owners, Product Mgmt 3–4 hrs (incl. Problem-Solving Workshop)
PI Readiness / Prep RTE + Product Mgmt POs/PMs, System Arch/Eng, SMs Short sessions as needed