SAFe (Scaled Agile Framework) events are structured, time-boxed ceremonies designed to drive synchronization, alignment, and continuous improvement across different levels of an enterprise.

These events are primarily categorized into Team-level events (which mirror standard Scrum practices) and Agile Release Train (ART) level events (which orchestrate multiple teams working toward a shared goal).

The core events within Essential SAFe are broken down below by organizational layer.

👥 Agile Team-Level Events

These recurrent ceremonies occur inside a short timebox called an Iteration (typically lasting 2 weeks) and focus on local execution.

• Iteration Planning: Teams refine the iteration plan, select backlog stories, and commit to a set of Iteration Goals.
• Team Sync (Daily Stand-up): A brief, daily 15-minute meeting where team members align on progress, discuss daily goals, and highlight impediments.
• Iteration Review: A cadence-based showcase at the end of the iteration where teams demo working software to gather immediate feedback.
• Iteration Retrospective: Held at the end of each iteration to reflect on the process, team dynamics, and behaviors to drive relentless improvement.
• Backlog Refinement: A weekly meeting where the Product Owner and team flesh out, estimate, and prep user stories for upcoming iterations.

🚊 Agile Release Train (ART) Level Events

These higher-level events drive the Planning Interval (PI), an 8 to 12-week timebox where an entire “train” of 5–12 teams delivers cross-functional value.

• PI Planning: The multi-day flagship event of SAFe where all teams, stakeholders, and leaders align on a shared business vision, map dependencies, and commit to PI objectives.
• System Demo: A regular event occurring every iteration where the integrated functionality built by the entire ART is demonstrated to stakeholders for feedback.
• Coach Sync (formerly Scrum of Scrums): Facilitated by the Release Train Engineer (RTE), Scrum Masters meet to resolve cross-team dependencies, risks, and progress hurdles.
• PO Sync: Product Owners and Product Management meet to track milestone progress, manage scope adjustments, and ensure the train remains aligned with business goals.
• ART Sync: A combined session of Coach Sync and PO Sync used to streamline communication regarding execution and deployment.
• Inspect & Adapt (I&A): A major event held at the end of the PI consisting of a system demo, quantitative measurements, and a problem-solving workshop to implement systemic backlog improvements.

Summary of Differences

For a quick comparison, you can look at how responsibilities scale across the framework: