Explanation/Reference:
説明する：
1.2 What is a Project?
A project is a temporary endeavor undertaken to create a unique product, service, or result. The temporary nature of projects indicates that a project has a definite beginning and end. The end is reached when the project’s objectives have been achieved or when the project is terminated because its objectives will not or cannot be met, or when the need for the project no longer exists. A project may also be terminated if the client (customer, sponsor, or champion) wishes to terminate the project. Temporary does not necessarily mean the duration of the project is short. It refers to the project’s engagement and its longevity. Temporary does not typically apply to the product, service, or result created by the project; most projects are undertaken to create a lasting outcome. For example, a project to build a national monument will create a result expected to last for centuries. Projects can also have social, economic, and environmental impacts that far outlive the projects themselves.

Explanation/Reference:
説明する：
6.6.2.3 Critical Chain Method
The critical chain method (CCM) is a schedule method that allows the project team to place buffers on any project schedule path to account for limited resources and project uncertainties. It is developed from the critical path method approach and considers the effects of resource allocation, resource optimization, resource leveling, and activity duration uncertainty on the critical path determined using the critical path method. To do so, the critical chain method introduces the concept of buffers and buffer management. The critical chain method uses activities with durations that do not include safety margins, logical relationships, and resource availability with statistically determined buffers composed of the aggregated safety margins of activities at specified points on the project schedule path to account for limited resources and project uncertainties. The resource-constrained critical path is known as the critical chain.

Explanation/Reference:
説明する：
1.4.2 Portfolio Management
A portfolio refers to projects, programs, subportfolios, and operations managed as a group to achieve strategic objectives. The projects or programs of the portfolio may not necessarily be interdependent or directly related. For example, an infrastructure firm that has the strategic objective of “maximizing the return on its investments” may put together a portfolio that includes a mix of projects in oil and gas, power, water, roads, rail, and airports. From this mix, the firm may choose to manage related projects as one program. All of the power projects may be grouped together as a power program. Similarly, all of the water projects may be grouped together as a water program.
Thus, the power program and the water program become integral components of the enterprise portfolio of the infrastructure firm.

Section: Volume C
説明する：
13.1.2.1 Stakeholder Analysis
Stakeholder analysis is a technique of systematically gathering and analyzing quantitative and qualitative information to determine whose interests should be taken into account throughout the project. It identifies the interests, expectations, and influence of the stakeholders and relates them to the purpose of the project. It also helps to identify stakeholder relationships (with the project and with other stakeholders) that can be leveraged to build coalitions and potential partnerships to enhance the project’s chance of success, along with stakeholder relationships that need to be influenced differently at different stages of the project or phase.
Stakeholder analysis generally follows the steps described below:
Identify all potential project stakeholders and relevant information, such as their roles, departments,

interests, knowledge, expectations, and influence levels. Key stakeholders are usually easy to identify. They include anyone in a decision-making or management role who is impacted by the project outcome, such as the sponsor, the project manager, and the primary customer. Identifying other stakeholders is usually done by interviewing identified stakeholders and expanding the list until all potential stakeholders are included.
Analyze the potential impact or support each stakeholder could generate, and classify them so as to define

an approach strategy. In large stakeholder communities, it is important to prioritize the stakeholders to ensure the efficient use of effort to communicate and manage their expectations.
Assess how key stakeholders are likely to react or respond in various situations, in order to plan how to

influence them to enhance their support and mitigate potential negative impacts.
There are multiple classification models used for stakeholders analysis, such as:
Power/interest grid, grouping the stakeholders based on their level of authority (“power”) and their level or

concern (“interest”) regarding the project outcomes;
Power/influence grid, grouping the stakeholders based on their level of authority (“power”) and their active

involvement (“influence”) in the project;
Influence/impact grid, grouping the stakeholders based on their active involvement (“influence”) in the project

and their ability to effect changes to the project’s planning or execution (“impact”); and Salience model, describing classes of stakeholders based on their power (ability to impose their will),

urgency (need for immediate attention), and legitimacy (their involvement is appropriate).

Section: Volume A
説明する：
4.3.3.3 Change Requests
A change request is a formal proposal to modify any document, deliverable, or baseline. An approved change request will replace the associated document, deliverable, or baseline and may result in an update to other parts of the project management plan. When issues are found while project work is being performed, change requests are submitted, which may modify project policies or procedures, project scope, project cost or budget, project schedule, or project quality. Other change requests cover the needed preventive or corrective actions to forestall negative impact later in the project. Requests for a change can be direct or indirect, externally or internally initiated, and can be optional or legally/contractually mandated, and may include:
Corrective action-An intentional activity that realigns the performance of the project work with the project

management plan;
Preventive action-An intentional activity that ensures the future performance of the project work is aligned

with the project management plan;
Defect repair-An intentional activity to modify a nonconforming product or product component;

