# Project Initiation and Stakeholder Identification

> Chapter 3 of the Courseiva PROJECT-PLUS curriculum — https://courseiva.com/learn/project-plus/project-initiation-and-stakeholder-identification

**Official objective:** 1.3 — Identify the steps to initiate a project, including the business case, project charter, and stakeholder identification and analysis.

## Introduction

Exam objective 1.3 of the PK0-005 exam centres on how a project gets started the right way. Before any technical work happens, the project's value must be justified, its authorisation must be secured, and every person who can influence or be affected by the outcome must be known. This chapter walks you through those three cornerstone steps, so you understand exactly what an IT project manager does before writing a single line of code.

## The Wedding Planner Analogy

A wedding planner is the person hired by a couple to take their vision of a perfect wedding and turn it into a real event, on time and within budget. The planner does not just start booking venues and caterers. They first gather the couple's ideas, then formalise a high-level plan called a 'wedding scope' - which is like a business case. This document captures the couple's desires (the problem being solved, like 'we want a beach ceremony'), the budget constraints, and what success looks like (e.g., 'guests are happy, no major hiccups').

Once that scope is tentatively approved, the planner creates a 'wedding charter' - a formal authorisation to proceed. This charter names the planner as the project manager, identifies the couple as the primary sponsors, and lays out key milestones like 'book venue by March' and 'send invitations by April'. Without this charter, the planner has no official power to negotiate with vendors or make spending decisions.

Next, the planner identifies every person with a stake in the wedding - not just the couple, but also the parents, the best man, the florist, the venue manager, the caterer, and even the cousin who offered to handle music. For each stakeholder, the planner analyses their influence and interest. The couple's mother might have high influence (she is paying for part of the reception) and high interest (she cares deeply about the menu), so she needs regular, detailed updates. The caterer has high interest in the timeline but low influence over design choices, so they get clear deadlines but not every email. This stakeholder identification and analysis ensures that no critical person is forgotten and that communication is targeted, reducing the risk of last-minute disasters. The entire process - from the initial meeting to the final seating chart - mirrors the project initiation phase in IT, where a vague idea becomes a planned, authorised, and resourced project.

## Core explanation

Project initiation is the very first phase of a project's lifecycle. Think of it as the 'green light' stage. Before any money is spent or any work begins, an organisation must decide whether a project is worth doing. This decision is guided by three key documents and activities: the business case, the project charter, and stakeholder identification and analysis.

The business case is a formal document that answers a single question: 'Why should we do this project?' It describes the problem or opportunity the project addresses, the expected benefits (both financial and non-financial), the estimated costs, a timeline, and a recommended solution. For example, if a company is losing customers because its website is slow, the business case would quantify the lost revenue, estimate the cost of upgrading servers, and show that the upgrade will pay for itself within a year. The business case is developed by someone who wants the project to happen - often a senior manager or a business analyst. It is not a technical document; it is a business justification. A project should not proceed without an approved business case, because the business case proves the project aligns with organisational goals and that the investment is worthwhile.

Once the business case is approved, the next step is to create the project charter. The project charter is the official authorisation to begin the project. It is usually issued by a project sponsor - a senior executive who champions the project and provides funding. The charter formally appoints the project manager and grants them the authority to use organisational resources to execute the project. A typical project charter includes:

- The project's purpose and justification (linking back to the business case)
- High-level requirements and objectives
- The project manager's name and their authority level
- The project sponsor's name
- Key milestones (but not detailed tasks)
- Budget constraints and key resources
- Key assumptions and constraints

The project charter is not a contract, but it is an agreement between the project sponsor and the project manager. It says, in effect, 'I, the sponsor, trust you to lead this work, and I will provide the support you need'. Without a project charter, the project manager has no formal authority to assign work, spend money, or make decisions. In smaller organisations, the charter might be a one-page email; in larger ones, it is a formal signed document.

With the charter signed, the project manager then turns to stakeholder identification and analysis. Stakeholders are any individuals, groups, or organisations who are affected by the project, can affect the project, or think they are affected. Stakeholder identification is the process of listing every possible stakeholder. Analysis is the process of understanding each stakeholder's interest, influence, expectations, and potential impact on the project.

Why is this so important? Because stakeholders can make or break a project. A vocal opponent who was not identified early can delay approval, spread negativity, or even kill the project. Conversely, a strong supporter can unlock resources and smooth the path. The most common way to analyse stakeholders is to use a power-interest grid, where you plot each stakeholder on a matrix with two axes: 'power' (their ability to influence the project) and 'interest' (how much they care about the outcome). This creates four groups:

