Transcript Mastering the Management of Iterative Development

®
IBM Software Group
PRJ480 Mastering the Management of Iterative Development v2
Module 6: Phase Management -Transition
© 2006 IBM Corporation
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.
6-2
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
6-3
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
6-4
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-5
Transition Considerations
Measurements
 Progress
 Expenditures (rate)
 Staffing
 Stability
 Modularity
 Adaptability
 Maturity
6-6
100%
High
Varying
Stable
5%-10%
Benign
Robust
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.
6-7
Transition Essential Artifacts
 The Product Build
 User Support Material
 Implementation Elements
 Optional Artifacts
 Test Suite ("smoke test")
 “Shrinkwrap” Product Packaging
6-8
RUP Distribution of Skills by Phase
Percentage of effort by activity for Transition phase.
Transition
%
Management
14
Environment/CM
5
Requirements
4
Design
4
Implementation
19
Assessment
24
Deployment
30
Total
100
6-9
Transition Evaluation Criteria
 Is the user satisfied?
 Are actual resource expenditures versus planned
expenditures acceptable?
6-10
Transition Phase Management Issues
 Falling victim to your own success
 Requests for new functionality
6-11
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.
6-12
Discussion: Characteristics of Transition
 What are expected characteristics of the project
during Transition?
 What are activities that need emphasis during Transition?
6-13
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)
6-14