GuideRolesEventsWorkflow

SAFe Events

Iteration Events

Iteration events are the team-level ceremonies within each 2-week iteration: Iteration Planning, Daily Stand-up, Iteration Review, and Iteration Retrospective. These mirror Scrum events but operate within the ART’s PI cadence.

Team-level ceremonies · Timebox: Varies (see details)

Overview

Iteration events are the team-level ceremonies within each 2-week iteration: Iteration Planning, Daily Stand-up, Iteration Review, and Iteration Retrospective. These mirror Scrum events but operate within the ART’s PI cadence.

Event Ownership

Owned / Facilitated By
Scrum Master / Team Coach (facilitator) / Product Owner (content)
SM/TC facilitates all iteration events and guards timeboxes
PO drives content in Iteration Planning and Iteration Review
SM/TC coaches the team toward self-management of these events
PO ensures stories are refined and acceptance criteria are clear before planning

Who Should Be Present

Iteration Planning (≤4 hrs)
Entire Agile Team. PO presents stories, team decomposes into tasks, team commits to iteration goal. Align with PI Objectives.
Daily Stand-up (15 min)
Agile Team (Developers). Inspect progress toward iteration goal, surface blockers, create plan for next 24 hours.
Iteration Review (≤1 hr)
Agile Team + stakeholders. Demo working increment, gather feedback, PO accepts/rejects stories against acceptance criteria.
Iteration Retrospective (≤1 hr)
Entire Agile Team. Inspect how the iteration went, identify improvements, commit to 1–2 actions for next iteration.

Preparation Checklist

01PO: Stories refined with acceptance criteria, iteration goal drafted aligned to PI Objectives
02SM/TC: Facilitation format selected, prior retrospective actions reviewed
03Team: Prior iteration’s work completed or carried over transparently
04SM/TC: Impediment log updated, flow metrics available for the team

Facilitation Techniques

Click any technique to expand details and learn when to apply it.

PI Objective Alignment Check

Start Iteration Planning by referencing the team’s PI Objectives. Ask: ‘Which PI Objectives does this iteration advance?’ This keeps iteration work connected to the bigger picture.

Click to expand

Walk the Board for Stand-ups

Instead of round-robin updates, walk the team board from right to left. Focus on finishing work before starting new work. Ask: ‘What needs to happen to get this to Done?’

Click to expand

Vary Retrospective Formats

Rotate formats: Start/Stop/Continue, 4Ls, Sailboat, Timeline, 1-2-4-All, Silent Retro. Same format every iteration produces diminishing returns.

Click to expand

Improvement Item as Iteration Story

The top retrospective improvement should become a story in the next iteration’s backlog. If improvements don’t compete for capacity, they don’t get done.

Click to expand

Tips & Tricks

01
Team Ownership
Iteration events should feel like the team’s own rhythm, not imposed ceremonies
02
PI Connection
Connect every iteration to the PI — if the team can’t explain how their iteration advances PI Objectives, alignment has drifted
03
PO Presence
The PO must be present and available during planning, not just at the beginning
04
Team-Owned Stand-ups
Daily Stand-ups are for the team, not for management. If managers attend, they observe only
05
Vary Retro Formats
Vary retrospective formats every 2–3 iterations to keep them fresh and surface different insights

Anti-Patterns to Avoid

Backlog Refinement Sessions: Schedule 1–2 refinement sessions per iteration (not a formal SAFe event, but critical). Spend ~10% of iteration capacity refining upcoming stories so Iteration Planning runs smoothly.
System Demo Preparation: Teams should integrate and prepare their portion of the System Demo during the iteration, not scramble at the end. Build demo readiness into the team’s Definition of Done.
Iteration Metrics Visibility: Make iteration-level metrics visible to the team: velocity, stories completed vs. committed, escaped defects. Data grounds retrospective conversations in reality.

Success Takeaways by Role

What each participant should walk away with when this event is run well.

Team

Clear iteration plan owned by the team; daily alignment; stakeholder validation; concrete improvement actions

PO

Confidence in team’s understanding of stories; validated delivery against acceptance criteria; input for backlog reordering

SM/TC

Pulse on team health and morale; impediments to act on; improvement items to track; coaching opportunities identified

Cross-Framework Definition
See Sprint Planning in the glossary
→