<?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" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-R1d0qAJDnmI5Fm9ChHCYQw" name="how_to_adopt,_ERIDQOMPEdyM47cGD2jiaQ" guid="-R1d0qAJDnmI5Fm9ChHCYQw" changeDate="2008-06-30T01:42:52.000-0700" version="7.2.0">
  <mainDescription>&lt;h3>&#xD;
    Getting started&amp;nbsp;&#xD;
&lt;/h3>Organize your project into a set of phases, each providing a milestone where business and management decisions can be&#xD;
made on whether the project should go to the next phase or not. A risk-value lifecycle&amp;nbsp;provide stakeholders with&#xD;
visibility on two main drivers: risks need to be driven down and value&amp;nbsp;needs&amp;nbsp;to be&amp;nbsp;driven up.&amp;nbsp;At the&#xD;
end of each phase in the lifecycle, there is a milestone that will help answer the questions and find the balance between&#xD;
risks and value. See &lt;a class=&quot;elementLink&quot;&#xD;
href=&quot;./../../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/phase_milestones_5678231E.html&quot;&#xD;
guid=&quot;_HNxbwMBJEdqSgKaj2SZBmg&quot;>Phase Milestones&lt;/a>&amp;nbsp;for more information on milestones and &lt;a class=&quot;elementLink&quot;&#xD;
href=&quot;./../../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/project_lifecycle_203F87.html&quot;&#xD;
guid=&quot;_nSfVwCNYEdyCq8v2ZO4QcA&quot;>Project Lifecycle&lt;/a>&amp;nbsp;for more information on balancing risks and value.&lt;br />&#xD;
&lt;p>&#xD;
    Divide phases into iterations that deliver an increment of software that you can&amp;nbsp;demonstrate and, potentially,&#xD;
    deliver.&amp;nbsp;Each iteration in a phase will contain just enough of any activity required to meet the objectives of&#xD;
    that phase by the time you meet the milestone that concludes it. If the milestone can't be satisfied, consider adding&#xD;
    one more iteration to that phase until the expected risks&amp;nbsp;for the phase are mitigated or the expected stakeholder&#xD;
    value is provided.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Plan the number of iterations in each phase according to the lifecycle pattern that is most appropriate to your&#xD;
    project. For example, when the problem domain is familiar, the risks are well-understood, and the project team is&#xD;
    experienced, you may need only one iteration in Inception and one in Elaboration phases, then&amp;nbsp;you can have&#xD;
    multiple iterations in Construction&amp;nbsp;(to develop the requirements and architecture) and a few iterations in&#xD;
    Transition to migrate the product to users.&amp;nbsp;Another example is when the problem domain is new or unfamiliar or the&#xD;
    team is inexperienced. In such a case, you might need several iterations in Elaboration to refine requirements and&#xD;
    architecture as you implement them, then one iteration in&amp;nbsp;Construction to deal with less critical requirements.&#xD;
    For more information on lifecycle patterns see&amp;nbsp;[&lt;a class=&quot;elementLinkWithUserText&quot;&#xD;
    href=&quot;./../../../core.mgmt.common.base/guidances/supportingmaterials/references.mgmt_D80619F3.html#DOD94&quot;&#xD;
    guid=&quot;_JlTPUM6aEdyuBO4ZIzcyig&quot;>DOD94&lt;/a>] and [&lt;a class=&quot;elementLinkWithUserText&quot;&#xD;
    href=&quot;./../../../core.mgmt.common.base/guidances/supportingmaterials/references.mgmt_D80619F3.html#GIL88&quot;&#xD;
    guid=&quot;_JlTPUM6aEdyuBO4ZIzcyig&quot;>GIL88&lt;/a>].&amp;nbsp;&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Phases are not identical in terms of schedule and effort. For example,&amp;nbsp;a typical distribution&amp;nbsp;of resources&#xD;
    and time spent for a medium-sized project is represented in the table below.&#xD;
&lt;/p>&#xD;
&lt;table title=&quot;Typical distribution of schedule and effort on a mid-sized project&quot; cellspacing=&quot;0&quot; cellpadding=&quot;2&quot;&#xD;
width=&quot;85%&quot; border=&quot;1&quot;>&#xD;
    &lt;tbody>&#xD;
        &lt;tr>&#xD;
            &lt;th id=&quot;&quot; scope=&quot;col&quot; abbr=&quot;&quot;>&#xD;
            &lt;/th>&#xD;
            &lt;th id=&quot;&quot; scope=&quot;col&quot; abbr=&quot;&quot;>&#xD;
                Inception&#xD;
            &lt;/th>&#xD;
            &lt;th id=&quot;&quot; scope=&quot;col&quot; abbr=&quot;&quot;>&#xD;
                Elaboration&#xD;
            &lt;/th>&#xD;
            &lt;th id=&quot;&quot; scope=&quot;col&quot; abbr=&quot;&quot;>&#xD;
                Construction&#xD;
            &lt;/th>&#xD;
            &lt;th id=&quot;&quot; scope=&quot;col&quot; abbr=&quot;&quot;>&#xD;
                Transition&#xD;
            &lt;/th>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;th id=&quot;&quot; scope=&quot;row&quot; abbr=&quot;&quot;>&#xD;
                Effort&#xD;
            &lt;/th>&#xD;
            &lt;td>&#xD;
                ~5%&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                20%&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                65%&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                10%&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;th id=&quot;&quot; scope=&quot;row&quot; abbr=&quot;&quot;>&#xD;
                Schedule&#xD;
            &lt;/th>&#xD;
            &lt;td>&#xD;
                10%&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                30%&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                50%&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                10%&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
    &lt;/tbody>&#xD;
&lt;/table>&#xD;
&lt;p>&#xD;
    For more information and examples of projects adopting the four-phase lifecycle, see [&lt;a&#xD;
    class=&quot;elementLinkWithUserText&quot;&#xD;
    href=&quot;./../../../core.mgmt.common.base/guidances/supportingmaterials/references.mgmt_D80619F3.html#KRO03&quot;&#xD;
    guid=&quot;_JlTPUM6aEdyuBO4ZIzcyig&quot;>KRO03&lt;/a>].&#xD;
&lt;/p>&#xD;
&lt;h3>&#xD;
    Common pitfalls&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    A common misconception about the four unified process phases is to compare them to&amp;nbsp;a waterfall approach, where one&#xD;
    would expect to document all of the requirements in Inception, create the whole design and architecture in Elaboration,&#xD;
    do all of the implementation in Construction, and test in Transition. Phases are&amp;nbsp;time-allocated in the project&#xD;
    schedule and&amp;nbsp;provide a framework and milestones for making business and management decisions. Each iteration in&#xD;
    each phase provides a complete pass through activities in the disciplines&amp;nbsp;of software development (for example,&#xD;
    requirements, design, implementation, integration, testing, and so on) and produces an executable&amp;nbsp;increment of&#xD;
    software&amp;nbsp;that minimizes risks and grows in value.&#xD;
&lt;/p></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
