Introducing Scrum in SAFe®
Where SAFe Scrum sits
SAFe Scrum is the team-level agile delivery method that runs inside an Agile Release Train (ART). The train operates on cadence and synchronization: a Program Increment (PI) of roughly 8–12 weeks, composed of 2-week iterations plus a final Innovation and Planning (IP) iteration. Every team on the ART plans, integrates, and demos on the same rhythm, which is what separates SAFe Scrum from a standalone Scrum team.
Concepts a candidate must know
- The PI is the larger development timebox: it opens with PI Planning and closes with Inspect & Adapt (I&A).
- Roles coexist. Each team has a Product Owner (team content authority) and a Scrum Master (process and team health); the Product Manager holds ART-level content authority and the Release Train Engineer (RTE) runs the ART.
- Events. Iteration planning, daily stand-up, iteration review, and retrospective sit inside the PI, alongside PI Planning, the System Demo, ART Sync, and I&A.
- Built-in quality and transparency are first-class SAFe values; the Scrum Master is the guardian of team-level transparency.
Traps that show up in questions
- Treating the System Demo as a once-per-PI event - it happens every iteration, with I&A closing the PI.
- Claiming SAFe Scrum drops the Product Owner or the retrospective. It has both.
- Assuming iteration length is negotiable per team; the cadence is fixed within the PI.
- Confusing who owns what: content belongs to the PO/PM, process to the Scrum Master, program flow to the RTE.
Rule of thumb
When asked "who is accountable?" classify the item: content → Product Owner/Product Manager; process and team health → Scrum Master; program flow and ART events → RTE.