What Are the SAFe Ceremonies/Events? Full List

SAFe's events include the standard team-level Scrum ceremonies (sprint planning, daily standup, sprint review, retrospective) plus a set of additional ART-level events specific to SAFe's coordinated, multi-team structure — most notably PI Planning, the System Demo, and the Inspect & Adapt workshop.

Quick facts

• Team-level events in SAFe are the same four standard Scrum ceremonies used in any Scrum team.
• ART-level events add coordination and alignment across all teams on the Agile Release Train.
• See related: What Is a Sprint Retrospective and How to Run One for the team-level version of one of these events.

The full list of SAFe events

Team-level events (standard Scrum)

These four events operate essentially the same as in any standard Scrum team, regardless of the broader SAFe context — sprint planning, daily standups, sprint reviews, and retrospectives all happen at the individual team level, following familiar Scrum practices.

PI Planning

The signature SAFe event: a large, structured gathering (often two full days) where all teams on an Agile Release Train come together to plan the upcoming Program Increment, surfacing cross-team dependencies and building a shared commitment to the ART's objectives for the next 8-12 weeks.

System Demo

Held at the end of each sprint (or more frequently), the System Demo brings together the integrated work of all teams on the ART, showing stakeholders how the pieces fit together as a working system — distinct from an individual team's sprint review, which shows only that team's specific work in isolation.

Inspect & Adapt (I&A)

Held at the end of each Program Increment, this ART-level event combines a system demo of the full PI's accumulated work, a quantitative and qualitative review of progress against PI objectives, and a structured, ART-wide retrospective and problem-solving workshop to identify and address larger, systemic improvement opportunities.

ART-level sync events

Beyond the major events above, SAFe also typically includes regular, lighter-weight sync events during the Program Increment — often structured as a "Scrum of Scrums" (Scrum Masters coordinating cross-team execution issues) and a "PO Sync" (Product Owners coordinating on content and priority alignment) — keeping cross-team coordination active throughout the PI, not just at the bookend planning and review events.

Common mistakes with SAFe events

• Treating PI Planning as sufficient coordination for the entire Program Increment, without the regular sync events needed to catch and address issues as they emerge mid-PI.
• Skipping or under-investing in the Inspect & Adapt workshop, missing the structured opportunity for ART-wide, systemic improvement.
• Confusing the System Demo with individual team sprint reviews, when they serve different purposes at different scopes.
• Not adapting the specific mix and cadence of events to the ART's actual size and complexity, applying a rigid template without genuine consideration of what coordination is actually needed.

FAQ

How long does PI Planning typically take? Most PI Planning events run two full days, though the exact duration can vary based on the ART's size and complexity.

Is the System Demo the same as a sprint review? No — a sprint review shows one team's specific work; the System Demo shows the integrated work of all teams on the ART together, demonstrating how the pieces function as a whole system.

How often does Inspect & Adapt happen? Typically once per Program Increment, at the end of each 8-12 week cycle, functioning as both a review and a structured, ART-wide retrospective.

Are all these events mandatory in every SAFe implementation? Most SAFe implementations use this core event structure, though organizations sometimes adapt the specific cadence or format to their particular context — the underlying principle of coordinated team and ART-level events generally remains consistent.