Project Initiation & Stakeholder Engagement
Initiation is where projects are formally born. The Project Charter authorizes the project, the Business Case justifies it, and stakeholder identification sets the foundation for every decision that follows.
Golden Rule: The Project Charter must be issued BEFORE a project manager can formally commit organizational resources. No charter = no authority. Stakeholders must be identified as early as possible — those missed at initiation are the ones who derail projects at execution.
Formally authorizes the project and grants the PM the authority to apply organizational resources. Issued by the project sponsor or initiating entity. It is the PM's "license to operate."
Justifies the project using financial analysis (NPV, IRR, Payback, BCR) and strategic alignment. Created before the charter — it's the "why we should do this project" document.
Identifies all individuals, groups, and organizations that can affect or be affected by the project. Created during initiation and updated continuously. Negative stakeholders are included too.
| Document | Created By | Purpose | Key Contents |
|---|---|---|---|
| Business Case | Business Analyst / Sponsor | Justify the investment | Financial analysis, strategic alignment, options considered |
| Benefits Management Plan | PM + Sponsor | Define how benefits will be realized | Target benefits, timeframe, metrics, benefit owner |
| Project Charter | Sponsor / PMO | Formally authorize the project | Purpose, objectives, PM authority, high-level milestones, budget |
| Stakeholder Register | PM | Document all stakeholders | Name, role, interest, influence, current/desired engagement level |
| Assumption Log | PM | Track project assumptions | Assumption, impact if wrong, owner, review date |
Organizational Process Assets (OPAs): Things your organization OWNS — templates, historical data, lessons learned, policies. Internal, controllable inputs.
Enterprise Environmental Factors (EEFs): Conditions you must WORK WITHIN — government regulations, market conditions, org culture, competitor landscape. External or uncontrollable inputs.
Exam tip: EEFs constrain the PM; OPAs enable the PM.
Marks the formal start of project execution (not initiation). The kickoff meeting aligns the team and key stakeholders on project objectives, roles, approach, and communication expectations.
Common exam trap: Some candidates confuse the kickoff with the charter signing. The charter authorizes the project; the kickoff starts the work.
Project Initiation & Business Justification
Projects are selected based on business value. The PMP exam tests your ability to compare projects using financial metrics and understand what a complete Project Charter contains.
What the Project Charter Contains
Who creates the charter? The PROJECT SPONSOR (or sponsoring entity / PMO). The PM may assist in drafting it but does NOT create it unilaterally. The charter cannot be issued by the PM for their own project.
Project Selection Methods
📊 Project Selection Worked Example — 3 Options
Opportunity cost is the value of the BEST ALTERNATIVE FORGONE — not the sum of all alternatives, not the difference. If you choose Project Beta ($320K NPV) over Project Alpha ($180K NPV), the opportunity cost is $180,000 — the value you gave up by not selecting Alpha.
The exam will try to trick you into answering $140K (the NPV difference) or $500K (the sum). The correct answer is always the value of the next-best option you didn't choose.
Stakeholder Identification & Analysis
You cannot manage what you haven't identified. Stakeholder analysis begins at project initiation and continues throughout. Three key tools: the Stakeholder Register, Power/Interest Grid, and Salience Model.
Who is a stakeholder? Anyone who can affect or be affected by the project — including those with negative interests. Failing to identify resistant or negative stakeholders early is a top cause of project failure on the exam.
Stakeholder Register — Sample Structure
| Name / Group | Role | Interest Area | Power | Current Engagement | Desired Engagement |
|---|---|---|---|---|---|
| Sarah Chen | Project Sponsor | ROI, timeline | High | Supportive | Leading |
| IT Operations Team | Internal User | System stability | Medium | Resistant | Neutral |
| Regulatory Body | External Regulator | Compliance | High | Unaware | Supportive |
| End Users (300+) | Customer Group | Usability, features | Low | Neutral | Supportive |
| Competing Dept. | Negative Stakeholder | Budget reallocation | Medium | Resistant | Neutral |
Power/Interest Grid — The 4 Engagement Strategies
Salience Model — Beyond Power and Interest
(Authority)
(Valid Claim)
(Time Sensitive)
| Tool | Dimensions | Best Used For | Output |
|---|---|---|---|
| Power/Interest Grid | Power vs. Interest | Determining communication frequency and depth | 4-quadrant engagement strategy |
| Power/Influence Grid | Power vs. Influence | Larger programs where active involvement varies | 4-quadrant strategy (similar to P/I) |
| Influence/Impact Grid | Influence vs. Impact | Identifying who drives change vs. who is affected | Prioritized engagement plan |
| Salience Model | Power + Legitimacy + Urgency | Complex multi-stakeholder environments | Stakeholder priority classification |
| Stakeholder Cube | Power + Interest + Attitude | 3D view across complex stakeholder landscapes | Multi-dimensional engagement priorities |
Stakeholder Engagement Strategies
Identifying stakeholders is not enough — you must move them toward active support. The Stakeholder Engagement Assessment Matrix tracks where each stakeholder IS (current) vs. where they NEED TO BE (desired).
Stakeholder Engagement Assessment Matrix
| Stakeholder | Unaware | Resistant | Neutral | Supportive | Leading | Action Needed? |
|---|---|---|---|---|---|---|
| Exec Sponsor | C | D | Yes — increase engagement | |||
| IT Operations Lead | C | D | Yes — address resistance | |||
| Project PMO | C D | No — aligned |
When C = D, no corrective engagement action is needed. When C ≠ D, develop targeted strategies to close the gap.
Understand root cause first: Resistance is usually fear (of change, job loss, loss of power) or lack of information. Diagnose before acting.
Engage, don't avoid: The PMP exam almost always rewards proactive engagement over avoidance. Escalation to the sponsor is a last resort, not a first response.
Involve them early: Including resistant stakeholders in planning often converts resistance into ownership — people support what they help create.
Stakeholder Engagement Plan: Defines strategies and actions needed to move each stakeholder from their current to desired engagement level. Part of the Project Management Plan.
Tailored communication: Different stakeholders need different messages, channels, and frequencies. Executives want summaries; technical teams want detail.
Reassess continuously: Stakeholder interests and power can shift during the project. Update the register and engagement plan regularly.
| Scenario | Correct Action | Wrong Action |
|---|---|---|
| Stakeholder is newly resistant mid-project | Meet with them to understand concerns; update engagement plan | Ignore them; report to sponsor immediately |
| Stakeholder not identified at project start | Add to register immediately; assess impact; engage proactively | Ignore since project is already in execution |
| Two stakeholders have conflicting requirements | Facilitate a meeting; use MoSCoW or priority analysis; escalate if unresolved | Pick one side without consulting both parties |
| Powerful stakeholder wants undocumented scope changes | Acknowledge, document the request, route through change control | Implement immediately to satisfy the powerful stakeholder |
Communications Management
The PMP exam heavily tests communications — especially the channels formula, communication types, and when to use formal vs. informal approaches. A PM spends ~90% of their time communicating.
📡 Communication Channels Formula
Interactive: Real-time, two-way exchange. Most effective for complex topics. Examples: meetings, phone calls, video calls.
Push: Information sent to recipients without a response expected. Examples: email, memos, project reports, letters.
Pull: Recipients access information on demand. Examples: intranet portals, document repositories, lessons learned databases.
Exam tip: For complex, sensitive, or critical issues — always choose Interactive. Push = FYI. Pull = self-serve.
Formal Written: Contracts, project plans, status reports, RFPs, legal documentation. Required for important decisions and scope changes.
Formal Verbal: Presentations, structured meetings, kickoff sessions. Official but spoken.
Informal Written: Email, texts, instant messages. Good for quick updates but not for binding agreements.
Informal Verbal: Hallway conversations, casual check-ins. Builds relationships but must be followed up in writing for anything decision-critical.
The Communications Management Plan defines: WHO needs what information, WHEN they need it, in WHAT FORMAT, through WHAT CHANNEL, and from WHOM. It also specifies escalation paths and issue resolution procedures.
| Stakeholder / Group | Information Needed | Frequency | Format | Channel | Owner |
|---|---|---|---|---|---|
| Project Sponsor | Project status, risks, decisions | Bi-weekly | Executive summary | Email + meeting | PM |
| Steering Committee | Milestone progress, financials | Monthly | Dashboard report | Formal presentation | PM |
| Project Team | Tasks, blockers, sprint goals | Daily / weekly | Meeting notes | Standup / team chat | Team Lead |
| External Regulator | Compliance milestones | Per requirement | Formal letter | Official submission | PM + Legal |
Noise: Anything that distorts the message — physical distractions, jargon, emotional state, cultural differences.
Sender / Receiver Model: Message → Encode → Channel → Decode → Feedback. Breakdowns occur at any stage.
Cultural differences: Especially important in global projects — body language, directness norms, and formality vary widely.
Agile teams favor face-to-face, high-bandwidth communication (Manifesto Principle 6). The Daily Scrum, Sprint Review, and Sprint Retrospective are structured communication events replacing many traditional written status reports.
Information radiators (big visible charts, Kanban boards) make project status continuously visible without requiring formal reporting.
Practice Quiz — Project Initiation & Stakeholder Engagement
10 PMP-style scenario questions. Select your answer to see instant feedback and explanation.
Review explanations above for any missed questions.
Memory Hooks & AI Advisor
Visual anchors and mnemonics for the highest-tested initiation and stakeholder concepts. Use the Advisor for focused exam guidance by category.
Flashcards
Click each card to flip and reveal the answer.
Who creates the Project Charter, and what does it formally authorize?
Created by the Sponsor / initiating entity. Formally authorizes the project and grants the PM authority to use organizational resources
What does NPV > 0 mean, and which selection method is most comprehensive?
NPV > 0 = project creates value, accept it. NPV is the most comprehensive method as it accounts for time value of money across all cash flows
What are the 4 engagement strategies and their corresponding quadrants?
High/High = Manage Closely; High/Low = Keep Satisfied; Low/High = Keep Informed; Low/Low = Monitor
A team grows from 8 to 10 members. How many new communication channels are added?
8 members: 8×7÷2 = 28 channels. 10 members: 10×9÷2 = 45 channels. New channels = 45 − 28 = 17 new channels
What are the 5 engagement levels in order from least to most engaged?
Unaware → Resistant → Neutral → Supportive → Leading. When current = desired, no action needed. Gap = develop engagement strategies
What is the key difference between EEFs and OPAs?
EEFs = external conditions the team must work within (regulations, market, culture). OPAs = internal assets the org owns (templates, processes, historical data)
What 3 attributes does the Salience Model use, and what is a "Definitive Stakeholder"?
Power, Legitimacy, and Urgency. A Definitive Stakeholder possesses all 3 attributes and requires immediate, highest-priority attention from the PM
Your org chose Project A ($150K NPV) over Project B ($220K NPV). What is the opportunity cost?
$220,000 — the value of the best alternative forgone (Project B). Not the $70K difference; not the $370K sum. Always the value of what you gave up
AI Advisor
Select a category for focused exam guidance.
Project Charter & Authorization
- Charter is the PM's license: Without a signed charter, a PM has no formal authority to spend money, assign resources, or make binding decisions. The charter precedes all planning.
- Sponsor creates it: The charter is issued by the project sponsor or sponsoring entity — not by the PM. The PM may help draft it but cannot self-authorize.
- High-level only: The charter contains high-level milestones, budget, and requirements — NOT detailed schedules or full scope definitions. Those come in the planning phase.
- Charter vs Business Case: The business case PRECEDES the charter — it justifies why the project should be selected. The charter authorizes the selected project to proceed.
- OPAs & EEFs as inputs: Both feed into the charter development process. EEFs provide the external context; OPAs provide templates and historical data.
- Kickoff misconception: The kickoff meeting starts EXECUTION, not initiation. The charter signed = project authorized; kickoff = team begins working.
- Assumption Log: Created alongside the charter to document all assumptions made at initiation — key exam input/output to know.
Stakeholder Identification
- Identify ALL stakeholders early: Including those with negative interests, opposition groups, and indirectly affected parties. Missed stakeholders are the #1 cause of late-project disruption.
- Stakeholder Register = WHO they are: Documents each stakeholder's name, role, interests, influence, power, current engagement level, and desired engagement level.
- Stakeholder Engagement Plan = HOW you'll engage: The separate plan that describes strategies for moving stakeholders from current to desired engagement levels.
- Power/Interest Grid exam rule: High Power + High Interest = Manage Closely (maximum effort). High Power + Low Interest = Keep Satisfied. Low Power + High Interest = Keep Informed. Low/Low = Monitor.
- Salience Model — PLU: Power + Legitimacy + Urgency. Only stakeholders with all 3 attributes are Definitive. Two attributes = Expectant. One = Latent.
- Register is living: Update the Stakeholder Register continuously throughout the project — new stakeholders emerge, existing ones change interest levels.
- Negative stakeholders matter: The exam will test scenarios with opponents or resistors. Correct answer is almost always: identify, understand, engage — not ignore or remove.
Stakeholder Engagement
- Engagement Matrix tracks gaps: Compare C (current) to D (desired) for each stakeholder. If C = D, maintain current approach. If C ≠ D, develop targeted strategies.
- Resistance root causes: Fear of job loss, lack of information, competing priorities, past bad experiences. Diagnose before prescribing. Direct conversation first.
- Escalation is last resort: PMP exam almost always rewards PM-level resolution before escalating to sponsor. Only escalate when PM-level action is genuinely insufficient.
- Involve resistors in planning: Co-creation builds ownership. Resistors who help design the solution become supporters. This is a classic exam answer.
- Engagement Plan is confidential: The Stakeholder Engagement Plan may contain sensitive information about stakeholder concerns and should not be shared openly with all stakeholders.
- Tailored communication: Different stakeholders need different messages, detail levels, and channels. One-size-fits-all communication is a common project mistake.
- Continuously reassess: A stakeholder who was supportive at project start can become resistant mid-project. Regularly review and update engagement strategies.
Communications Management
- PM spends ~90% of time communicating: This statistic is frequently tested. Communication is the PM's primary tool for managing stakeholders and teams.
- Channels formula: n(n−1)/2: Always calculate both before and after the team change to find NEW channels added. Adding 1 person to a team of n adds exactly n new channels.
- Interactive > Push > Pull for critical issues: For complex, sensitive, or high-stakes communication, choose the most interactive method (meeting, call). Push (email) for status. Pull (portal) for reference information.
- Formal written = legally binding: Contracts, change requests, issue escalations, and scope decisions must always be documented in writing. "Verbal agreement" is not sufficient for project management purposes.
- Communications Management Plan answers who/what/when/how: It defines each stakeholder's information needs, the format, frequency, channel, and responsible party.
- Sender-receiver model: Message → Encode → Transmit → Receive → Decode → Feedback. Noise can disrupt at any stage. PM is responsible for ensuring the message was received AND understood.
- Information radiators (agile): Big visible charts, Kanban boards, and dashboards replace many formal status reports by making status continuously visible to all team members.
Project Selection & Business Case
- NPV is most comprehensive: It accounts for time value of money AND all project cash flows. Higher NPV = more value created. NPV > 0 = accept. If forced to choose one method, NPV is preferred.
- IRR vs hurdle rate: Compare IRR to the organization's required rate of return (hurdle rate or cost of capital). IRR > hurdle rate = accept. Between projects, higher IRR wins.
- Payback ignores time value: Payback Period is simple but flawed — it doesn't account for the time value of money or cash flows after the payback point. Use as a screening tool, not a final decision.
- BCR rule: > 1 = accept: BCR = PV(Benefits) ÷ PV(Costs). BCR of 1.4 means $1.40 returned per $1 invested. BCR < 1 = reject always.
- Opportunity cost = best alternative forgone: The classic trap is choosing the difference or the sum. The correct answer is always the NPV (or value) of the BEST project you did NOT select.
- Business case precedes charter: The sequence is: Business Case (justify) → Benefits Management Plan (define expected benefits) → Project Charter (authorize). Don't confuse the ordering.
- Benefits Realization: Some benefits are realized AFTER project completion (post-launch). The Benefits Management Plan defines who is responsible for tracking and realizing benefits over time.
Ready to Test Your Knowledge?
Practice with full-length PMP exam simulations on FlashGenius — timed, scored, and mapped to exam domains.
Unlock Full Practice Tests on FlashGenius →