<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-csiMO5Li8kAQqqCWULo6Wg" name="iteration_review_meeting,_fSg-Y8WhEe6PpZUqNEM0jA" guid="-csiMO5Li8kAQqqCWULo6Wg" changeDate="2024-02-07T02:10:46.702-0800">
  <mainDescription>At the end of each sprint a iteration review meeting is held. During this meeting the Scrum team shows what they&#xD;
accomplished during the iteration. Typically this takes the form of a demo of the new features.&lt;br />&#xD;
&lt;br />&#xD;
Participants in the iteration review typically include the Product Owner, the team, management, customers, and engineers&#xD;
from other projects.&lt;br />&#xD;
&lt;br />&#xD;
During the iteration review the project is assessed against the iteration goal determined during the iteration planning&#xD;
meeting. Ideally the team has completed each product backlog item brought into the iteration, but it is more important that&#xD;
they achieve the overall goal of the iteration.</mainDescription>
  <keyConsiderations>The iteration review meeting is intentionally kept very informal, typically with rules forbidding the use of PowerPoint&#xD;
slides and allowing no more than two hours of preparation time for the meeting. A iteration review meeting should not&#xD;
become a distraction or significant detour for the team; rather, it should be a natural result of the iteration.&lt;br /></keyConsiderations>
</org.eclipse.epf.uma:TaskDescription>
