The Coach Sync (formerly Scrum of Scrums) is an ART-level event facilitated by the Release Train Engineer (RTE). It ensures cross-team synchronization, makes dependencies visible, addresses impediments, and helps track progress against PI Objectives.
SAFe distinguishes two contexts:
During PI Planning (Day 1 and Day 2): The RTE facilitates the Coach Sync within the team breakouts. On Day 1, initial dependencies and risks are surfaced. On Day 2, these are refined, ROAM risks are addressed, and the ART Planning Board (formerly Program Board) is updated.
During PI Execution: The Coach Sync takes place on a regular cadence throughout the PI. SAFe does not prescribe a fixed frequency – in practice, it is often weekly or multiple times per week.
Practical Relevance
During PI Planning, the Coach Sync focuses on:
- Surfacing initial dependencies (Day 1),
- Refining and resolving risks (Day 1 and Day 2),
- Supporting Draft and Final Plan Reviews (Day 2).
During PI Execution, it focuses on:
- Ongoing monitoring of impediments and dependencies,
- Tracking progress toward PI Objectives,
- Coordinating with the PO Sync, together forming the ART Sync.
Relevance for Organizations
The Coach Sync provides a coordination layer between teams and program management. Without it, organizations risk:
- late detection of dependencies,
- siloed problem-solving,
- unnecessary escalations to management.
When well facilitated, the Coach Sync delivers:
- Transparency across teams,
- Faster impediment resolution,
- Shorter decision paths,
- Shared accountability within the ART.
Real-World Examples
Automotive (Driver Assistance Systems): An ART developed ADAS functions. In PI Planning, the Coach Sync exposed dependencies (e.g., sensor data, test environments) and supported risk handling with ROAM. During execution, delays in test environments were escalated, prioritized, and resolved by reallocating capacity. This kept the PI Objectives on track.
Telecommunications (Platform Modernization): A provider migrated on-premise systems to the cloud while building new self-service features. In planning, the Coach Sync aligned sequencing between migration tasks and feature delivery. During execution, it synchronized deployment windows and shared environments, reducing failed deployments and shortening release cycles.
Insurance (Digital Claims): Multiple teams had planned overlapping compliance work. In the Coach Sync during planning, this duplication was identified and consolidated into a single enabler item. During execution, the Coach Sync tracked regulatory deadlines and distributed compliance tasks across teams, ensuring timely delivery without duplication.
Practical Implementation
- Frequency: During PI Planning on both days within team breakouts; during execution on a regular cadence throughout the PI (commonly weekly or several times per week).
- Participants: Scrum Masters/Team Coaches, facilitated by the RTE; architects or QA may join if needed.
- Facilitation: A working meeting, not a status report. Decisions and actions are documented and followed up.
- Tools: ART Planning Board (formerly Program Board) and ROAM risks during planning; Kanban boards or ART Boards during execution.
CALADE Perspective
In many organizations, the Coach Sync degrades into a status-reporting session or is undervalued during PI Planning. At CALADE, we emphasize running it as an active working session focused on solving, not reporting. This makes the Coach Sync a true learning and steering instrument that drives ART performance.
Related Terms
- Release Train Engineer (RTE)
- PO Sync
- ART Sync
- ART Planning Board (formerly Program Board)
- ROAM risks
- Impediments
← back to list