- High power, high interest: manage closely (e.g., the project sponsor, a key customer)
- High power, low interest: keep satisfied (e.g., the CEO who does not care about details but can stop the project)
- Low power, high interest: keep informed (e.g., end-users who will use the product)
- Low power, low interest: monitor only (e.g., a distant department that is barely affected)

Project initiation as a phase ends when the project charter is signed and stakeholders are identified. It ensures that the project starts with a clear rationale, official permission, and a map of all the human relationships that matter.

## Real-world context

Imagine you work for a mid-sized retail company called 'ShopLocal'. The company has been using an ancient inventory system that runs on a single server in the back office. The CEO has heard that competitors are using cloud-based systems that can handle holiday spikes automatically. She asks you to look into replacing the inventory system. Here is what you, as an IT professional, actually do for project initiation.

First, you need a business case. You interview the warehouse manager, the purchasing director, and the CFO. You gather data: the current system crashes twice a month, costing an estimated 40 hours of rework per crash at £50 per hour. That is £4,000 per month in lost productivity. The new cloud system costs £20,000 per year. You write a one-page business case showing that the project pays for itself in five months. You add non-financial benefits like better reporting and no more manual backups. You present it to the CEO. She approves it in principle, but asks for a clearer timeline. You revise the business case and resubmit. Once she signs off, you have the business case approved.

Next, the CEO issues a project charter. She writes a short document naming you as project manager, stating the project's objective (replace the inventory system by Q3), and authorising you to spend up to £25,000 and to work with the warehouse team. She also names herself as the project sponsor. You keep this charter in your project folder - it is your official badge of authority. Without it, the warehouse manager could refuse to give you time with his team.

Now you start stakeholder identification. You brainstorm a list: the CEO (sponsor), the warehouse manager (high interest, high power - he uses the system daily), the purchasing director (high interest, medium power), the IT support team (low interest, medium power - they will have to maintain the new system), the CFO (low interest, high power - she controls the budget), the vendor you will buy the system from (low interest, low power - but you need them to succeed), and the end-users - the warehouse pickers (high interest, low power - they will use the new interface daily). You create a power-interest grid:

- CEO (sponsor): high power, high interest - manage closely. You send her a brief weekly update.
- Warehouse manager: high power, high interest - manage closely. You meet him weekly to get requirements and feedback.
- Warehouse pickers: high power? Actually, low power but high interest - keep informed. You send them a monthly newsletter about upcoming changes and hold two town-hall meetings.
- CFO: high power, low interest - keep satisfied. You send her a one-line update each month and always copy her on budget-related emails.
- IT support team: low power, low interest - monitor. You send them a brief email after each major decision.

You discover that the warehouse manager is a potential resistor - he has used the old system for twenty years and hates change. You decide to bring him into the planning team early so he feels ownership. This is a direct result of stakeholder analysis: you identified a risk and took action.

Finally, you compile all this into a project initiation document (sometimes called a PID, which is the charter plus the stakeholder register) and file it in the project's shared folder. The project initiation phase is complete. You now move into planning, but you already know exactly who your allies and opponents are, and you have formal permission to proceed.

## Exam focus

The PK0-005 exam loves to test the order and purpose of initiation activities. You will see questions that ask: 'Which document is created first, the business case or the project charter?' The answer is always the business case first, because you need justification before authorisation. Another common question is: 'Who has the authority to assign resources to a project?' The answer is the project manager, but only after the project charter is signed. The exam also tests the distinction between a project manager and a project sponsor. Remember: the sponsor provides funding and high-level support; the manager does the day-to-day work and has authority over resources within the project.

The exam tests stakeholder classification heavily. You will see scenario questions where you are given a list of stakeholders and must decide how to manage them. For example: 'A regulatory body must approve your software release. They have no interest in the project's details, but they can block it. How should you manage them?' The correct answer is 'keep satisfied' (high power, low interest). Never 'manage closely' - that is for high power, high interest. The exam writers deliberately include stakeholders with similar profiles to confuse you.

Here are the specific concepts PK0-005 tests about initiation:

- The Business Case: Its components (problem statement, benefits, costs, timeline, recommendations). A question might ask: 'Which of the following is not part of a business case?' Traps include listing 'project manager's name' (that belongs in the charter) or 'detailed task list' (that belongs in the plan).

