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