Kaung Myat Tun

The iteration (or sprint) review is about showing what was delivered and getting feedback from customers and stakeholders.

The retrospective, on the other hand, is different in purpose and audience:

📌 Sprint Retrospective

• When: Held at the end of each iteration (usually right after the sprint review, before the next sprint planning).
• Participants: The development team, Scrum Master, and optionally the Product Owner — but not external stakeholders.
• Purpose: To reflect internally on how the team worked during the sprint, rather than what was delivered.
• Focus: Continuous improvement in processes, collaboration, tools, and team dynamics.

🔍 Key Differences

• Review = What was built → feedback from customers and stakeholders.
• Retrospective = How it was built → improvement for the team’s ways of working.

⚙️ Typical Retrospective Agenda

1. Set the stage – create an open and safe environment.
2. Gather data – look at what went well, what didn’t, and what puzzles remain.
3. Generate insights – analyze patterns, root causes, or blockers.
4. Decide on actions – pick specific improvements for the next sprint.
5. Close – appreciate contributions and align on next steps.

👉 So, you can think of it like this:

• Sprint Review: External focus — deliverables and product feedback.
• Sprint Retrospective: Internal focus — team process and collaboration.