An Iteration is a chunk of planned work time. SAFe® recommends Iterations are two weeks long. Iterations can also be referred to as Sprints. This article discusses the Agile team meetings held during each Iteration. For information on Agile Release Train (ART) meetings, see ART Events Overview.
Agile Team Meetings
Iteration Planning
During this event, held at the beginning of each Iteration, the Scrum Coach (SC) and Product Owner (PO) work with the team to revisit, refine, and commit to the Stories originally planned for that Iteration during PI Planning. Stories can be added, adjusted, or removed as needed. Team members should actively participate by contributing their knowledge and ideas to the planned stories.
Sync-ups or Check-ins
Throughout the two weeks of an iteration, the Scrum Coach (SC) runs quick daily team sync-ups. Each team member shares what they have just completed, what they're planning on working on next, and what, if anything, is blocking their progress.
Iteration Review
During this event, held at the end of each Iteration, the team shares and celebrates what they've accomplished with the Product Owner (PO), the Product Manager (PM) and key stakeholders. The Scrum Coach (SC) coordinates with the team ahead of time to arrange who will share during the review.
Iteration Retrospective
During this event, held after the Iteration Review the end of each Iteration, the Scrum Coach (SC) leads a team discussion on how the work went and how they can improve their work practices.