<?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="-bKCPpzSyEsmYjTJRRzG7Tg" name="iteration_planning,_RIQ2QcWNEe6PpZUqNEM0jA" guid="-bKCPpzSyEsmYjTJRRzG7Tg"/>
  <org.eclipse.epf.uma:DescriptorDescription xmi:id="-DwvZnCjxE2G3LOAUEnaZVw" name="estimating_the_backlog,_b7Xm8MWiEe6PpZUqNEM0jA" guid="-DwvZnCjxE2G3LOAUEnaZVw">
    <refinedDescription>&lt;p>&#xD;
    Prior to release planning and periodically as the product backlog evolves and the team gains insight through experience&#xD;
    the Team will estimate the size of items on the Product Backlog.&amp;nbsp;&amp;nbsp; This is key information to help&#xD;
    the&amp;nbsp;Product Owner make prioritization decisions (some items may become less of a priority if the&amp;nbsp;Product&#xD;
    Owner learns that major effort will be required to deliver them).&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Estimations are relative and&amp;nbsp;are measured in “points” rather than real-world units of effort.&amp;nbsp; To the&#xD;
    uninitiated this may&amp;nbsp;seem unpredicatable but after the first few iterations, teams can empirically derive&amp;nbsp;a&#xD;
    velocity&amp;nbsp;that allows them to&amp;nbsp;accurately predict delivery capability.&amp;nbsp;&lt;br />&#xD;
&lt;/p></refinedDescription>
  </org.eclipse.epf.uma:DescriptorDescription>
  <org.eclipse.epf.uma:DescriptorDescription xmi:id="-aW-xU7YHA0YT5xCeAWhHPg" name="iteration_planning_meeting,_cc_tUMWiEe6PpZUqNEM0jA" guid="-aW-xU7YHA0YT5xCeAWhHPg">
    <keyConsiderations>The product owner doesn't have to describe every item being tracked on the product backlog. Depending on the size of the&#xD;
backlog and the speed of the team it may be sufficient to describe only the high priority items, saving the discussion of&#xD;
lower priority items for the next iteration planning meeting. Typically, the team will provide guidance when they start to&#xD;
get further into the backlog list than they know could be done in the next iteration.</keyConsiderations>
    <refinedDescription>&lt;p>&#xD;
    The Iteration Planning Meeting is attended by the Product Owner, the entire Team, and any interested and appropriate&#xD;
    management or customer representatives.&lt;br />&#xD;
    &lt;br />&#xD;
    During the iteration planning meeting the product owner describes the highest priority features to the team. The team&#xD;
    asks enough questions during this meeting so that they can go off after the meeting and determine which tasks they will&#xD;
    move from the product backlog to the iteration backlog.&lt;br />&#xD;
    &lt;br />&#xD;
    Collectively, the team and the product owner define a iteration goal, which is a short description of what the&#xD;
    iteration will attempt to achieve. The success of the iteration will later be assessed during the iteration Review&#xD;
    Meeting against the iteration goal, rather than against each specific item selected from the product backlog.&lt;br />&#xD;
    &lt;br />&#xD;
    After the iteration planning meeting, the team meets separately to discuss what they heard and decide how much they can&#xD;
    commit to during the coming iteration. In some cases there will be negotiation with the product owner but it will&#xD;
    always be up to the team to determine how much they can commit to completing.&#xD;
&lt;/p></refinedDescription>
  </org.eclipse.epf.uma:DescriptorDescription>
  <org.eclipse.epf.uma:DescriptorDescription xmi:id="-yNi2cof_4ydv8k2GcGi-JQ" name="solution_architect,_cdCJkMWiEe6PpZUqNEM0jA" guid="-yNi2cof_4ydv8k2GcGi-JQ">
    <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>
</xmi:XMI>
