### 5.5.3 Guidelines and Participants | Key Participants | Description | |:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Team Coordinator (TeCo) | Supports/facilitates the Iteration Retrospective by selecting, preparing and facilitating all the required activities <br> to be used in each of the different steps of the meeting. | | Business Manager (BM) | Informed of the outputs of the retrospective if necessary. | | Agile Team Member (ATeM) | Responsible for the execution of all the activities foreseen in this ceremony, including collecting all the hard data, <br> understand it and define action plans.<br>Accountable for all the work items and activities that come as outputs of this ceremony. | | Product Owner (PrOw) | Informed of the outputs of the retrospective if necessary. | | Architecture Owner (ArOw) | Acts as an Agile Team Member (ATeM). | | Project Manager (PM) | Informed about the outputs of the ceremony. | **Guidelines** - **Have working agreements defined.** – Working agreements are very important in the day-to-day activities of the Agile Project Core Team (A-PCT), including the several different ceremonies. This is especially true for Iteration Retrospective. Because of its format and contents, these agreements become even more important as they contribute decisively to a smooth ceremony. - **Have a fully dedicated facilitator** – An Iteration Retrospective requires an active and focused presence of all Agile Team Members (ATeM). This is not compatible with the also active and fully dedicated presence of the facilitator. The Team Coordinator (TeCo) is the right facilitator. - **Send the agenda previously to everyone** – Although the agenda is explained in the first part of the Iteration Retrospective, sending it in advance (activities included) allows all Agile Team Members (ATeM) to understand how they are going to invest their time and to prepare specific materials when needed. - **Avoid the “no man’s-land” responsibility** –Agile teams tend to create action items which they believe they are not responsible for by putting them on someone else’s hands. - By doing this, they will no longer be able to control how they can improve, making the retrospective a very limited exercise in terms of its main goal: The improvement of the Agile Project Core Team (A-PCT). - **Record all the learnings, actions and people accountable** – One of the most relevant outcomes of each Retrospective is the increased knowledge that the Agile Project Core Team (A-PCT) gains. However, because memory cannot keep track of everything, the outputs must be recorded in a Retrospective Log (can be a document, a wiki, etc). This will be used as a reference in the next Iteration Retrospective but also by the end of the project, when it’s time to collect the Lessons Learned. Please refer to the section 7.3.2 Project Logs for more information on Project Logs. ![[5.5 RASCI Iteration Retrospective.png]]