SkarpChapter 4 of 20
Stakeholders, Stakeholder Register, and Risk Register Essentials
Dive into the people and uncertainties that shape every project: who your stakeholders are, how to document them, and how to systematically capture and track risks.
1. Why Stakeholders and Risks Matter (Link to Earlier Modules)
Connecting to What You Know
A project is "A temporary endeavor undertaken to create a unique product, service, or result." Here we focus on two success factors: people (stakeholders) and uncertainties (risks).
Life Cycles and Documentation
In a predictive life cycle, scope, time, and cost are set early, so stakeholder and risk registers are often detailed from the start. In adaptive life cycles, these lists are lighter and updated more frequently.
Why This Matters for CAPM
For CAPM, you must know the official stakeholder definition, what goes into stakeholder and risk registers, and how they support engagement and risk management across the project life cycle.
Mental Picture
Keep this picture: the stakeholder register captures who and what they care about; the risk register captures what might happen (good or bad) and what you plan to do about it.
2. Canonical Definition of a Stakeholder (Know This Cold)
Memorize This Definition
A stakeholder is: "An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio."
Three Ways They Relate
Stakeholders may affect the project, be affected by it, or perceive themselves to be affected. That last phrase is a frequent exam trap.
Not Just Individuals
Stakeholders can be individuals, groups, or organizations: end users, departments, regulators, suppliers, communities, even entire companies.
Exam Traps
Wrong options often omit "perceive itself to be affected" or only mention internal people. Any such shortened definition is not PMI-correct.
3. Stakeholder Register: Purpose and Typical Contents
What Is the Stakeholder Register?
It is a structured list of all identified stakeholders, capturing key details to support analysis and engagement planning. It is updated whenever stakeholders or attitudes change.
Identification Data
Typical fields: name, role, organization, contact details, internal vs external, and location/time zone. This anchors who the stakeholder is.
Classification and Attitude
You record power, interest, influence or impact, and attitude (supportive, neutral, resistant). This helps you prioritize and tailor engagement.
Expectations and Engagement Info
You capture what they want, their success criteria, constraints, preferred communication channels and frequency, and current vs desired engagement level.
4. Risk Register: Purpose and Typical Contents
What Is the Risk Register?
It is the central log of project risks, recording descriptions, analysis, owners, and agreed response strategies, and supporting ongoing risk monitoring.
What Is a Risk?
A risk is an uncertain event or condition that, if it occurs, has a positive or negative effect on project objectives. Positive risks are opportunities; negative risks are threats.
Core Fields
Typical fields: risk ID, description, category, probability, impact, risk score, owner, related stakeholders, response strategy, and status/history.
Exam Signal Words
If a scenario mentions risk IDs plus probability, impact, owner, and responses, the correct artifact is the risk register, not issue log or lessons learned.
5. Example: Building Simple Stakeholder and Risk Registers
Scenario
You manage a project to implement an online appointment system for a university health center. Let’s sketch stakeholder and risk register entries.
Stakeholder Example: Dr. Lee
Dr. Lee, Medical Director: high power, high interest, supportive. Expects minimal disruption and strong data privacy. Wants weekly emails and monthly review meetings.
Stakeholder Example: IT Security Officer
IT Security Officer: medium–high power, medium interest, cautious. Expects compliance with security and privacy rules. Needs early design input and review checkpoints.
Risk Example: Integration Failure
Risk: integration with student system fails, causing double bookings. Technical, medium probability, high impact. Owner: lead dev. Response: early tests and manual fallback.
Risk Example: High Adoption Opportunity
Risk (opportunity): higher-than-expected adoption could justify telehealth funding. Business category, medium probability, high impact. Response: design for extensibility and prep business case.
6. Identifying Stakeholders: Step-by-Step + Power–Interest Grid
Stakeholder Identification Is Ongoing
You start by reviewing the charter, business case, contracts, and requirements, then brainstorm with the team and consult org charts and past projects.
Talk to Key People
Interview the sponsor, product owner/manager, functional managers, PMO, and operations. Ask who uses, funds, can stop, or is impacted by the project.
Document and Update
Record stakeholders in the register with initial classifications. Keep updating as scope or context changes and new stakeholders appear.
Power–Interest Grid Basics
Plot stakeholders by power (influence) and interest (concern). This helps you prioritize engagement and choose communication approaches.
Four Quadrants and Strategies
High power/high interest: manage closely. High power/low interest: keep satisfied. Low power/high interest: keep informed. Low power/low interest: monitor.
7. Stakeholder Engagement Strategies and Communication Design
From Analysis to Action
After classifying stakeholders by power, interest, and attitude, you design engagement strategies and communications that fit their influence and concerns.
Typical Strategies
High power/supportive: collaborate closely. High power/resistant: address resistance. Low power/supportive: leverage advocacy. Low power/resistant: monitor and inform.
Designing Communications
Executives need high-level status and risk summaries; technical teams need detailed tasks. Choose formats and frequencies that match each stakeholder.
Transparency vs Confidentiality
Share enough information to build trust and enable decisions, but protect sensitive data and respect governance rules and legal constraints.
Adjusting the Plan
If a powerful stakeholder turns resistant, update the stakeholder register and engagement plan, and address concerns proactively rather than ignoring them.
8. Risk Management Basics: From Identification to Reserves
Risk Management Flow
Risk management cycles through identifying risks, qualitatively analyzing them, planning responses, implementing those responses, and monitoring and updating.
Risk Register’s Role
Each identified risk goes into the risk register with description and category, then gains probability, impact, owners, response strategies, and status over time.
Contingency vs Management Reserve
Contingency reserve covers identified risks and is included in the cost baseline. Management reserve covers unknown-unknowns and sits outside the baseline.
Cost Baseline and Budget
The cost baseline is a time-phased budget for cost control. Adding management reserve to the cost baseline gives the total project budget.
Exam Tip
If asked which reserve is in the cost baseline, choose contingency reserve. Management reserve is only in the total project budget, not the baseline.
9. Thought Exercise: Classify Stakeholders and Risks
Work through this scenario mentally and, if possible, jot down your answers.
Scenario
You are the project manager for a campus-wide Wi‑Fi upgrade.
Stakeholders:
- Chief Information Officer (CIO)
- Approves the budget and final go-live.
- Very busy, only wants key highlights.
- Students
- Heavy users of Wi‑Fi for study and entertainment.
- Very vocal on social media when unhappy.
- Network Vendor
- Supplies equipment and technical support.
- Facilities Department
- Manages building access and construction work.
Risks:
A. Old building walls block signals more than expected, requiring extra access points.
B. Successful upgrade enables new digital services that increase student satisfaction scores.
Your tasks
- For each stakeholder, decide:
- Power: High / Medium / Low
- Interest: High / Medium / Low
- Likely quadrant on the power–interest grid (manage closely, keep satisfied, keep informed, monitor).
- For each risk:
- Is it a threat or an opportunity?
- Suggest a brief response strategy (mitigate, exploit, etc.).
Reflect
- Which stakeholders would you put into your stakeholder register first, and why?
- Which risk would most affect your cost baseline, and how might that influence your contingency reserve?
There is no single perfect answer, but thinking this through builds the pattern recognition you need for scenario-based CAPM questions.
10. Quick Check: Stakeholder and Risk Fundamentals
Test your understanding of core definitions and artifacts.
Which statement best describes the difference between a stakeholder register and a risk register?
- The stakeholder register records individuals, groups, or organizations related to the project and their interests; the risk register records uncertain events or conditions that may affect project objectives and how you plan to respond.
- The stakeholder register records only internal team members; the risk register records external vendors and suppliers.
- The stakeholder register records positive events; the risk register records only negative events that could delay the schedule.
- The stakeholder register is used only in predictive life cycles; the risk register is used only in adaptive life cycles.
Show Answer
Answer: A) The stakeholder register records individuals, groups, or organizations related to the project and their interests; the risk register records uncertain events or conditions that may affect project objectives and how you plan to respond.
Option 1 is correct: the stakeholder register captures information about people and organizations connected to the project and their characteristics, while the risk register captures uncertain events or conditions (threats and opportunities), their analysis, and planned responses. Stakeholders can be internal or external, and both registers are used in predictive and adaptive life cycles.
11. Quick Check: Definition and Reserves
Confirm you can recall the canonical stakeholder definition and distinguish reserves.
Which option correctly states PMI’s canonical definition of a stakeholder?
- An individual or group inside the organization who can affect or be affected by a project.
- An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
- Any customer or end user who receives the project’s product or service.
- Any person with high power and interest in the project’s outcome.
Show Answer
Answer: B) An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
Option 2 is the exact PMI definition and includes all required elements: individual, group, or organization; may affect, be affected by, or perceive itself to be affected; and applies to a decision, activity, or outcome of a project, program, or portfolio. The other options are incomplete or too narrow.
12. Flashcards: Core Terms and Exam Triggers
Use these cards to reinforce key definitions and distinctions.
- Stakeholder (PMI canonical definition)
- An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
- Stakeholder register (purpose)
- A living document that identifies stakeholders and captures information such as their roles, power, interest, attitude, requirements, and preferred engagement and communication approaches to support stakeholder engagement planning.
- Risk register (purpose)
- A central log of identified risks (threats and opportunities) that records descriptions, categories, probability, impact, priority, owners, response strategies, and status for ongoing risk management.
- Power–interest grid: High power / High interest
- Manage closely: collaborate, involve in key decisions, and keep them well informed because they can strongly influence the project and care deeply about outcomes.
- Power–interest grid: High power / Low interest
- Keep satisfied: provide periodic high-level updates and address major concerns, but avoid overloading them with detail.
- Contingency reserve vs management reserve
- Contingency reserve covers identified risks and is included in the cost baseline. Management reserve covers unknown-unknowns and is not in the cost baseline but is part of the total project budget.
- Cost baseline
- A time-phased budget used for cost control, including contingency reserves for identified risks. Adding management reserve to the cost baseline yields the total project budget.
- Threat vs opportunity
- Both are risks. A threat is an uncertain event with a negative effect on objectives; an opportunity is an uncertain event with a positive effect on objectives.
- Risk owner
- The person responsible for monitoring a specific risk and ensuring the planned response actions are carried out.
- When to update stakeholder and risk registers
- Whenever new stakeholders or risks are identified, existing ones change (e.g., attitude, probability, impact), or responses are added, implemented, or closed—throughout the project life cycle.
Key Terms
- threat
- A type of risk that, if it occurs, has a negative effect on one or more project objectives.
- project
- A temporary endeavor undertaken to create a unique product, service, or result.
- risk owner
- The person responsible for monitoring a specific risk and ensuring the planned response actions are carried out.
- opportunity
- A type of risk that, if it occurs, has a positive effect on one or more project objectives.
- stakeholder
- An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
- cost baseline
- A time-phased budget used for cost control, typically including contingency reserves for identified risks.
- risk register
- A central log of identified risks (threats and opportunities) that records descriptions, categories, probability, impact, priority, owners, response strategies, and status for ongoing risk management.
- management reserve
- Budget set aside for unknown-unknowns (unforeseen work); not included in the cost baseline but part of the total project budget.
- adaptive life cycle
- A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
- contingency reserve
- Budget set aside for identified risks that remain after planning responses; included in the cost baseline.
- stakeholder register
- A living document that identifies stakeholders and captures information such as their roles, power, interest, attitude, requirements, and preferred engagement and communication approaches to support stakeholder engagement planning.
- power–interest grid
- A stakeholder analysis tool that classifies stakeholders based on their power to influence the project and their interest in its outcomes, guiding engagement strategies.
- predictive life cycle
- A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.