2. Project Initiation Documentation Contents

The Project Initiation Documentation is a collection of most of the documents produced so far in both the SU and IP processes.

• First of all, we have the project approach and project definition, which contains a lot of information about the project and is extracted from the Project Brief.

• The Project Management Team Structure, which includes the Roles Descriptions.

• The Business Case, which includes time and cost information from the project plan.

• The four management strategy documents, which are Quality, Configuration Management, Risk and Communications.

• The Project Plan, which contains information on timescale, cost, resource requirements, products that will be produced, risks, tolerances, controls and quality.

• The Project Controls document, which describes how the project will be monitored and controlled, tolerances between the different management levels, and the number of stages.

• How PRINCE2 was tailored to suit the project.

Corp..

Project mandate

Corporate or Programme Management

www.Mgm tPlaza.com

Direction

Project Board

Initiation Notification

Starting up a Project (SU)

Project Init Doc

Req. Deliver Project?

Authorize initiation

Authorize the project

PID Contents

• Project Approach

• Project Management Team Structure

• Business Case

• Risk Management Strategy

• Quality Management Strategy

• Communication Management Strategy

• Project Controls

Management

Project Manager

Req. to Initiate a Project

Project Brief + IS Plan

Project Starts

Auth. To Initiate

Initiating a

Project (IP)

• Project Plan

• Tailoring and Project Definition

Delivery

Team Manager

-- Once during project

-- Once per stage

-- Many times during stage

-- Once per Work Package

Notification ^{-- Notification}

Auth.

-- Authorization

Mgmt Prod -- Management Product

Based on OGC PRINCE2® material. Reproduced under license from OGC

Pre-Project Initiation

Fig 3.10 PID Contents

8. Sb: Managing a Stage Boundary after the Initiation Stage

This is the first Managing a Stage Boundary process and it is normally performed after each Controlling a Stage process or each stage.

The objectives for the Managing a Stage Boundary process are:

• To assure the Project Board that all products in the Stage are produced and approved.

• If it is a large project you can create Lessons Report from the lessons log. This is optional.

• Create the End Stage Report, to show what has been completed in the current stage compared to the Stage Plan.

• Create the Next Stage Plan.

Corp..

Project mandate

Corporate or Programme Management

www.Mgm tPlaza.com