### 5.4.1 Frequency and Duration The Iteration Review is strongly related to the Iteration Planning meeting described in the previous sections, connecting the planning and the reviewing activities of an iteration cycle. At the end of the iteration, the Iteration Review meeting evaluates how successful the Agile Project Core Team (A-PCT) was in reaching the iteration goal. PM2-Agile recommends the Iteration Review as a closure ceremony meeting occurring on the last day of the iteration. Several factors can influence the duration of the meeting. For instance, a longer iteration means, in theory, the team will develop and deliver more work, implying a more extended demo. Furthermore, when more work is delivered, the likelihood of finding or discussing more issues will probably increase and with it, the time required to discuss them. So, although there is no established duration for the Iteration Review ceremony, the Agile Project Core Team (A-PCT) should strive for objectivity during the demo. Based on the field experience and assuming a 2-week iteration, PM2-Agile considers 90 to 120 minutes a good practice.