Why do teams have an Iteration retrospective?

The Iteration Retrospective is a regular event where Agile teams reflect on the completed iteration

to derive new ideas and identify ways to improve their process. This reflection is aligned with the

concept of relentless improvement, which is a core value of SAFe. The retrospective aims to uncover

what worked well, what did not, and what the team can do better in the next iteration1.

During the Iteration Retrospective, teams discuss the results of the iteration, review their practices,

and create improvement stories for the next iteration. Inputs to this event may include iteration

goals, the team’s increment, a list of improvement stories identified, and the actions taken since the

last retrospective, as well as a collection of agreed-to iteration metrics. The outputs of a successful

Iteration Retrospective include the creation of a few improvement stories and an updated Team

Backlog1.

The process involves the entire team, facilitated by the Scrum Master/Team Coach, who introduces

the goals, agenda, and format of the retrospective. The team then reviews and discusses the metrics

they have agreed upon and determines any actions to take. Team members may write their thoughts

on a flip chart or a digital tool designated for the retrospective. Popular formats for qualitative

feedback include individual note-taking, appreciation notes, conceptual words, rating scales, and

simple open discussions recorded under headings of what went well, what did not, and what to do

better next time