<?xml version="1.0" encoding="UTF-8"?>
<xmi:XMI 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">
  <org.eclipse.epf.uma:ProcessDescription xmi:id="-TBSlP9wLfvrxrmg7W0hBjw" name="iteration_epilogue,_A9vKkcWcEe6PpZUqNEM0jA" guid="-TBSlP9wLfvrxrmg7W0hBjw"/>
  <org.eclipse.epf.uma:DescriptorDescription xmi:id="-irRtvePP1G4bNVrEw-S0og" name="iteration_review_meeting,_oFVpcMWiEe6PpZUqNEM0jA" guid="-irRtvePP1G4bNVrEw-S0og">
    <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>
    <refinedDescription>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.</refinedDescription>
  </org.eclipse.epf.uma:DescriptorDescription>
  <org.eclipse.epf.uma:DescriptorDescription xmi:id="-0pEpb2k5MONiymhatrZBSA" name="solution_architect,_oFXepsWiEe6PpZUqNEM0jA" guid="-0pEpb2k5MONiymhatrZBSA">
    <refinedDescription>&lt;p>&#xD;
    &quot;Idea Gostaran&quot; Projects are related and their software solutions are architecturally related.&#xD;
&lt;/p></refinedDescription>
  </org.eclipse.epf.uma:DescriptorDescription>
  <org.eclipse.epf.uma:DescriptorDescription xmi:id="-dcVzWrpCOR0jE4wEWImKLg" name="iteration_retrospective,_ocK1EMWiEe6PpZUqNEM0jA" guid="-dcVzWrpCOR0jE4wEWImKLg">
    <refinedDescription>&lt;p>&#xD;
    The Iteration Retrospective is an opportunity for the team to discuss what's working and what's not working, and agree&#xD;
    on changes to try.&amp;nbsp; One approach taken is that the whole team gathers and discusses what they’d like to&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Start doing&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Stop doing&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Continue doing&#xD;
    &lt;/li>&#xD;
&lt;/ul></refinedDescription>
  </org.eclipse.epf.uma:DescriptorDescription>
</xmi:XMI>
