EPF_Practices/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/transition_phase.xmi

<?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:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf"
    epf:version="1.5.0" xmi:id="-FrUmsKsGW4bnNmb9uaNOkg"
    name=",__ca5UBOMEduCNqgZdt_OaA" guid="-FrUmsKsGW4bnNmb9uaNOkg" changeDate="2008-02-24T08:16:27.171-0800"
    version="1.0.0">
  <mainDescription>&lt;p>&#xD;
    The purpose in this phase is to ensure that the software is ready for delivery to users.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    There are objectives for the Transition phase that help you to&amp;nbsp;fine-tune functionality, performance, and overall&#xD;
    quality of the beta product from the end of&amp;nbsp;the previous phase &lt;a class=&quot;elementlinkwithusertext&quot; href=&quot;./../../../core.mgmt.common.base/guidances/supportingmaterials/references.mgmt_D80619F3.html#KRO03&quot; guid=&quot;_JlTPUM6aEdyuBO4ZIzcyig&quot;>[KRO03]&lt;/a>:&#xD;
&lt;/p>&#xD;
&lt;ol>&#xD;
    &lt;li>&#xD;
        &lt;p>&#xD;
            &lt;strong>Beta test to validate that user expectations are met.&lt;/strong> This typically requires some fine-tuning&#xD;
            activities, such as bug-fixing and making enhancements for performance and usability.&#xD;
        &lt;/p>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;p>&#xD;
            &lt;strong>Achieve stakeholder concurrence that deployment is complete.&lt;/strong> This may involve various levels&#xD;
            of tests for product acceptance, including formal and informal tests and beta tests.&#xD;
        &lt;/p>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;p>&#xD;
            &lt;strong>Improve future project performance through lessons learned.&lt;/strong> Document lessons learned and&#xD;
            improve the process and tool environment for the project.&#xD;
        &lt;/p>&#xD;
    &lt;/li>&#xD;
&lt;/ol>&#xD;
&lt;h4> Key considerations&lt;/h4>&#xD;
&lt;p> The Transition phase can include running old and new systems in parallel, &#xD;
  migrating data, training users, and adjusting business processes. &lt;/p>&#xD;
&lt;p>&#xD;
    The number of iterations in the Transition phase varies from one iteration for a simple system requiring primarily&#xD;
    minor bug fixing, to many iterations for a complex system, involving addition of features and performing activities to&#xD;
    make the business transition from using the old system to using the new system.&#xD;
&lt;/p>&#xD;
&lt;p> When the Transition phase objectives are met, the project can be closed.&amp;nbsp;For &#xD;
  some products, the end of the current project lifecycle may coincide with the &#xD;
  beginning of the next lifecycle, leading to the next generation of the same &#xD;
  product. &lt;/p></mainDescription>
</org.eclipse.epf.uma:ContentDescription>