Section: Volume E
Explanation/Reference: https://4squareviews.com/2013/06/26/5th-edition-pmbok-guide-chapter-9-conflict-resolution/

Section: Volume C
Explanation:
5.2.1.5 Stakeholder Register
Described in Section 13.1.3.1. The stakeholder register is used to identify stakeholders who can provide information on the requirements. The stakeholder register also captures major requirements and main expectations stakeholders may have for the project.
13.1.3.1 Stakeholder Register
The main output of the Identify Stakeholders process is the stakeholder register. This contains all details related to the identified stakeholders including, but not limited to:
Identification information. Name, organizational position, location, role in the project, contact information;

Assessment information. Major requirements, main expectations, potential influence in the project, phase

in the life cycle with the most interest; and
Stakeholder classification. Internal/external, supporter/neutral/resistor, etc.

The stakeholder register should be consulted and updated on a regular basis, as stakeholders may change- or new ones identified-throughout the life cycle of the project.
Process: 13.1 Identify Stakeholders
Definition: The process of identifying the people, groups, or organizations that could impact or be impacted by a decision, activity, or outcome of the project; and analyzing and documenting relevant information regarding their interests, involvement, interdependencies, influence, and potential impact on project success.
Key Benefit: The key benefit of this process is that it allows the project manager to identify the appropriate focus for each stakeholder or group of stakeholders.
Inputs
1. Project charter
2. Procurement documents
3. Enterprise environmental factors
4. Organizational process assets
Tools & Techniques
1. Stakeholder analysis
2. Expert judgment
3. Meetings
Outputs
1. Stakeholder register

Section: Volume A
Explanation:
Process: 4.2. Develop Project Management Plan
Definition: The process of defining, preparing, and coordinating all subsidiary plans and integrating them into a comprehensive project management plan. The project's integrated baselines and subsidiary plans may be included within the project management plan.
Key Benefit: The key benefit of this process is a central document that defines the basis of all project work.
Inputs
1. Project charter
2. Outputs from other processes
3. Enterprise environmental factors
4. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Facilitation techniques
Outputs
1. Project management plan
4.2.3.1 Project Management Plan
The project management plan is the document that describes how the project will be executed, monitored, and controlled. It integrates and consolidates all of the subsidiary plans and baselines from the planning processes.
Project baselines include, but are not limited to:
Scope baseline (Section 5.4.3.1),

Schedule baseline (Section 6.6.3.1), and

Cost baseline (Section 7.3.3.1).

Subsidiary plans include, but are not limited to:
Scope management plan (Section 5.1.3.1),

Requirements management plan (Section 5.1.3.2),

Schedule management plan (Section 6.1.3.1),

Cost management plan (Section 7.1.3.1),

Quality management plan (Section 8.1.3.1),

Process improvement plan (Section 8.1.3.2),

Human resource management plan (Section 9.1.3.1),

Communications management plan (Section 10.1.3.1),

Risk management plan (Section 11.1.3.1),

Procurement management plan (Section 12.1.3.1), and

Stakeholder management plan (Section 13.2.3.1).

Among other things, the project management plan may also include the following:
Life cycle selected for the project and the processes that will be applied to each phase;

Details of the tailoring decisions specified by the project management team as follows:

○ Project management processes selected by the project management team,
○ Level of implementation for each selected process,
○ Descriptions of the tools and techniques to be used for accomplishing those processes, and
○ Description of how the selected processes will be used to manage the specific project, including the dependencies and interactions among those processes and the essential inputs and outputs.
Description of how work will be executed to accomplish the project objectives;

Change management plan that documents how changes will be monitored and controlled;

Configuration management plan that documents how Configuration management will be performed;

Description of how the integrity of the project baselines will be maintained;

Requirements and techniques for communication among stakeholders; and

Key management reviews for content, the extent of, and timing to address, open issues and pending

decisions.
The project management plan may be either summary level or detailed, and may be composed of one or more subsidiary plans. Each of the subsidiary plans is detailed to the extent required by the specific project. Once the project management plan is baselined, it may only be changed when a change request is generated and approved through the Perform Integrated Change Control process.

Section: Volume B