| <?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.4/uma.ecore" |
| xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.2.0" xmlns:epf="http://www.eclipse.org/epf" |
| epf:version="1.2.0" xmi:id="-bhzuf6RMHP3d-AHkoKDg7g" |
| name="phase,__7xOEC7aEdqHMdmRzC0-2g" guid="-bhzuf6RMHP3d-AHkoKDg7g" changeDate="2008-02-22T01:49:33.109-0500" |
| version="1.0.0"> |
| <mainDescription><h3>
 |
| What is a Phase?
 |
| </h3>
 |
| <p>
 |
| While the entire purpose of a project is to produce a product, the specific goals of the team will vary substantially
 |
| throughout the project. In the beginning, there usually is considerable latitude in the requirements for the product.
 |
| It may not be clear whether the project is feasible or even if it is likely to be profitable. At that time, it is
 |
| critical to bring an answer to these questions, and of little to no value to start developing the product in
 |
| earnest.&nbsp;Towards the end of the project, the product itself is usually complete, and issues of quality, delivery,
 |
| and completeness then take center stage. At different points in time, tasks are undertaken in new ways and work
 |
| products will have new content.
 |
| </p>
 |
| <p>
 |
| To coordinate the team’s efforts in a manner that takes these fundamental observations into account, the project
 |
| lifecycle should be divided into a sequence of phases. Each phase has a defined set of goals, its own iteration style
 |
| and customized&nbsp; <a class="elementLinkWithUserText"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html"
 |
| guid="_x459ktnmEdmO6L4XMImrsA">tasks</a>&nbsp;and&nbsp;<a class="elementLinkWithUserText"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html"
 |
| guid="_H4JXwB_SEdq6CKKKq4D7YA">work products</a> to address the unique needs of the project at that point in time.
 |
| </p>
 |
| <p>
 |
| We recommend&nbsp;dividing the project lifecycle into&nbsp;four phases: Inception, Elaboration, Construction and
 |
| Transition.
 |
| </p>
 |
| <h3>
 |
| Iteration and Phases
 |
| </h3>
 |
| <p>
 |
| Each phase is divided into iterations. An iteration is a complete development loop resulting in a build (internal or
 |
| external) of an executable system, usually a subset of the final product under development, which grows incrementally
 |
| from iteration to iteration to become the final product.<br />
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
