software project management -->Transition Phase

1. TRANSITION PHASE
uploaded by : REHMAT ULLAH

2. The purpose of this phase is to ensure that the software is ready for
the delivery to users.
There are objectives for the Transition phase that help you to fine-
tune functionality, performance, and overall quality of the beta
product from the end of the previous phase

3. 1. Beta test to validate that user expectations are
met. This typically requires some fine-tuning
activities, such as bug-fixing and making
enhancements for performance and usability.
2. Achieve stakeholder concurrence that
deployment is complete. This may involve various
levels of tests for product acceptance, including formal
and informal tests and beta tests.

4. 3. Prepare deployment site and convert operational
databases. To get the new system up and running, you may
have to purchase new hardware, add space for new
hardware, or convert data from earlier systems to the new
system.
4. Train users and maintainers to achieve user self-
reliability. These activities ensure that the adopting
organization(s) are qualified to use the system and have moved
any necessary data from earlier systems or taken any other
measures required to operate the new system successfully.

5. 5. Improve future project performance through
lessons learned. This includes documenting lessons
learned and improving the process and tool environment.

6. The Transition phase can include running old and new
systems in parallel, migrating data, training users, and
adjusting business processes.
When the Transition phase objectives are met, the project
can be closed. 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.

7. http://www.ambysoft.com/unifiedprocess/aup11/html
/transition.html
http://projectmanagement.hubpages.com/hub/Transitio
n_Phase