2. Project Stakeholder Management
Coincides with PMBOK 13.0
Process Group and Knowledge Area Mapping
Knowledge Areas Initiating Planning Process Group Executing Process Group
Monitoring and Controlling Process
Group
Closing Process Group
4. Project Integration
Management
4.1 Develop Project Charter
4.2 Develop Project
Management Plan
4.3 Direct and Manage Project
Work
4.4 Manage Project Knowledge
4.5 Monitor and Control Project Work
4.6 Perform Integrated Change Control
4.7 Close Project or
Phase
5. Project Scope
Management
5.1 Plan Scope Management
5.2 Collect Requirements
5.3 Define Scope
5.4 Create WBS
5.5 Validate Scope
5.6 Control Scope
6. Project Schedule
Management
6.1 Plan Schedule Management
6.2 Define Activities
6.3 Sequence Activities
6.4 Estimate Activity Durations
6.5 Develop Schedule
6.6 Control Schedule
7. Project Cost
Management
7.1 Plan Cost Management
7.2 Estimate Costs
7.3 Determine Budget
7.4 Control Costs
8. Project Quality
Management
8.1 Plan Quality Management 8.2 Manage Quality 8.3 Control Quality
9. Project Resource
Management
9.1 Plan Resource Management
9.2 Estimate Activity Resources
9.3 Acquire Resources
9.4 Develop Team
9.5 Manage Team
9.6 Control Resources
10. Project
Communications
Management
10.1 Plan Communications
Management
10.2 Manage Communications 10.3 Monitor Communications
11. Project Risk
Management
11.1 Plan Risk Management
11.2 Identify Risks
11.3 Perform Qualitative Risk
Analysis
11.4 Perform Quantitative Risk
Analysis
11.5 Plan Risk Responses
11.6 Implement Risk Responses 11.7 Monitor Risks
12. Project Procurement
Management
12.1 Plan Procurement
Management
12.2 Conduct Procurements 12.3 Control Procurements
13. Project Stakeholder
Management
13.1 Identify Stakeholders
13.2 Plan Stakeholder
Engagement
13.3 Manage Stakeholder
Engagement
13.4 Monitor Stakeholder Engagement
3. Project Stakeholder Management
Coincides with PMBOK 13.0
The Project Stakeholder Management Processes are:
13.1 Identify Stakeholders
13.2 Plan Stakeholder Engagement
13.3 Manage Stakeholder Engagement
13.4 Monitor Stakeholder Engagement
Planning
Monitoring and
Controlling
Executing
Initiating
Closing
4. Project Stakeholder Management Overview
Project Stakeholder Management
Coincides with PMBOK 13.0
Identify Stakeholders
Plan Stakeholder
Engagement
Manage Stakeholder
Engagement
Monitor Stakeholder
Engagement
1. Project charter
2. Business documents
3. Project management plan
4. Project documents
5. Agreements
6. Enterprise environmental factors
7. Organizational process assets
1. Project charter
2. Project management plan
3. Project documents
4. Agreements
5. Enterprise environmental
factors
6. Organizational process assets
1. Project management plan
2. Project documents
3. Enterprise environmental factors
4. Organizational process assets
1. Project management plan
2. Project documents
3. Work performance data
4. Enterprise environmental factors
5. Organizational process assets
1. Expert judgment
2. Data gathering
3. Data analysis
4. Data representation
5. Meetings
1. Expert judgment
2. Data gathering
3. Data analysis
4. Decision making
5. Data representation
6. Meetings
1. Expert judgment
2. Communication skills
3. Interpersonal and team skills
4. Ground rules
5. Meetings
1. Data analysis
2. Decision making
3. Data representation
4. Communication skills
5. Interpersonal and team skills
6. Meetings
1. Stakeholder register
2. Change requests
3. Project management plan
updates
4. Project documents updates
1. Stakeholder engagement plan
1. Change requests
2. Project management plan updates
3. Project documents updates
1. Work performance information
2. Change requests
3. Project management plan updates
4. Project documents updates
Inputs
Tools&
Techniques
Outputs
5. Key Concepts
Project Stakeholder Management
Coincides with PMBOK 13.0
Every project has stakeholders who are impacted by or can impact the
project in a positive or negative way.
Some stakeholders may have a limited ability to influence the project’s
work or outcomes; others may have significant influence on the project and
its expected outcomes.
Academic research and analyses of high-profile project disasters highlight
the importance of a structured approach to the identification and
engagement of all stakeholders.
To increase the chances of success, the process of stakeholder identification
and engagement should commence as soon as possible after the project
charter has been approved.
6. Trends and Emerging Practices
Project Stakeholder Management
Coincides with PMBOK 13.0
Who is a Stakeholder?
Broader definitions of stakeholders are being developed that expand the traditional
categories of employees, suppliers, and shareholders to include groups such as
regulators, lobby groups, environmentalists, financial organizations, the media, and
those who simply believe they are stakeholders—they perceive that they will be
affected by the work or outcomes of the project.
7. Trends and Emerging Practices
Project Stakeholder Management
Coincides with PMBOK 13.0
Trends and emerging practices for Project Stakeholder Management include but are not
limited to:
1. Identifying all stakeholders, not just a limited set.
2. Ensuring that all team members are involved in stakeholder engagement activities.
3. Reviewing the stakeholder community regularly, often in parallel with reviews of
individual project risks.
4. Consulting with stakeholders who are most affected by the work or outcomes of the
project through the concept of co-creation. Co-creation places greater emphasis on
including affected stakeholders in the team as partners.
5. Capturing the value of effective stakeholder engagement, both positive and
negative.
8. Project Stakeholder Management
Coincides with PMBOK 13.0
Because each project is unique, the project manager may need to tailor the
way Project Stakeholder Management processes are applied.
Considerations for tailoring include but are not limited to:
1. Stakeholder diversity
2. Complexity of stakeholder relationships
3. Communication technology
Tailoring Considerations
9. Considerations for Agile or Adaptive Environments
Project Stakeholder Management
Coincides with PMBOK 13.0
Projects experiencing a high degree of change require active engagement
and participation with project stakeholders.
This includes collaboration directly with the customer or Product Owner,
increasing communication through daily stand-ups, transparent
communication through Kanban Boards and inviting all stakeholders to
update meetings.
The development team also takes changing requirements on board as they
come to light, “grooming the backlog” of work, and increasing engagement.
Hinweis der Redaktion
The process of identifying project stakeholders regularly and analysing and documenting relevant information regarding their interests, involvement, interdependencies, influence, and potential impact on project success.
The process of developing approaches to involve project stakeholders based on their needs, expectation, interests, and potential impact on the project.
The process of communicating and working with stakeholders to meet their needs and expectations, address issues, and foster appropriate stakeholder engagement involvement.
The process of monitoring project stakeholder relationships and tailoring strategies for engaging stakeholders through the modification of engagement strategies and plans.
.
.
How many stakeholders are there? How diverse is the culture within the stakeholder community?
How complex are the relationships within the stakeholder community? The more networks a stakeholder or stakeholder group participates in, the more complex the networks of information and misinformation the stakeholder may receive.
What communication technology is available? What support mechanisms are in place to ensure that best value is achieved from the technology?