PRINCE2 Foundation v7 Initiating a Project

Initiating a Project (IP) is where PRINCE2 turns a viable project idea into a properly governed project. Foundation questions often test whether you recognize that this is the process for establishing the main control baseline, not just doing more vague planning.

What to understand

The key product here is the Project Initiation Documentation (PID), which brings together how the project will be controlled. The process also strengthens the Business Case, planning, roles, approaches, and reporting arrangements so the board can authorize the project with confidence.

The stronger answer usually recognizes that IP is about creating a managed project environment. It is more than scheduling. It is about making governance possible.

Example

If a board asks for clearer control over risks, reporting, quality, and scope before approving full project delivery, those needs point toward Initiating a Project and the PID.

Common pitfalls

• Treating IP as just a bigger version of Starting up a Project.
• Assuming control baselines already exist before initiation is complete.
• Forgetting that the PID is about integrated control, not only one plan.
• Confusing authorization to initiate with authorization of the full project.

Sample Exam Question

Which PRINCE2 process is most closely associated with creating the PID and establishing the project control baseline?

A. Starting up a Project B. Initiating a Project C. Managing a Stage Boundary D. Managing Product Delivery

Best answer: B

Why: Initiating a Project creates the PID and establishes the controlled basis for project authorization and management.

Why the others are weaker: A is earlier and lighter-touch, C is for later stage review, and D is delivery-focused.