180 likes | 326 Views
PRJ480 Mastering the Management of Iterative Development v2. Module 5: Phase Management - Construction. Module 5 Objectives. As a project progresses through phases and iterations, Describe the changing emphasis of Project Management by:
E N D
PRJ480 Mastering the Management of Iterative Development v2 Module 5: Phase Management - Construction
Module 5 Objectives As a project progresses through phases and iterations, Describe the changing emphasis of Project Management by: • Understanding Construction objectives, milestones, and evaluation criteria. • Understanding principal Construction activities and artifacts and their uses. • Discussing team considerations regarding building the product.
Construction Primary Objectives: • Minimizing development costs by optimizing resources and avoiding unnecessary scrap and rework • Achieving adequate quality as rapidly as practical • Achieving useful versions (alpha, beta, and other test releases) as rapidly as practical Essential Activities: • Resource management, control, and process optimization • Complete component development and testing against evaluation criteria • Assessment of product releases against acceptance criteria of the vision
Entering Construction • Major project risks have been mitigated, and the architecture is established on a firm foundation during Elaboration. • The tone of the project changes from engineering to production. • You know what you need to do (most of the invention was achieved and uncertainties were removed). • Staffing is increased. • Planning is aimed at efficiency and quality.
Construction Considerations • Phase Focus • Resource management control and process optimization • Complete component development • Assess product against acceptance criteria and vision
Construction Considerations • Measurements • Progress 90% • Expenditures (rate) High • Staffing Steady • Stability Moderate • Modularity <25% • Adaptability Benign • Maturity Usable
Rework in the Iterative Lifecycle Extensive rework during Construction is avoided through solidifying the architecture in the Elaboration phase. • Too much rework • Gold plating • Unstable requirements • Not enough focus on cost and schedule • Too little rework • Excessive schedule pressure • Poor quality testing • Perception of rework as incompetence or failure
100 75 50 25 Rework Trends Rework (% of total) Rework after architectural baseline should total <= 25% of the system Inception Elaboration Construction Transition
Importance of Testing: A Manager’s Perspective • Tests represent a part of the exit criteria for phases. • Tests provide some risk mitigation. • Tests of executable code provide quantifiable progress. • Test results provide quality measurements.
Test Each Iteration: Functionality and Performance Iteration 1 Iteration 2 Iteration 3 Iteration 4 Test Suite 1 Test Suite 2 Test Suite 3 Test Suite 4 Tests
Construction Essential Artifacts • The System • Deployment Plan • Implementation Model (and all constituent artifacts, including Implementation Elements) • Test Suite ("smoke test") • User Support Material • Iteration Plan • Design Model (and all constituent artifacts) • Development Process • Development Infrastructure • Data Model
Construction% Management 10 Environment/CM 5 Requirements 8 Design 16 Implementation 34 Assessment 24 Deployment 3 Total 100 RUP Distribution of Skills by Phase Percentage of effort by activity for the Construction phase.
Construction Evaluation Criteria • Is this product baseline mature enough to be deployed in the user community? • Is this product baseline stable enough to be deployed in the user community? • Are the collateral artifacts ready for transition to the user community? • Are actual resource expenditures versus planned expenditures acceptable?
Construction Phase Management Issues • Project not converging • Forgetting about new risks
Construction Phase Recommendations • Each release provides: • A sense of accomplishment to developers • A point of control to managers • Reassurance to customers and other stakeholders • Never throw a release at a customer without preparation • Set expectations • Spend time with the customer • Adhere to the release schedule, shifting functionality rather than schedules • But beware of the snowplow effect, where everything gets pushed to the end of the schedule
Discussion: Characteristics of Construction • What are expected characteristics of the project during Construction? • What are activities that need emphasis during Construction?
Module 5 Review • The main objective of Construction is to build the product. • Avoid rework by solidifying architecture in Elaboration • Never throw a release at a customer without preparation • Test each iteration for functionality and performance • Essential artifacts are: • The system • Iteration Plan/Assessment