1. ® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 6: Phase Management -Transition

2. 6-2 Module 6 Objectives As a project progresses through phases and iterations, Describe the changing emphasis of Project Management by:  Understanding Transition objectives, milestones, and evaluation criteria.  Understanding principal Transition activities and artifacts and their uses.  Understanding team considerations regarding delivering the product to end users.

3. 6-3 Transition Primary Objectives:  Achieving user self-supportability  Achieving stakeholder concurrence that deployment baselines are complete and consistent with the evaluation criteria of the vision  Achieving final product baselines as rapidly and cost-effectively as practical Essential Activities:  Synchronization and integration of concurrent construction increments into consistent deployment baselines  Deployment-specific engineering  Assessment of deployment baselines against the complete vision and acceptance criteria in the requirements set

4. 6-4 Optional Transition Activities Transition could include any of the following activities:  Beta testing to validate the new system against user expectations  Beta testing and parallel operation relative to a legacy system it is replacing  Conversion of operational databases  Training of users and maintainers

5. 6-5 Transition Considerations Phase Focus  Deployment plans  End user support material  Create product release  Make product available to end users  Fine-tune product based on feedback

6. 6-6 Transition Considerations Measurements  Progress100%  Expenditures (rate)High  StaffingVarying  StabilityStable  Modularity5%-10%  AdaptabilityBenign  MaturityRobust

7. 6-7 Transition Iteration Planning  It is likely that the number of betas used will determine the number of Transition iterations.  Each Transition iteration requires planning and tracking the artifacts that compose the beta or final release.

8. 6-8 Transition Essential Artifacts  The Product Build  User Support Material  Implementation Elements  Optional Artifacts  Test Suite ("smoke test")  “Shrinkwrap” Product Packaging

9. 6-9 RUP Distribution of Skills by Phase Management Environment/CM Requirements Design Implementation Assessment Deployment Total Transition % 14 5 4 4 19 24 30 100 Percentage of effort by activity for Transition phase.

10. 6-10 Transition Evaluation Criteria  Is the user satisfied?  Are actual resource expenditures versus planned expenditures acceptable?

11. 6-11 Transition Phase Management Issues  Falling victim to your own success  Requests for new functionality

12. 6-12 Transition Phase Recommendations  The easiness of this phase will be proportional to:  The quality of the product  The degree to which the user has been prepared  Don’t move all your developers to another project at the end of Construction.  All but the simplest products require some form of user training.  Give adequate attention to the ease of installation. A difficult installation can destroy user confidence in a product.

13. 6-13 Discussion: Characteristics of Transition  What are expected characteristics of the project during Transition?  What are activities that need emphasis during Transition?

14. 6-14 Module 6 Review  The main objective of Transition is to successfully transition the product to a satisfied user.  The number of betas will likely determine the number of iterations.  Essential artifacts are:  Iteration Plan/Iteration Assessment (Project Manager)  The Product Build (Architect)