설명/참조:
설명:
4.5.3.2 Change Log
A change log is used to document changes that occur during a project. These changes and their impact to the project in terms of time, cost, and risk, are communicated to the appropriate stakeholders. Rejected change requests are also captured in the change log.
13.3.1.3 Change Log
Described in Section 4.5.3.2. A change log is used to document changes that occur during a project.
These changes-and their impact on the project in terms of time, cost, and risk-are communicated to the appropriate stakeholders.

섹션: 볼륨 E

설명/참조:
설명:
Process: 5.1 Plan Scope Management
Definition: The process of creating a scope management plan that documents how the project scope will be defined, validated, and controlled.
Key Benefit: The key benefit of this process is that it provides guidance and direction on how scope 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. Meetings
Outputs
1. Scope management plan
2. Requirements management plan

섹션: 볼륨 E
설명/참조:

섹션: 볼륨 D
설명:
11.2.2.2 Information Gathering Techniques
Examples of information gathering techniques used in identifying risks can include:
Brainstorming. The goal of brainstorming is to obtain a comprehensive list of project risks. The project team

usually performs brainstorming, often with a multidisciplinary set of experts who are not part of the team. Ideas about project risk are generated under the leadership of a facilitator, either in a traditional free-form brainstorm session or structured mass interviewing techniques. Categories of risk, such as in a risk breakdown structure, can be used as a framework. Risks are then identified and categorized by type of risk and their definitions are refined.
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.
Interviewing. Interviewing experienced project participants, stakeholders, and subject matter experts helps

to identify risks.
Root cause analysis. Root-cause analysis is a specific technique used to identify a problem, discover the

underlying causes that lead to it, and develop preventive action.

섹션: 볼륨 E
Explanation/Reference: https://www.greycampus.com/opencampus/project-management-professional/closing-a-project-or- phase

설명/참조:
설명:
9.3.2.3 Team-Building Activities
Team-building activities can vary from a 5-minute agenda item in a status review meeting to an off-site, professionally facilitated experience designed to improve interpersonal relationships. The objective of team-building activities is to help individual team members work together effectively. Team-building strategies are particularly valuable when team members operate from remote locations without the beneft of face-to-face contact. Informal communication and activities can help in building trust and establishing good working relationships.
As an ongoing process, team building is crucial to project success. While team building is essential during the initial stages of a project, it is a never-ending process. Changes in a project environment are inevitable, and to manage them effectively, a continued or a renewed team-building effort should be applied. The project manager should continually monitor team functionality and performance to determine if any actions are needed to prevent or correct various team problems.
One of the models used to describe team development is the Tuckman ladder (Tuckman, 1965; Tuckman
& Jensen, 1977), which includes fve stages of development that teams may go through. Although it’s common for these stages to occur in order, it’s not uncommon for a team to get stuck in a particular stage or slip to an earlier stage. Projects with team members who worked together in the past may skip a stage.
Forming. This phase is where the team meets and learns about the project and their formal roles and

responsibilities. Team members tend to be independent and not as open in this phase.
Storming. During this phase, the team begins to address the project work, technical decisions, and the

project management approach. If team members are not collaborative and open to differing ideas and perspectives, the environment can become counterproductive.
Norming. In the norming phase, team members begin to work together and adjust their work habits and

behaviors to support the team. The team learns to trust each other.
Performing. Teams that reach the performing stage function as a well-organized unit. They are

interdependent and work through issues smoothly and effectively.
Adjourning. In the adjourning phase, the team completes the work and moves on from the project. This

typically occurs when staff is released from the project as deliverables are completed or as part of carrying out the Close Project or Phase process (Section 4.6). The duration of a particular stage depends upon team dynamics, team size, and team leadership. Project managers should have a good understanding of team dynamics in order to move their team members through all stages in an effective manner.
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

섹션: 볼륨 D
설명:
Project Life Cycle. The series of phases that a project passes through from its initiation to its closure.