| <?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:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmlns:rmc="http://www.ibm.com/rmc" |
| rmc:version="7.5.0" xmi:id="-aOaMjqW4RZWOiHT1_U1NNw" |
| name="deploying_the_solution,_yYlQoC3xEdycYKq0PulnEQ" guid="-aOaMjqW4RZWOiHT1_U1NNw" |
| changeDate="2009-07-08T13:22:35.711-0700" version="7.5.0"> |
| <mainDescription><h3>
 |
| Planning transition iterations
 |
| </h3>
 |
| <p>
 |
| Software may be deployed into a production environment at the end of any Construction or Transition iteration.
 |
| Deployment to production before the end of the project may be done to drive down risk by validating the application,
 |
| deployment scripts, deployment environment, and to get valuable feedback from operations and systems teams, as well as
 |
| end users. These early deployments are often done on a limited scale in terms of target audience or only partial
 |
| applications are deployed. For the deployment to work, one or several iterations are focused on work necessary to
 |
| successfully release the system. In the Transition phase, one or several iterations may be dedicated to preparing for a
 |
| smooth deployment. The number of iterations depends on the complexity of the system and various other factors, as
 |
| listed here. When planning for deployment, the Work Items list should be updated with relevant tasks related to these
 |
| considerations:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Resolving defects
 |
| </li>
 |
| <li>
 |
| Testing installation or deployment scripts to avoid surprises in actual deployment&nbsp;
 |
| </li>
 |
| <li>
 |
| Updating any&nbsp;operations&nbsp;and support test environments used to simulate production problems
 |
| </li>
 |
| <li>
 |
| Performing release-specific testing efforts, such as pilot or beta testing,to a subset of your end-user community
 |
| where the system is deployed
 |
| </li>
 |
| <li>
 |
| Conducting acceptance reviews with stakeholders, including a&nbsp;final release acceptance testing effort where
 |
| people outside of the team are involved and decide whether it truly meets their needs
 |
| </li>
 |
| <li>
 |
| Finalizing relevant documentation, such as operations and system manuals, end-user documentation and release notes
 |
| </li>
 |
| <li>
 |
| Creating&nbsp;physical collateral, such as installation media
 |
| </li>
 |
| <li>
 |
| Replacing or installing physical assets, or both, including workstations, servers, and network components
 |
| </li>
 |
| <li>
 |
| Replacing existing software with new versions
 |
| </li>
 |
| <li>
 |
| Updating existing databases, including any relevant data migration and database schema changes
 |
| </li>
 |
| <li>
 |
| Production data population
 |
| </li>
 |
| <li>
 |
| Training end users and operations&nbsp;and support staff
 |
| </li>
 |
| <li>
 |
| Fixing any discrepancies discovered during the transition phase
 |
| </li>
 |
| <li>
 |
| Setting up management and operational systems and processes
 |
| </li>
 |
| <li>
 |
| Training the team that is taking over maintenance and evolution of the system
 |
| </li>
 |
| <li>
 |
| Deploying the software to the production environment
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| When the team and stakeholders are reviewing late Construction and early Transition iterations, the team should gather
 |
| feedback from actual stakeholders' use of the product and take that information into consideration when prioritizing
 |
| the work for the next iteration.
 |
| </p>
 |
| <p>
 |
| See [<a class="elementLinkWithUserText"
 |
| href="./../../../core.tech.common.base/guidances/supportingmaterials/references.tech_6CCF393.html#AMB07"
 |
| guid="_9ToeIB83Edqsvps02rpOOg">AMB07</a>]&nbsp; for more information.
 |
| </p>
 |
| <h3>
 |
| Reviewing transition iterations
 |
| </h3>
 |
| <p>
 |
| Transition iteration reviews have a different focus from other iterations in the project lifecycle. The goal is not to
 |
| brainstorm about what&nbsp;features to develop next. Instead, reviews will assess the release management resources and
 |
| procedures, the quality of the software,&nbsp;and how prepared users and operations teams are to face a move of the
 |
| software into the production environment.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
