Directing a Project

Directing a Project Process in PRINCE2

Understanding the Directing a Project (DP) Process in PRINCE2

The Directing a Project (DP) process is a crucial component of PRINCE2 methodology that focuses on project governance from the Project Board's perspective. It provides the framework for decision-making at the senior management level throughout a project's lifecycle.

Why is the Directing a Project Process Important?

The DP process is essential because it:

• Establishes clear accountability at the senior management level
• Ensures projects remain viable and aligned with organizational objectives
• Provides a structured approach for key decision points
• Creates a clear interface between corporate management and the project management team
• Enables appropriate delegation while maintaining ultimate accountability

What is the Directing a Project Process?

The DP process represents the Project Board's responsibilities and activities. Unlike other PRINCE2 processes that are managed by the Project Manager, the DP process is conducted by the Project Board. It spans the entire project from initiation to closure and focuses on four key decision points:

1. Starting a project (DP1): Deciding whether to proceed with the project
2. Directing a project (DP2): Providing ongoing direction and control
3. Stage boundaries (DP3): Making decisions at stage transitions
4. Project closure (DP4): Confirming the project can be closed

How the Directing a Project Process Works

The DP process operates through five main activities:

1. DP1: Authorize initiation - The Project Board evaluates the Project Brief and decides whether to commit resources to the initiation stage.

2. DP2: Authorize the project - After reviewing the Project Initiation Documentation (PID), the Board decides whether to proceed with the project.

3. DP3: Authorize a Stage or Exception Plan - At each stage boundary, the Board reviews progress and approves plans for the next stage or considers exception plans if needed.

4. DP4: Give ad hoc direction - Throughout the project, the Board provides guidance, makes decisions on escalated issues, and monitors progress through highlights reports.

5. DP5: Authorize project closure - The Board confirms that project objectives have been met, approves the closure, and ensures proper handover of products.

Exam Tips: Answering Questions on Directing a Project

• Understand the Project Board composition: Remember the three key roles - Executive (responsible for business case), Senior User (represents users), and Senior Supplier (represents those providing resources).

• Know the boundaries of authority: The Project Board makes decisions at key points but delegates day-to-day management to the Project Manager.

• Recognize management by exception: The Project Board sets tolerances and only needs to be involved when these might be exceeded.

• Identify the correct decision points: Questions often focus on when the Project Board should make decisions versus when the Project Manager should handle matters.

• Connect to other processes: Understand how DP interacts with other processes, especially Managing a Stage Boundary (SB) and Controlling a Stage (CS).

• Focus on the four main decisions: Questions often revolve around authorization of initiation, the project itself, stage plans, and project closure.

• Remember what products the Board reviews: Be clear on which management products the Board uses for decision-making (e.g., Project Brief, PID, End Stage Reports, Exception Reports).

When answering exam questions, always consider the perspective of governance and oversight rather than detailed management. The Project Board is concerned with the "what" and "why" rather than the "how" of project activities. They focus on business justification, risk appetite, and major decision points rather than day-to-day project execution.