The event where all team members determine how much of the team’s backlog they can commit to delivering during an upcoming Iteration is known as Iteration Planning. This is a core event in the Scaled Agile Framework (SAFe) where teams select stories from the Team Backlog and commit to executing a set of them in the upcoming Iteration. The purpose of Iteration Planning is to organize the work and define a realistic scope for the Iteration, ensuring that the team’s capacity and the complexity, size, and dependencies of each story are considered1.

During Iteration Planning, the following activities take place:

The Product Owner (PO) typically starts the event by presenting high-priority stories from the Team Backlog and any preliminary Iteration Goals.

The team then collaborates to define, organize, and commit to the work for the next Iteration, summarizing this work as a set of committed Iteration Goals.

The Iteration Planning meeting is timeboxed to ensure focus and efficiency, and it results in a clear commitment from the team to the Iteration Goals1.

This event is distinct from Backlog Refinement, Solution Planning, and Solution Demo, which serve different purposes within the SAFe framework. Iteration Planning is specifically about the commitment to the Iteration’s delivery and is the first event of the Iteration1.