| <?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.5/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmi:id="-ILQMonu5qLiOKjvMlGtDPg" |
| name="new_concept,_28Gp8F6AEd22Gu98eFOlrQ" guid="-ILQMonu5qLiOKjvMlGtDPg" changeDate="2008-07-31T08:47:49.906-0400"> |
| <mainDescription><p>
 |
| Story points are probably the most commonly used estimating unit among agile teams today.&nbsp; The name&nbsp;is
 |
| derived from agile teams commonly expressing requirements as “user stories”.&nbsp;&nbsp;A story point is a relative
 |
| estimate of the "size" of the work compared to other work on the project.&nbsp;So,&nbsp;a 10-point user story is
 |
| expected to take twice as long as a 5-point user story.
 |
| </p>
 |
| <p>
 |
| Estimates are not quantified but implicitly&nbsp;include&nbsp;the&nbsp;team's collective&nbsp;understanding of the
 |
| complexity, risk and time for&nbsp;the work being estimated.&nbsp; A story point is unique to the team and cannot be
 |
| compared with a story point on another team.&nbsp;&nbsp;It can be counter productive to map&nbsp;story points to
 |
| their&nbsp;absolute time equivalent and the accepted technique&nbsp;for predicting time to completion is the team's
 |
| velocity.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