- The Project Charter: Its components (purpose, objectives, high-level milestones, budget, sponsor, project manager). They love to ask: 'Which document formally authorises the project?' Answer: The project charter. They also test that the charter includes the authority level of the project manager, not the exact team member assignments.

- Stakeholder Analysis: The power-interest grid. You must memorise the four quadrants and the action for each: manage closely (high-high), keep satisfied (high-low), keep informed (low-high), monitor (low-low). They often present a scenario where a stakeholder has high power but low interest, and you must select the correct management strategy.

- The difference between stakeholder identification (finding all stakeholders) and stakeholder analysis (understanding their needs and influence). The exam will present a scenario and ask: 'What should the project manager do next after identifying stakeholders?' The answer: 'Analyse their power and interest.'

Trap to watch: The exam sometimes uses 'project initiation document' interchangeably with 'project charter' in some contexts, but on the PK0-005, the official term is 'project charter'. Do not confuse it with the 'business case'. Another trap: they might list 'project scope statement' as part of initiation - it is not; scope statement comes in planning. Stick to the three initiation deliverables: business case, charter, stakeholder register (which results from identification and analysis).

## Step by step

1. **Develop the Business Case** — Identify a business problem or opportunity. Quantify the costs, benefits, and risks. Write a formal document that justifies why the project should be undertaken. This step ensures the project aligns with organisational goals and that resources are not wasted on unnecessary work.
2. **Obtain Business Case Approval** — Present the business case to the decision-maker (often a senior manager or steering committee). They review the justification and either approve, reject, or request changes. Approval signals that the project is worth exploring further.
3. **Create and Sign the Project Charter** — The project sponsor drafts and signs a project charter. This document formally authorises the project, names the project manager, states the high-level objectives, and allocates initial budget and resources. This step gives the project manager official authority to proceed.
4. **Identify Stakeholders** — Brainstorm and list every individual or group who may be affected by the project or can influence it. Use techniques like reviewing organisational charts, interviewing experts, and analysing previous projects. This step ensures no critical person is overlooked.
5. **Analyse Stakeholders** — For each stakeholder, assess their power (ability to influence the project) and interest (how much they care about the outcome). Plot them on a power-interest grid. Determine the best communication and management strategy for each (e.g., manage closely, keep satisfied, keep informed, or monitor). This step helps you proactively manage relationships.
6. **Document and Communicate** — Record all stakeholders in a stakeholder register, including their names, roles, power/interest level, and management strategy. Share the project charter with all identified stakeholders. This step ensures everyone knows the project exists and who is responsible for what.

## Comparisons

### Business Case vs Project Charter

**Business Case:**
- Created before the project charter
- Justifies the project's value with costs and benefits
- Often written by a business analyst or sponsor

**Project Charter:**
- Created after the business case is approved
- Formally authorises the project and names the project manager
- Written and signed by the project sponsor

### Project Manager vs Project Sponsor

**Project Manager:**
- Responsible for day-to-day execution and planning
- Has authority over project resources (team, budget) once charter is signed
- Reports to the sponsor on progress

**Project Sponsor:**
- Provides high-level support and funding
- Has authority to approve or reject the business case and charter
- Removes organisational obstacles for the project manager

### Stakeholder Identification vs Stakeholder Analysis

**Stakeholder Identification:**
- Focuses on finding all possible stakeholders
- Happens first in the stakeholder process
- Results in a list of names and roles

**Stakeholder Analysis:**
- Focuses on understanding each stakeholder's power and interest
- Happens after identification
- Results in a management strategy for each stakeholder

### Manage Closely (High Power, High Interest) vs Keep Satisfied (High Power, Low Interest)

**Manage Closely (High Power, High Interest):**
- Includes stakeholders like the project sponsor or key customer
- Requires frequent, detailed updates and active involvement
- Stakeholder has both the power to influence and a strong interest in outcomes

**Keep Satisfied (High Power, Low Interest):**
- Includes stakeholders like a CEO who controls budget but not details
- Requires periodic updates and ensuring their needs are met without overwhelming them
- Stakeholder has power to influence but low interest in daily details

## Diagram

_This flowchart shows the logical sequence of steps in project initiation, from identifying a business problem to completing the initiation phase with a signed charter and stakeholder register._

```mermaid
flowchart TD
    A[Business Problem or Opportunity] --> B[Develop Business Case]
    B --> C{Business Case Approved?}
    C -->|No| D[Project is not initiated]
    C -->|Yes| E[Create Project Charter]
    E --> F[Project Charter Signed by Sponsor]
    F --> G[Identify Stakeholders]
    G --> H[Analyse Stakeholders using Power-Interest Grid]
    H --> I[Stakeholder Register Created]
    I --> J[Project Initiation Complete]
    J --> K[Move to Project Planning]
```

