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 it should not.
Main Description

Introduction

The purpose in this phase is to achieve concurrence among all stakeholders on the lifecycle objectives for the project.

When trying to understand project scope and objectives, as well as feasibility of intended solution, there are four objectives for Inception phase [KRO03]:

  1. 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).
  2. Identify key system functionality. Decide which requirements are most critical.
  3. Determine at least one possible solution. Identify at least one candidate architecture and its feasibility.
  4. Understand the cost, schedule and risks associated with the project.

The following table summarizes the Inception phase objectives and what activities address each objective:

Phase objectives

Activities addressing 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
Assess and Plan Next Iteration



Key Considerations

Projects may have one or more iterations in Inception phase. Among reasons for multiple iteratios in Inception, you find:

  • Project is large and it is hard to define its scope.
  • Unprecedent system.
  • Too many stakeholders with competing needs and complex relations.
  • Major technical risks demanding the creation of a prototype or proof-of-concept.