Move from single-team Scrum into the Scaled Agile Framework without losing what you already know. Learn how SAFe layers Program and Portfolio structures on top of team-level Scrum, and translate familiar terms like Sprint and Product Owner into ART, PI, Release Train Engineer and Product Management.
Watch the free preview
Why one Scrum team does not simply scale to a hundred people — free to watch, no account needed.
What you'll learn
- Explain why a single Scrum team does not scale to many teams by simple copy-paste
- Describe SAFe's configuration levels and how they layer on top of team-level Scrum
- Map core Scrum vocabulary onto its SAFe equivalents at the Program and Portfolio levels
- Distinguish the Agile Release Train, the Program Increment and the Release Train Engineer from their team-level roots
- Produce a Scrum-to-SAFe term mapping sheet you can use to onboard into a SAFe environment
Syllabus
Why Scaling Scrum Needs More Than Copy-Paste
Why one Scrum team does not simply scale to a hundred peopleFree preview
What SAFe actually is — levels and the same-principles idea
The New Structures — ART, PI and Roles
The Agile Release Train and the Program Increment
SAFe roles — RTE, Product Management and the team Product Owner
Applying SAFe in a Real IT Environment
PI Planning and the ART cadence in practice
Case study — a Scrum Master's first week in a SAFe ART
Making the Transition Stick
Building your Scrum-to-SAFe term mapping sheet
Common traps when moving from Scrum to SAFe