Stakeholder Identification and Role Assignment in Project Initiation
PMBOK v8 Definition
Stakeholders who will interact and influence the overall outcome of the project are identified and project management roles are assigned. This information is often captured in artifacts such as a project charter or stakeholder register. The key benefits of this Focus Area are that projects are only authorized when aligned with the organization’s strategic objectives and when the business case, benefits, and stakeholders are considered from the start of the project.
This concept belongs to the Stakeholders Performance Domain within the PMBOK v8 framework, specifically associated with the Identify Stakeholders process.
Why It Matters for the Exam
This concept appears frequently in PMI exam questions about project initiation, stakeholder analysis, and governance. Questions typically test your understanding of when stakeholder identification occurs, what artifacts capture this information, and how stakeholder influence changes throughout the project lifecycle. Expect scenario-based questions where you must identify the correct sequence of stakeholder activities.
Key Points to Remember (for the exam)
- Primary Artifacts: Stakeholder information is captured in the project charter and stakeholder register
- Timing: Stakeholder identification occurs regularly, not just at project start (process is iterative)
- Strategic Alignment: Projects are authorized only when aligned with organizational strategic objectives
- Inclusion Scope: Stakeholders include internal and external individuals, groups, and organizations
- Stakeholder Categories: Supportive, neutral, and opponents (those not supportive) must all be identified
- PM Role: In some organizations, the project manager is involved in developing the business case and defining benefits
- Key Skills Required: Negotiation and conflict management are essential for this performance domain
Typical PMI Exam Example
A project manager is assigned to a new infrastructure project. The sponsor has provided the business case but has not identified any stakeholders. What should the project manager do FIRST?
Correct approach: Begin identifying stakeholders who will interact with and influence the project outcome, documenting them in the stakeholder register, and ensuring the project aligns with strategic objectives before proceeding with detailed planning.
PMI Exam Traps
-
Trap: Thinking stakeholder identification happens only once at project start Reality: Stakeholders are identified regularly throughout the project; influence, power, and interests may change as the project unfolds
-
Trap: Focusing only on supportive stakeholders Reality: You must identify opponents (those not supportive) as well as neutral and supportive stakeholders
-
Trap: Confusing the project charter with the stakeholder register Reality: Both artifacts capture stakeholder information, but the charter authorizes the project while the register documents detailed stakeholder analysis
-
Trap: Believing the project manager always develops the business case Reality: In some organizations, the PM is involved, but this is not universal; the key benefit is that stakeholders are considered from the start
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Plan Stakeholder Engagement | Sequential process after Identify Stakeholders | Exam tests the order: Identify → Plan → Manage |
| Plan Communications Management | Complementary process | Planning how to communicate with identified stakeholders |
| Business Case | Input to project authorization | Projects authorized only when aligned with strategic objectives |
| Directions of Influence | Classification technique | Upward, Downward, Outward, Sideward classifications tested frequently |
Quick Review Questions
-
What are the two primary artifacts where stakeholder information is captured during project initiation?
-
A stakeholder who opposes your project has been identified. Should you exclude them from the stakeholder register? Why or why not?
-
When should stakeholder identification occur during a project lifecycle?
-
What are the four directions of influence used to classify stakeholders?
-
In what circumstances might a project manager be involved in developing the business case?
PMBOK v8 Reference
Section 2.6 - Stakeholders Performance Domain (Stakeholders who will interact and influence the overall outcome of the project are identified and project management roles are assigned)
Note: The PMBOK v8 organizes content by Performance Domains rather than traditional Process Groups and Knowledge Areas. The Stakeholders Performance Domain includes: Identify Stakeholders, Plan Stakeholder Engagement, Plan Communications Management, and Manage Stakeholder Engagement.