Initiating A Project

home

Articles

Risk Blog

Traders Blog

Initiating A Project

Initiating a Project (IP) is the second process in the Prince2 project management methodology.

What One of eight processes in Prince2, Initiating a Project is essentially the time when the project officially "starts".

All the information and personnel required to run the project should have be gathered in the previous stage, Starting Up A Project.

There are a number of sub-processes:-

*Planning Quality (IP1)
*Planning A Project (IP2)
*Refining the Business Case and Risks (IP3)
*Setting Up Project Controls (IP4)
*Setting Up Project Files (IP5)
*Assembling a Project Initiation Document (IP6)

Why Prince2 recommends that every project should have an initiation stage. At the end, the project board and the project manager will have confirmeed in writing what they understanding of what is to be done, project constraints and how control is to be applied.

The detail of why you have an initiation process is clear when the aims are seen:-

*The key products the project will deliver.
*The scope
*Constraints on the product to be delivered.
*The good reasons for doing the project.
*Any project constraints
*Who the decision makers are
*The how and when of product delivery
*Cost
*How quality will be achieved
*Project control
*The commitment looked for

All this information should end up packaged in the Product Initiation Document.

How Largely the responsibility of the Project Manager, how the Initiation process is handled can set the tone for the whole project. So tailoring of the process according to nature of the project undertaken is especially important.

Depending on the project and the amount of ceremony involved, the following are products to be worked towards in IP.

*Project Quality Plan (IP1)
*Project Inititation Document (IP6)
*Communications Plan (IP4)
*Quality Log (IP5)
*Issue Log (IP4/5)
*Lessons Learned Log (IP5)
*Risk Log (IP3)