6.4 Initiating a Project (IP) Process

6.4 Initiating a Project (IP) Process

The Initiating a Project (IP) process is executed during the first management stage of the project—officially designated as the Initiation Stage. The primary objective of IP is to establish solid foundations for the project, enabling the organization to gain a comprehensive understanding of the work required to deliver the project's deliverables before committing significant financial investment.

While Starting Up a Project (SU) acts as a rapid, low-cost pre-project filter, Initiating a Project (IP) is an in-depth planning and setup process. IP takes the high-level concepts from the Project Brief and transforms them into a fully baselined, rigorous blueprint for execution: the Project Initiation Documentation (PID).

---

Purpose and Core Objectives of the IP Process

Initiating a Project aims to answer six fundamental governance questions:

1. What is the project trying to achieve, and what specific specialist products will be delivered?
2. Why is the project justified, and what business benefits will justify the investment?
3. How will the project deliverables be produced, tested, and quality-assured?
4. Who will be involved in decision-making, management, delivery, and stakeholder communication?
5. When will the work be executed, and how are management stages and milestones structured?
6. How will risk, quality, change, communication, sustainability, and data be governed across the project lifecycle?

---

Step-by-Step Activities of the Initiating a Project Process

During the Initiation Stage, the Project Manager leads the project management team through six core activities to build the project foundation:

+-----------------------------------------------------------------------------------+
| 1. Agree Management Approaches (Risk, Quality, Change, Comm, Sust, Data)          |
+-----------------------------------------------------------------------------------+
                                          |
                                          v
+-----------------------------------------------------------------------------------+
| 2. Establish Project Controls (Tolerances, Boundaries, Reporting, Escalation)     |
+-----------------------------------------------------------------------------------+
                                          |
                                          v
+-----------------------------------------------------------------------------------+
| 3. Create the Project Plan (Product-Based Planning, Schedule, Resources)          |
+-----------------------------------------------------------------------------------+
                                          |
                                          v
+-----------------------------------------------------------------------------------+
| 4. Refine the Business Case (Detailed Financial ROI, Benefits & Risk Rationale)   |
+-----------------------------------------------------------------------------------+
                                          |
                                          v
+-----------------------------------------------------------------------------------+
| 5. Prepare Benefits Management Approach (Metrics, Timeline, User Accountability)  |
+-----------------------------------------------------------------------------------+
                                          |
                                          v
+-----------------------------------------------------------------------------------+
| 6. Assemble the Project Initiation Documentation (PID)                             |
+-----------------------------------------------------------------------------------+

1. Agree the Management Approaches

The Project Manager collaborates with stakeholders to establish six standardized Management Approaches. These documents define how specific management practices will be executed throughout the project:

• Quality Management Approach: Defines the quality standards, inspection techniques, Quality Reviews, acceptance criteria, and responsibilities for product verification.
• Risk Management Approach: Defines the risk management procedure, risk identification techniques, risk categories, probability/impact scoring matrices, risk registers, and risk tolerance thresholds.
• Change Control Approach: Details how changes, issue reports, and product baselines will be requested, evaluated, authorized, and tracked, specifying Change Authority roles and change budget limits.
• Communication Management Approach: Defines stakeholder information requirements, communication channels, reporting types and frequencies, and stakeholder engagement strategies.
• Sustainability Management Approach (PRINCE2 7 Focus): Establishes explicit environmental, social, and economic sustainability targets, monitoring metrics, carbon offset policies, and compliance procedures.
• Data Management Approach (PRINCE2 7 Focus): Details how digital project data, information assets, documentation versions, security protocols, and project management information systems (PMIS) will be managed.

2. Establish Project Controls

The Project Manager defines the mechanics for exercising control throughout the project. This includes setting stage boundary mechanisms, defining tolerance thresholds across the seven performance aspects (cost, time, quality, scope, risk, benefit, sustainability), establishing reporting frequencies (Highlight Reports, Checkpoint Reports), and defining formal escalation routes for exceptions.

3. Create the Project Plan

Using PRINCE2 Product-Based Planning techniques, the Project Manager drafts the comprehensive master Project Plan. This activity involves:

