Process 3 of 7

Initiating a Project

Establish (a solid understanding of) the work that needs to be done.

Objectives

  • Reasons for doing the project; expected benefits and associated risks.
  • Scope and the products to be delivered.
  • How, when and at what cost the products will be delivered?
  • Who will be involved in the project decision making?
  • How the required quality will be delivered?
  • How baselines will be established and controlled?
  • How risks, issues and changes will be identified, assessed and controlled?
  • Who needs information, in what format and at when?
  • How progress will be monitored and controlled?
  • How PRINCE2 will be tailored to suit the project?

Roles and Responsibilities

Corp. Or Prog. Mgmt

Approves and reviews the Benefits Review Plan and Business Case.

Executive

Approves the Benefits Review Plan and Project Initiation Documentation.

Senior User

Approves the Benefits Review Plan and Project Initiation Documentation.

Senior Supplier

Approves the Benefits Review Plan and Project Initiation Documentation.

Project Manager

Create Project Initiation Documentation, Benefits Review Plan and next Stage Plan.

Project Assurance

Reviews the documentation.

Project Support

Assist the PM in creating the Strategy documents.

Applying the Themes

Business Case (Why)

Outline Business Case is upgraded to the detailed Business Case.

Organisation (Who)

Project Management Team and Role descriptions are updated and added to the PID.

Quality (What)

Quality Management Strategy and Quality Register are created.

Plans (How, How much, When)

Project Plan is created.

Risk (What if)

Risk Management Strategy and Risk Register are created.

Change (What is the impact)

Configuration Management Strategy and Issue Register are created.

Progress (Where are we, direction, should we carry on)

Project Controls are determined.