## 5.4 Iteration Review As described in the previous sections, each iteration kicks-off with an iteration goal defined by the Product Owner (PrOw). This triggers the rest of the Agile Project Core Team (A-PCT) to build a strategy they believe will help them reach the goal. Throughout the iteration, the team will implement this strategy by developing all the relevant items. Unfortunately, not everything is black or white, and misunderstandings are common in creative activities like software development. As such, it is imperative to continually assess the work developed by the Agile Team Members (ATeM) to ensure alignment with the Product Owner’s (PrOw) expectations. In this context, PM2- Agile recommends the use of the Iteration Review ceremony. The Iteration Review’s ==primary purpose is to assess if the iteration goal was achieved==, which can be done with a **practical demo** of what the Agile Team Members (ATeM) built. This allows the Product Owner (PrOw) and other stakeholders to provide feedback and helps the Agile Team Members (ATeM) understand if they are going in the right direction. Therefore, most of the time invested preparing the Iteration Review should focused on this demo. The following sections will detail how a typical Iteration Review meeting must be structured and how often should it happen. ### [[5.4.1 Frequency and Duration]] ### [[5.4.2 Structure of an Iteration Review]] ### [[5.4.3 Guidelines and Participants]]