According to the Agile Practice Guide and the PMBOK® Guide, the Retrospective is a critical ceremony held at the end of every iteration to ensure continuous improvement (Kaizen).
Purpose of the Retrospective: Unlike a project review or demo which focuses on the product (the " what " ), the Retrospective focuses on the process (the " how " ). The team reflects on their performance, communication, tools, and relationships during the iteration.
Continuous Improvement: The primary goal is to identify what went well, what didn ' t, and most importantly, to agree on specific actionable improvements to be implemented in the very next iteration. This allows the team to correct issues early rather than letting them persist throughout the project.
Timing: The Retrospective occurs after the Iteration Review (where the product is demonstrated) but before the Iteration Planning for the next cycle. This ensures that the lessons learned can be immediately applied to the upcoming work.
Analysis of other options:
Iteration planning (Option A): This meeting occurs at the beginning of an iteration to define what will be built and how it will be achieved.
Backlog refinement review (Option C): Also known as grooming, this is an ongoing process throughout the iteration (not necessarily just at the end) to prepare user stories for future sprints.
Daily standup (Option D): This is a short, daily meeting (typically 15 minutes) held during the iteration to synchronize activities and identify blockers. It is not an " end of iteration " meeting.
Per PMI standards, the Retrospective is the cornerstone of the " Inspect and Adapt " pillar of Agile, ensuring that the team ' s velocity and quality increase over time through self-correction and shared learning.
