## 5.5 Iteration Retrospective The idea of retrospecting is not new in PM2. For instance, one of its key ceremonies - the Project-End Review meeting - aims to capture lessons learned and post-project recommendations to help teams benefiting from the experience acquired during the project. Moreover, PM2 points the need to capture these improvement opportunities throughout the project and not just at the end, where most of them may have already been forgotten. With PM2-Agile, there are two key elements that will take retrospection one step further. On one hand, the retrospective ceremony (Iteration Retrospective) happens frequently (by the end of each iteration), allowing a permanent and recurrent evaluation of the Agile Project Core Team’s (A-PCT) performance made by the team itself. On the other hand, the Agile Project Core Team (A-PCT) will not wait by the end of the project to make adjustments. As soon as possible, the improvement opportunities are integrated into the team’s work, allowing them to evolve and improve. The Iteration Retrospective is part of the Reviewing stage of the CIR rhythm that supports PM2-Agile and it acts has the closure of the cycle. By the end of the project, when it’s time to collect Lessons Learned, the repository where the Agile Project Core Team (A-PCT) keeps the logs of the Iteration retrospectives, is an invaluable source of information that will dramatically enrich the lessons learned and the post-project recommendations. It’s also important to mention that the Iteration Retrospective meeting is focused on real problems that affect a team. During this meeting, the Agile Project Core Team (A-PCT) finds solutions that can be implemented without having to wait for management’s approval. Since these improvements are chosen by the Agile Project Core Team (A-PCT) and not imposed, the Agile Team Members (ATeM) are even more committed to their success. There are several ways to organize and structure an Iteration Retrospective. PM2-Agile recommends a structure where its flexibility allows to easily adjust the duration and the activities used to reach the goal of each step of the meeting. The following sections provide more details on the expected duration and the different steps of the Iteration Retrospective. ### [[5.5.1 Frequency and Duration]] ### [[5.5.2 Structure of an Iteration Retrospective]] ### [[5.5.3 Guidelines and Participants]]