| <?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.5/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmi:id="-NrSTjiuzDnfEiZxA7N_tFA" |
| name=",_RunHEF8ZEd22Gu98eFOlrQ" guid="-NrSTjiuzDnfEiZxA7N_tFA" changeDate="2008-07-31T12:05:05.046-0400"> |
| <mainDescription><p>
 |
| At the beginning of a project the team will create a&nbsp;high-level release plan.&nbsp; The team cannot possibly know
 |
| everything up front so a detailed plan is not necessary.&nbsp; The&nbsp;release plan should&nbsp;address:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| The number and duration of the sprints
 |
| </li>
 |
| <li>
 |
| How many people or teams should be on this project
 |
| </li>
 |
| <li>
 |
| The number of releases
 |
| </li>
 |
| <li>
 |
| The value delivered in&nbsp;each release
 |
| </li>
 |
| <li>
 |
| The ship date for the releases
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Key inputs to release planning are:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| The prioritized Product Backlong
 |
| </li>
 |
| <li>
 |
| The&nbsp;estimated velocity
 |
| </li>
 |
| <li>
 |
| Any hard and fast&nbsp;to-market dates the Product Owner must satisfy
 |
| </li>
 |
| </ul></mainDescription> |
| <purpose>To level-set expectations (internal and external) and to proactively uncover needs and dependencies</purpose> |
| </org.eclipse.epf.uma:TaskDescription> |