• Defining the Project Product Description and establishing user acceptance criteria.
• Creating the Product Breakdown Structure (PBS) to decompose the overall project scope into specialist products.
• Writing Product Descriptions for key deliverables.
• Estimating work effort, activity schedules, dependencies, and resource allocations.
• Dividing the project schedule into manageable management stages.

4. Refine the Business Case

The preliminary Outline Business Case created during pre-project startup is expanded into a detailed, baselined Business Case. The PM incorporates refined cost estimates from the Project Plan, quantifies financial return on investment (ROI), aligns expected strategic outcomes, and evaluates major business risk exposures to establish firm business justification.

5. Prepare the Benefits Management Approach

The PM, working closely with the Executive and Senior User, creates a standalone document detailing how and when project benefits will be measured and realized. It assigns explicit benefit ownership to Senior Users and operational managers.

6. Assemble the Project Initiation Documentation (PID)

In the final activity of IP, the Project Manager compiles all planning outputs, management approaches, baseline controls, team structures, and tailoring strategies into a unified reference document: the Project Initiation Documentation (PID). The PID is submitted to the Project Board for authorization during the Directing a Project (DP) process.

---

Deep Dive: The Benefits Management Approach & Realization Lifecycle

PRINCE2 7 places strong emphasis on ensuring projects deliver measurable organizational value. Deliverables (outputs) are created so that users can achieve outcomes, which in turn generate benefits.

+---------------+      +------------------+      +-------------------+      +------------------+
| Specialist    | ---> | Operational      | ---> | Measurable        | ---> | Corporate /      |
| Product       |      | Outcome          |      | Benefit           |      | Strategic Target |
| (e.g. CRM Sys)|      | (e.g. Faster CS) |      | (e.g. +15% Sales) |      | (e.g. Market Lead|
+---------------+      +------------------+      +-------------------+      +------------------+

Essential Elements of the Benefits Management Approach

• Target Benefit Definitions: Clear, non-ambiguous statements describing expected improvements.
• Key Performance Indicators (KPIs): Precise quantitative measures used to evaluate benefit achievement.
• Baseline Metrics: Objective pre-project measurements against which post-project performance is evaluated.
• Realization Timeline: Specifies whether benefits will be realized during the project (e.g., early phase rollout) or post-project during operational business-as-usual (BAU).
• Benefit Owner Accountability: Designated Senior User or operational line manager accountable for realizing each specified benefit after project handover.

---

Master Comparison: Starting Up a Project (SU) vs. Initiating a Project (IP)

Understanding the distinctions between SU and IP is vital for passing the PRINCE2 7 Foundation examination:

---

Governance Summary of IP Management Products

---

Tailoring Initiating a Project Across Project Contexts

The IP process must be adapted depending on project environment and scale:

• Agile / Iterative Contexts: In an agile project, IP is used to establish the overall vision, governance guardrails, release roadmap, and initial product backlog. Rather than producing fixed scope schedules, the Project Plan defines fixed stage timeboxes and team velocity targets, while scope flexibility is managed through prioritized backlog refinement.
• Simple / Low-Risk Projects: For small projects, the six management approaches can be summarized in single-paragraph sections within a streamlined PID, reducing documentation overhead while maintaining formal governance.
• Commercial / Multi-Organization Projects: When external contractors are involved, IP includes defining commercial contracts, procurement management approaches, customer-supplier communication rules, and legal baseline controls.

---

Key Exam Traps & Core Takeaways for IP

• Trap 1: Believing Initiating a Project is a pre-project activity. False! Starting Up a Project (SU) is pre-project; Initiating a Project (IP) takes place inside Stage 1 (the Initiation Stage).
• Trap 2: Assuming the Benefits Management Approach is part of the PID. False! In PRINCE2 7, the Benefits Management Approach is created during IP as a standalone management product because its lifecycle extends beyond the project end date into operational BAU.
• Trap 3: Thinking product work begins during IP. False! Only initiation and planning activities take place during IP. Specialist product delivery begins in Stage 2 after the Board Authorizes the Project.
• Trap 4: Missing the 2 new Management Approaches in PRINCE2 7. Remember that PRINCE2 7 explicitly requires the Sustainability Management Approach and Data Management Approach alongside Quality, Risk, Change, and Communication.