Initiating a Project

From IT frameworks

Contents 1 Initiating a Project (IP) 1.1 Purpose & Description 1.2 Objectives 1.3 Inputs 1.4 Outputs 1.5 Hints and Tips 2 Sub-processes

Initiating a Project (IP)

Purpose & Description

• This process lays down the foundations upon which the Project will be built.
• This process ensures the expectations within the Project are well understood and defines resources needed to complete the Project within the approved timeframe.
• This Process follows after Directing a Project, as long as DP1 approves the initiation of the Project.

Objectives

• Ensures the Business Case for the Project is fully understood.
• Ensures the deliverables are qualified and quantified.
• Ensures the Project Board own the Project.
• Ensures Quality expectations are defined and measuring methods determined.
• Ensures Risks are managed.
• To produce a Next Stage Plan.

Inputs

• Authorisation to proceed from Project Board
• Project Brief & Initial Stage Plan.

Outputs

• PID to DP2
• Next Stage Plan to DP3.

Hints and Tips

• For small projects both SU & IP can be combined. Then the output to Project Board should be the Project Brief + Initial Stage Plan = PID yet still ensuring the Project Board receive the necessary information.

Sub-processes

• IP1 Planning Quality
• IP2 Planning a Project
• IP3 Refining the Business Case and Risks
• IP4 Setting up Project Controls
• IP5 Setting up Project Files
• IP6 Assembling a Project Initiation Document