<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription 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="-k3Ss0y6wDinVKIhm-m2wTA" name="new_concept,_HmEeALsSEe29CKVnbOLlJg" guid="-k3Ss0y6wDinVKIhm-m2wTA" changeDate="2023-03-05T08:27:55.187+0330">
  <mainDescription>Story points are probably the most commonly used estimating unit among agile teams today.&amp;nbsp; The name&amp;nbsp;is derived&#xD;
from agile teams commonly expressing requirements as “user stories”.&amp;nbsp;&amp;nbsp;A story point is a relative estimate of the&#xD;
&quot;size&quot; of the work compared to other work on the project.&amp;nbsp;So,&amp;nbsp;a 10-point user story is expected to take twice as&#xD;
long as a 5-point user story. &#xD;
&lt;p>&#xD;
    Estimates are not quantified but implicitly&amp;nbsp;include&amp;nbsp;the&amp;nbsp;team's collective&amp;nbsp;understanding of the&#xD;
    complexity, risk and time for&amp;nbsp;the work being estimated.&amp;nbsp;Generally&amp;nbsp;a story point is unique to the team&#xD;
    and cannot be compared with a story point on another team but becuase of multi team people nature of methodology point&#xD;
    must be global in all project.&amp;nbsp;It can be counter productive to map&amp;nbsp;story points to their&amp;nbsp;absolute time&#xD;
    equivalent and the accepted technique&amp;nbsp;for predicting time to completion is the team's velocity.&#xD;
&lt;/p></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
