SkarpChapter 3 of 21
Stakeholders, Governance, and the Project Manager’s Integration Role
Who really holds power on a project, how do decisions get made, and how does a project manager keep everything—from scope to stakeholders—moving in sync?
Stakeholders and Governance: Why They Matter for CAPM
Big Picture
This module links three core CAPM ideas: stakeholders, project governance, and the project manager’s integration role across all project areas.
Stakeholder Definition
Memorize this: a stakeholder is "An individual, group, or organization who may affect, be affected by, or perceive itself to be affected" by the project.
Why It Matters
Stakeholders include internal and external parties, plus anyone who only perceives they are affected. They all matter for engagement and risk.
Governance and Integration
Project governance defines who decides what and how. The project manager integrates scope, schedule, cost, quality, resources, and stakeholders into one coherent whole.
Identifying Stakeholders and Building the Stakeholder Register
Start With Identification
Stakeholder work starts by identifying everyone who may affect, be affected by, or perceive themselves as affected by the project.
Think Broadly
Brainstorm internal roles (sponsor, PMO, managers) and external groups (customers, regulators, community, media, unions).
Stakeholder Register
The stakeholder register records each stakeholder’s role, power, interest, attitude, desired engagement, and communication preferences.
Living Document
The register is updated whenever new stakeholders appear or attitudes change. On exam questions, update it before changing plans or communications.
Example: Building a Stakeholder Register for a Campus App
Campus App Scenario
You manage a university mobile app project. Who may affect, be affected by, or perceive themselves affected by this project?
Identified Stakeholders
Include sponsor, IT director, PMO, vendor, students, faculty, registrar, finance, IT ops, student union, accessibility office.
Sample Register Entries
For each stakeholder, record power, interest, attitude, desired engagement, and preferred communication methods.
New Stakeholder Appears
A Data Protection Officer emerges due to regulation changes. Correct move: update the stakeholder register and engagement and risk plans.
Stakeholder Analysis: Power, Interest, and Engagement Strategies
Power/Interest Grid
You analyze stakeholders by power (influence) and interest (concern) to choose appropriate engagement strategies.
High Power, High Interest
Collaborate closely: frequent two-way communication, involvement in key decisions, early feedback.
High Power, Low Interest
Keep satisfied: periodic high-level updates and involve them when their domain is affected, without flooding them with detail.
Attitude Matters
Layer in attitude (supportive, neutral, resistant) and update your analysis and engagement plan when attitudes or power shift.
Thought Exercise: Classify Stakeholders and Pick Strategies
Work through this scenario mentally (or jot notes). This mirrors CAPM-style reasoning.
Scenario
You manage a project to implement an electronic medical records (EMR) system in a mid-size clinic.
Stakeholders:
- Chief Medical Officer (CMO): decides clinical policies, strongly supports EMR, very busy.
- Senior Nurse Manager: worries about extra workload, influential among nurses.
- IT Security Lead: responsible for data protection compliance, has veto power on security issues, low initial interest.
- Patients’ Advisory Council: volunteers representing patient interests, no formal authority but active on social media.
Your tasks
- For each stakeholder, decide their approximate power (high/medium/low) and interest (high/medium/low).
- Place them into one of the four strategy buckets: collaborate closely, keep satisfied, keep informed, monitor.
- Note one specific engagement action for each.
Pause and think before checking the suggested mapping in your head:
- CMO: Likely high power, high interest → collaborate closely (e.g., monthly steering meetings).
- Senior Nurse Manager: Medium power (strong informal influence), high interest → collaborate closely or keep informed with workshops and pilots.
- IT Security Lead: High power (veto), low/medium interest → keep satisfied with targeted reviews of security designs.
- Patients’ Advisory Council: Low formal power, high interest → keep informed via newsletters, usability tests, and feedback channels.
Reflect: Which stakeholder poses the biggest risk if mishandled? How would you know, and how would that show up in the stakeholder register?
Project Governance: Phase Gates, Change Control Boards, and Escalation Paths
What Is Governance?
Project governance defines formal oversight and decision mechanisms: who reviews progress, approves changes, and resolves escalated issues.
Phase Gates
At the end of each phase, governance bodies review performance, risks, and business case to decide go, hold, redirect, or terminate.
Change Control Board
A CCB reviews and approves or rejects change requests. The PM analyzes impacts but typically does not approve major changes alone.
Escalation Paths
Escalation paths define when and to whom issues are escalated beyond the PM, often based on impact thresholds and authority levels.
Risk Register and Stakeholder Register as Governance Artifacts
Risk Register Role
The risk register lists risks, their probability, impact, owners, and responses. It feeds phase gate decisions and escalation.
Stakeholder Register Role
The stakeholder register identifies who must be involved in governance bodies and where resistance or support may appear.
They Work Together
New risks often involve stakeholders, so both registers are updated. Governance reviews can create new risks or shift attitudes.
On the Exam
When new risks or stakeholders appear, update the appropriate register(s) and then apply governance, rather than acting with no documentation.
PMO Types and Their Impact on Governance and the PM
What Is a PMO?
A PMO standardizes project governance processes and supports projects with methods, tools, and sometimes direct management.
Supportive PMO
Provides advice, templates, and training. Authority is low; the PM retains most decision-making power.
Controlling PMO
Provides support and enforces standards through audits and required processes. Authority is moderate.
Directive PMO
Directly manages projects and assigns PMs. Authority is high and strongly shapes governance and decisions.
The Project Manager’s Integration Role Across Scope, Schedule, Cost, Quality, Resources, and Stakeholders
What Is Integration?
Integration means the PM coordinates scope, schedule, cost, quality, resources, and stakeholder engagement as a single system.
Change Request Example
A new feature affects schedule, cost, quality, and risks. The PM analyzes all impacts, updates registers, and uses the CCB for approval.
Resource Conflict Example
Losing a key resource affects schedule and quality. The PM negotiates, escalates if needed, and re-baselines with proper approvals.
Exam Mindset
Look for answers that consider multiple constraints and stakeholders and that use governance and communication, not just local fixes.
Quiz 1: Stakeholders and Governance Decisions
Test your understanding of stakeholders, registers, and governance mechanisms.
A new regulatory body announces stricter data protection rules that will significantly affect your ongoing project. This body was not previously identified. What is the BEST next action for the project manager?
- Immediately update the schedule to add more compliance testing activities.
- Update the stakeholder register and risk register, then plan how to engage the new regulator before proposing changes.
- Escalate to the sponsor and ask them to negotiate directly with the regulator without updating project documents.
- Send an email to all team members instructing them to stop work until further notice.
Show Answer
Answer: B) Update the stakeholder register and risk register, then plan how to engage the new regulator before proposing changes.
The new regulatory body is a stakeholder and introduces new risks. The best next step is to update the stakeholder register and risk register, then plan engagement and potential responses. Changing the schedule or stopping work without analysis and proper governance is premature; escalating without updating records misses core governance practices.
Quiz 2: PMO Types and Integration Thinking
Check your understanding of PMO authority and the PM’s integration role.
Your organization has a PMO that assigns project managers, owns the project budgets, and chairs the change control board. Which PMO type is this, and what is the MOST appropriate role of the project manager when a major scope change is requested?
- Supportive PMO; the project manager can approve the change independently as long as the team agrees.
- Controlling PMO; the project manager should reject the change to protect the baseline.
- Directive PMO; the project manager should analyze impacts across scope, schedule, cost, quality, and resources, and present the analysis to the PMO-led CCB.
- Supportive PMO; the project manager should ask the sponsor to decide without involving the PMO.
Show Answer
Answer: C) Directive PMO; the project manager should analyze impacts across scope, schedule, cost, quality, and resources, and present the analysis to the PMO-led CCB.
A PMO that assigns PMs, owns budgets, and chairs the CCB is a directive PMO with high authority. The project manager’s role is to perform integration analysis (scope, schedule, cost, quality, resources, stakeholders) and bring that information to the PMO-led governance body for a decision.
Key Terms and Concepts Review
Flip through these cards to reinforce core definitions and distinctions before you move on.
- Stakeholder (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
- A living document that lists project stakeholders and key information about them, such as role, power, interest, attitude, desired engagement, and communication preferences.
- Power/interest grid
- A stakeholder analysis tool that maps stakeholders by their level of power (influence) and interest in the project, guiding strategies like collaborate closely, keep satisfied, keep informed, or monitor.
- Phase gate
- A governance checkpoint at the end of a project phase where decision makers review performance, risks, and the business case to decide whether to continue, modify, or terminate the project.
- Change Control Board (CCB)
- A formally chartered group that reviews, evaluates, and approves, defers, or rejects change requests, based on their impact on scope, schedule, cost, quality, risk, and stakeholders.
- Escalation path
- A predefined route for raising issues or risks beyond the project manager’s authority, specifying when and to whom items are escalated.
- Risk register
- A central record of identified risks, including their probability, impact, owners, response strategies, and status, used for decision making and governance.
- Supportive PMO
- A PMO type with low authority that provides consultative support such as templates, training, and best practices but does not enforce standards.
- Controlling PMO
- A PMO type with moderate authority that provides support and requires compliance with standardized methodologies, tools, and governance processes.
- Directive PMO
- A PMO type with high authority that directly manages projects, often assigning project managers and owning budgets and major decisions.
- Project manager’s integration role
- The responsibility to coordinate and balance scope, schedule, cost, quality, resources, and stakeholder engagement, ensuring that changes and decisions are evaluated across all areas and handled through proper governance.
Key Terms
- project
- A temporary endeavor undertaken to create a unique product, service, or result.
- phase gate
- A governance checkpoint at the end of a project phase where continuation, modification, or termination decisions are made.
- 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.
- directive PMO
- A PMO that directly manages projects and has high authority over them.
- risk register
- A central record of identified risks, including probability, impact, owners, responses, and status.
- supportive PMO
- A PMO that provides consultative support with low authority over projects.
- controlling PMO
- A PMO that provides support and enforces compliance with standards, with moderate authority.
- escalation path
- A predefined route for raising issues or risks beyond the project manager’s authority level.
- project governance
- The framework of rules, roles, and decision-making mechanisms that guide project oversight, control, and alignment with organizational objectives.
- power/interest grid
- A stakeholder analysis tool that maps stakeholders by power and interest to guide engagement strategies.
- stakeholder register
- A document listing project stakeholders and key information about their role, power, interest, attitude, desired engagement, and communication preferences.
- change control board (CCB)
- A formally chartered group that reviews and decides on change requests based on their impacts.
- Project Management Office (PMO)
- An organizational structure that standardizes project-related governance processes and supports resource, methodology, and tool sharing.
- integration (project management)
- The coordination of all project components—scope, schedule, cost, quality, resources, and stakeholder engagement—into a coherent whole.