Guideline: Plan Project Phases |
This guideline explains how to plan the phases of a project.
Relationships
Related Elements | Plan the Project
Main Description
Each phase takes a certain perspective on a project. The objectives of the iterations inside the phases need to be aligned with the goal of a phase. The following table provides general rules for the objectives of each phase, how many resources are allocated and how long each phase should last compared with the overall schedule. At the end of each phase, the success of each phase is evaluated and go-no-go decisions points for executive management offered.
Phase | Objectives | # / length of iteration (weeks) | Resources | Duration
Inception | Identify: Coarse-grained requirements Risks Candidate architectures | ~1-2 / 2-4 weeks | ~5% | ~10%
Elaboration | Prove: Architecture Critical functionality High-level risk reduction | 1-2 / 2-6 | ~20% | ~30%
Construction | Build: Continue detailing requirements Functionality | 1-n 2-4 | ~65% | ~50%
Transition | Enable: Deployment Fine-tuning | 1-2 / 2-4 | ~10% | ~10%
Example: Schedule for a 4 month project, starting 9/1/2006 using the phase plan above.
Phase | # / length of iteration (weeks) | Duration
Inception | One 1-week Iteration | 9/1/2006 – 9/8/2006
Elaboration | One 3-week Iteration One 2-week Iteration | 9/11/2006-10/13/2006
Construction | Four 2-week Iterations | 10/16/2006-12/8/2006
Transition | One 2-week interation | 12/11/2006-12/22/2006
This program and the accompanying materials are made available under the Eclipse Public License v1.0 which accompanies this distribution. View copyright information here: OpenUP Copyright