Updates-Changes to formally controlled project documents, plans, etc., to reflect modified or additional

ideas or content.

Section: Volume E
説明する：
Delphi technique. The Delphi technique is a way to reach a consensus of experts. Project risk experts participate in this technique anonymously. A facilitator uses a questionnaire to solicit ideas about the important project risks. The responses are summarized and are then recirculated to the experts for further comment.
Consensus may be reached in a few rounds of this process. The Delphi technique helps reduce bias in the data and keeps any one person from having undue influence on the outcome.
5.2.2.5 Group Decision-Making Techniques
A group decision-making technique is an assessment process having multiple alternatives with an expected outcome in the form of future actions. These techniques can be used to generate, classify, and prioritize product requirements.
There are various methods of reaching a group decision, such as:
* Unanimity. A decision that is reached whereby everyone agrees on a single course of action. One way to reach unanimity is the Delphi technique, in which a selected group of experts answers questionnaires and provides feedback regarding the responses from each round of requirements gathering. The responses are only available to the facilitator to maintain anonymity.
* Majority. A decision that is reached with support obtained from more than 50 % of the members of the group. Having a group size with an uneven number of participants can ensure that a decision will be reached, rather than resulting in a tie.
* Plurality. A decision that is reached whereby the largest block in a group decides, even if a majority is not achieved. This method is generally used when the number of options nominated is more than two.
* Dictatorship. In this method, one individual makes the decision for the group. All of these group decision- making techniques can be applied to the group creativity techniques used in the Collect Requirements process.

Section: Volume E
Explanation/Reference:
説明する：
Process: 9.3 Develop Project Team
Definition: The process of improving competencies, team member interaction, and overall team environment to enhance project performance. The key benefit of this process is that it results in improved teamwork, enhanced people skills and competencies, motivated employees, reduced staff turnover rates, and improved overall project performance.
Key Benefit: The key benefit of this process is that it results in improved teamwork, enhanced people skills and competencies, motivated employees, reduced staff turnover rates, and improved overall project performance.
Inputs
1. Human resource management plan
2. Project staff assignments
3. Resource calendars
Tools & Techniques
1. Interpersonal skills
2. Training
3. Team-building activities
4. Ground rules
5. Colocation
6. Recognition and rewards
7. Personnel assessment tools
Outputs
1. Team performance assessments
2. Enterprise environmental factors updates

Explanation/Reference:
説明する：
Process: 5.5 Validate Scope
Definition: The process of formalizing acceptance of the completed project deliverables.
Key Benefit: The key benefit of this process is that it brings objectivity to the acceptance process and increases the chance of final product, service, or result acceptance by validating each deliverable.
Inputs
1. Project management plan
2. Requirements documentation
3. Requirements traceability matrix
4. Verified deliverables
5. Work performance data
Tools & Techniques
1. Inspection
2. Group decision-making techniques
Outputs
1. Accepted deliverables
2. Change requests
3. Work performance information
4. Project documents updates

Explanation/Reference:
説明する：
2.1.4 Organizational Process Assets
Organizational process assets are the plans, processes, policies, procedures, and knowledge bases specific to and used by the performing organization. They include any artifact, practice, or knowledge from any or all of the organizations involved in the project that can be used to perform or govern the project. The process assets also include the organization’s knowledge bases such as lessons learned and historical information. Organizational process assets may include completed schedules, risk data, and earned value data. Organizational process assets are inputs to most planning processes. Throughout the project, the project team members may update and add to the organizational process assets as necessary.
Organizational process assets may be grouped into two categories: (1) processes and procedures, and (2) corporate knowledge base.
6.1 Plan Schedule Management
Definition: The process of establishing the policies, procedures, and documentation for planning, developing, managing, executing, and controlling the project schedule.
Key Benefit: The key benefit of this process is that it provides guidance and direction on how the project schedule will be managed throughout the project.
Inputs
1. Project management plan
2. Project charter
3. Enterprise environmental factors
4. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Analytical techniques
3. Meetings
Outputs
1. Schedule management plan

Explanation/Reference:
説明する：
Process: 9.3 Develop Project Team
Definition: The process of improving competencies, team member interaction, and overall team environment to enhance project performance.
Key Benefit: The key benefit of this process is that it results in improved teamwork, enhanced people skills and competencies, motivated employees, reduced staff turnover rates, and improved overall project performance.
Inputs
1. Human resource management plan
2. Project staff assignments
3. Resource calendars
Tools & Techniques
1. Interpersonal skills
2. Training
3. Team-building activities
4. Ground rules
5. Colocation
6. Recognition and rewards
7. Personnel assessment tools
Outputs
1. Team performance assessments
2. Enterprise environmental factors updates

Section: Volume E
Explanation/Reference: https://www.project-management-prepcast.com/kunena/pmp-exam-discussion/7710-difference- between-manage-quality-and-control-quality