Concept: Inception Phase |
First of the four phases in the project lifecycle, it is about understanding the project scope and objectives and getting enough information to confirm that the project should proceed - or convince you that it should not.
Main Description
The purpose in this phase is to achieve concurrence among all stakeholders on the lifecycle objectives for the project. When trying to understand the project scope and objectives, as well as the feasibility of the intended solution, there are four objectives for the Inception phase [KRO03]: Understand what to build. Determine the Vision, the scope of the system, and its boundaries. Identify who is interested in this system and why (see Stakeholders). Identify key system functionality. Decide which requirements are most critical. Determine at least one possible solution. Identify at least one candidate architecture and its feasibility. Understand the cost, schedule, and risks associated with the project. The following table summarizes the Inception phase objectives and what activities address each objective: Inception phase objectives and activities
Phase objectives | Activities that address objectives
Understand what to build | Manage Requirements
Identify key system functionality | Initiate Project Manage Requirements
Determine at least one possible solution | Determine Architectural Feasibility
Understand the cost, schedule, and risks associated with the project | Initiate Project Manage Iteration
#### Key considerations Projects may have one or more iterations in the Inception phase. Among reasons for multiple iterations in Inception, you find: Project is large, and it is hard to define its scope. Unprecedented system. Too many stakeholders with competing needs and complex relationships. Major technical risks demand the creation of a prototype or proof of concept.
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