		<div class="wpcnt">
			<div class="wpa">
				<span class="wpa-about">Advertisements</span>
				<div class="u top_amp">
							<amp-ad width="300" height="265"
		 type="pubmine"
		 data-siteid="9896746"
		 data-section="1">
		</amp-ad>
				</div>
			</div>
		</div><div class="cs-rating pd-rating" id="pd_rating_holder_594384_post_3037"></div>
<script type="text/javascript" charset="UTF-8"><!--//--><![CDATA[//><!--
PDRTJS_settings_594384_post_3037={"id":594384,"unique_id":"wp-post-3037","title":"Iteration%2FSprit%20Review%20vs%20Retrospective","permalink":"https:\/\/kaungmyattun.com\/2025\/08\/31\/iteration-sprit-review-vs-retrospective\/","item_id":"_post_3037"};
//--><!]]></script>
<script type="text/javascript" charset="UTF-8" src="https://polldaddy.com/js/rating/rating.js"></script>

<p class="wp-block-paragraph">The <strong>iteration (or sprint) review</strong> is about <em>showing</em> what was delivered and getting feedback from customers and stakeholders.</p>



<p class="wp-block-paragraph">The <strong>retrospective</strong>, on the other hand, is different in purpose and audience:</p>



<h3 class="wp-block-heading">ð Sprint Retrospective</h3>



<ul class="wp-block-list">
<li><strong>When</strong>: Held at the end of each iteration (usually right after the sprint review, before the next sprint planning).</li>



<li><strong>Participants</strong>: The development team, Scrum Master, and optionally the Product Owner — but <strong>not external stakeholders</strong>.</li>



<li><strong>Purpose</strong>: To reflect internally on <em>how</em> the team worked during the sprint, rather than <em>what</em> was delivered.</li>



<li><strong>Focus</strong>: Continuous improvement in processes, collaboration, tools, and team dynamics.</li>
</ul>



<h3 class="wp-block-heading">ð Key Differences</h3>



<ul class="wp-block-list">
<li><strong>Review</strong> = <em>What</em> was built → feedback from customers and stakeholders.</li>



<li><strong>Retrospective</strong> = <em>How</em> it was built → improvement for the team’s ways of working.</li>
</ul>



<h3 class="wp-block-heading">âï¸ Typical Retrospective Agenda</h3>



<ol class="wp-block-list">
<li><strong>Set the stage</strong> – create an open and safe environment.</li>



<li><strong>Gather data</strong> – look at what went well, what didn’t, and what puzzles remain.</li>



<li><strong>Generate insights</strong> – analyze patterns, root causes, or blockers.</li>



<li><strong>Decide on actions</strong> – pick specific improvements for the next sprint.</li>



<li><strong>Close</strong> – appreciate contributions and align on next steps.</li>
</ol>



<p class="wp-block-paragraph">ð So, you can think of it like this:</p>



<ul class="wp-block-list">
<li><strong>Sprint Review</strong>: External focus — <em>deliverables and product feedback</em>.</li>



<li><strong>Sprint Retrospective</strong>: Internal focus — <em>team process and collaboration</em>.</li>
</ul>