## Common misconceptions

- **Misconception:** The project charter and the business case are the same document. **Reality:** They are distinct. The business case is a justification document that asks for permission to consider the project. The project charter is the formal authorisation to start the project. One precedes the other. (Beginners see both documents as just paperwork and assume they are interchangeable. But the exam tests their sequence and purpose separately.)
- **Misconception:** Stakeholder identification happens once at the start and is never revisited. **Reality:** Stakeholder identification is an iterative process. New stakeholders can appear as the project progresses, and existing stakeholders can change their influence or interest. (Many beginners think a project is static. In reality, people join teams, regulations change, and new departments become involved.)
- **Misconception:** Only people inside the company who work on the project are stakeholders. **Reality:** Stakeholders include anyone affected by the project, whether inside or outside the organisation. This includes vendors, regulators, customers, and even the general public in some cases. (Beginners often default to thinking 'stakeholder = team member'. But a customer who will use the final product is a stakeholder, even if they never attend a meeting.)
- **Misconception:** The project manager creates the business case. **Reality:** The business case is usually created by a business analyst, a senior manager, or the project sponsor. The project manager is typically not involved until the charter is signed. (It seems logical that the person who will run the project would write the justification. But in practice, the business case is a strategic document that requires business knowledge, not project management skills.)
- **Misconception:** The project charter must be long and formal to be valid. **Reality:** A project charter can be as short as a one-page email or a signed memo. Its validity comes from the sponsor's authority, not its length or format. (Beginners often overestimate formality. In many organisations, approval happens informally, but the exam recognises that any written authorisation from a sponsor counts.)

## Key takeaways

- The business case justifies a project's value and must be approved before the project charter is created.
- The project charter formally authorises the project and names the project manager, giving them authority to use resources.
- A stakeholder is any person or group who can affect or be affected by the project, including both supporters and opponents.
- Stakeholder analysis uses a power-interest grid to classify stakeholders into four management strategies: manage closely, keep satisfied, keep informed, and monitor.
- Project initiation ends when the project charter is signed and stakeholders are identified and analysed.
- The project sponsor provides funding and high-level support, while the project manager handles day-to-day execution and has authority over project resources.
- Stakeholder identification is an ongoing process throughout the project lifecycle, not a one-time activity.
- Without a signed project charter, a project manager has no official authority to assign work or spend budget.

## FAQ

**What is the difference between a business case and a project charter?**

A business case justifies why a project should be done (cost-benefit analysis). A project charter is the formal approval to start the project and authorises the project manager to use resources.

**Who creates the project charter?**

The project charter is created and signed by the project sponsor, who is a senior executive with authority to allocate funding and resources.

**Do I need to identify stakeholders more than once?**

Yes. Stakeholder identification is an ongoing process. New stakeholders can appear during the project, and existing stakeholders can change their influence or interest.

**What is a stakeholder register?**

A stakeholder register is a document that lists all identified stakeholders, their roles, their power/interest level, and the planned management strategy for each.

**Can a project start without a project charter?**

Technically, informal work might happen, but officially a project should not start without a charter. Without it, the project manager has no authority to spend money or assign work.

**What is the power-interest grid?**

It is a tool used in stakeholder analysis to classify stakeholders based on their power to influence the project and their interest in its outcome. It helps decide how to manage each stakeholder group.

## Check your understanding

1. **Which document must be approved before a project charter can be created?**

   Answer: The business case must be approved first, as it justifies the project's value and need.

2. **What is the primary purpose of a project charter?**

   Answer: To formally authorise the project and give the project manager the authority to use organisational resources.

3. **In stakeholder analysis, what management strategy should be used for a stakeholder with high power and low interest?**

   Answer: Keep satisfied. This stakeholder can influence the project but does not care about daily details, so periodic updates are sufficient.

4. **Who issues and signs the project charter?**

   Answer: The project sponsor, a senior executive who provides funding and support for the project.

5. **What is the difference between stakeholder identification and stakeholder analysis?**

   Answer: Stakeholder identification is the process of listing all potential stakeholders. Stakeholder analysis is the process of evaluating their power, interest, and influence to determine how to manage them.

---

Interactive version with quiz and diagrams: https://courseiva.com/learn/project-plus/project-initiation-and-stakeholder-identification