Get May-2023 updated CAPM Certification Exam Sample Questions [Q26-Q48]

Explanation/Reference:
Explanation:
Planning Process Group
4.2 Develop Project Management Plan
5.1 Plan Scope Management
5.2 Collect Requirements
5.3 Define Scope
5.4 Create WBS
6.1 Plan Schedule Management
6.2 Define Activities
6.3 Sequence Activities
6.4 Estimate Activity Resources
6.5 Estimate Activity Durations
6.6 Develop Schedule
7.1 Plan Cost Management
7.2 Estimate Costs
7.3 Determine Budget
8.1 Plan Quality Management
9.1 Plan Human Resource Management
10.1 Plan Communications 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
12.1 Plan Procurement Management
13.2 Plan Stakeholder Management

Section: Volume E

Explanation/Reference:
Explanation:
5.4.2.1 Decomposition
Decomposition is a technique used for dividing and subdividing the project scope and project deliverables into smaller, more manageable parts. The work package is the work defined at the lowest level of the WBS for which cost and duration can be estimated and managed. The level of decomposition is often guided by the degree of control needed to effectively manage the project. The level of detail for work packages will vary with the size and complexity of the project. Decomposition of the total project work into work packages generally involves the following activities:
Identifying and analyzing the deliverables and related work;

Structuring and organizing the WBS;

Decomposing the upper WBS levels into lower-level detailed components;

Developing and assigning identification codes to the WBS components; and

Verifying that the degree of decomposition of the deliverables is appropriate.

Section: Volume E
Explanation/Reference: https://www.projectmanager.com/blog/project-quality-management-quick-guide

Section: Volume E

Section: Volume B

Section: Volume D
Explanation
Explanation:
12.1.3.2 Procurement Statement of Work
The statement of work (SOW) for each procurement is developed from the project scope baseline and defines only that portion of the project scope that is to be included within the related contract. The procurement SOW describes the procurement item in sufficient detail to allow prospective sellers to determine if they are capable of providing the products, services, or results. sufficient detail can vary based on the nature of the item, the needs of the buyer, or the expected contract form. Information included in a SOW can include specifications, quantity desired, quality levels, performance data, period of performance, work location, and other requirements.
The procurement SOW is written to be clear, complete, and concise. It includes a description of any collateral services required, such as performance reporting or post-project operational support for the procured item. In some application areas, there are specific content and format requirements for a procurement SOW. Each individual procurement item requires a SOW; however, multiple products or services can be grouped as one procurement item within a single SOW.
The procurement SOW can be revised and refined as required as it moves through the procurement process until incorporated into a signed agreement.

Section: Volume A
Explanation:
Process: 9.1 Plan Human Resource Management
Definition: The process of identifying and documenting project roles, responsibilities, required skills, reporting relationships, and creating a staffing management plan.
Key Benefit: The key benefit of this process is that it establishes project roles and responsibilities, project organization charts, and the staffing management plan including the timetable for staff acquisition and release.
Inputs
1. Project management plan
2. Activity resource requirements
3. Enterprise environmental factors
4. Organizational process assets
Tools & Techniques
1. Organization charts and position descriptions
2. Networking
3. Organizational theory
4. Expert judgment
5. Meetings
Outputs
Human resource management plan

Explanation/Reference:
Explanation:
Process: 4.6. Close Project or Phase
Definition: The process of finalizing all activities across all of the Project Management Process Groups to formally complete the phase or project.
Key Benefit: The key benefit of this process is that it provides lessons learned, the formal ending of project work, and the release of organization resources to pursue new endeavors.
Inputs
1. Project management plan
2. Accepted deliverables
3. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Analytical techniques
3. Meetings
Outputs
1. Final product, service, or result transition
2. Organizational process assets updates

Explanation/Reference:
Reference: https://www.projectengineer.net/project-procurement-management-according-to-the-pmbok/

Section: Volume E
Explanation:
10.1.3.1 Communications Management Plan
The communications management plan is a component of the project management plan that describes how project communications will be planned, structured, monitored, and controlled. The plan contains the following information:
Stakeholder communication requirements;

Information to be communicated, including language, format, content, and level of detail;

Reason for the distribution of that information;

Time frame and frequency for the distribution of required information and receipt of acknowledgment or

response, if applicable;
Person responsible for communicating the information;

Person responsible for authorizing release of confidentialrefining information;

Person or groups who will receive the information;

Methods or technologies used to convey the information, such as memos, e-mail, and/or press releases;

Resources allocated for communication activities, including time and budget;

Escalation process identifying time frames and the management chain (names) for escalation of issues that

cannot be resolved at a lower staff level;
Method for updating and refining the communications management plan as the project progresses and

develops;
Glossary of common terminology;

Flow charts of the information flow in the project, workflows with possible sequence of authorization, list of

reports, and meeting plans, etc.; and
Communication constraints usually derived from a specific legislation or regulation, technology, and

organizational policies, etc.
The communications management plan can also include guidelines and templates for project status meetings, project team meetings, e-meetings, and e-mail messages. The use of a project website and project management software can also be included if these are to be used in the project.

Section: Volume E
Explanation:
6.3.2.2 Dependency Determination
Dependencies may be characterized by the following attributes: mandatory or discretionary, internal or external, as described below. Dependency has four attributes, but two can be applicable at the same time in following ways: mandatory external dependencies, mandatory internal dependencies, discretionary external dependencies, or discretionary internal dependencies.
Mandatory dependencies. Mandatory dependencies are those that are legally or contractually required or

inherent in the nature of the work. Mandatory dependencies often involve physical limitations, such as on a construction project, where it is impossible to erect the superstructure until after the foundation has been built, or on an electronics project, where a prototype has to be built before it can be tested. Mandatory dependencies are also sometimes referred to as hard logic or hard dependencies. Technical dependencies may not be mandatory. The project team determines which dependencies are mandatory during the process of sequencing the activities. Mandatory dependencies should not be confused with assigning schedule constraints in the scheduling tool.
Discretionary dependencies. Discretionary dependencies are sometimes referred to as preferred logic,

preferential logic, or soft logic. Discretionary dependencies are established based on knowledge of best practices within a particular application area or some unusual aspect of the project where a specific sequence is desired, even though there may be other acceptable sequences. Discretionary dependencies should be fully documented since they can create arbitrary total float values and can limit later scheduling options. When fast tracking techniques are employed, these discretionary dependencies should be reviewed and considered for Explanation:
4.1.2.1 Expert Judgment
Expert judgment is often used to assess the inputs used to develop the project charter. Expert judgment is applied to all technical and management details during this process. Such expertise is provided by any group or individual with specialized knowledge or training and is available from many sources, including:
Other units within the organization,

Consultants,

Stakeholders, including customers or sponsors,

Professional and technical associations,

Industry groups,

Subject matter experts (SME), and

Project management office (PMO).

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
5. Expert judgment
6. Facilitation techniques
Outputs
7. 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.
modification or removal. The project team determines which dependencies are discretionary during the process of sequencing the activities.
External dependencies. External dependencies involve a relationship between project activities and non-

project activities. These dependencies are usually outside the project team’s control. For example, the testing activity in a software project may be dependent on the delivery of hardware from an external source, or governmental environmental hearings may need to be held before site preparation can begin on a construction project. The project management team determines which dependencies are external during the process of sequencing the activities.
Internal dependencies. Internal dependencies involve a precedence relationship between project activities

and are generally inside the project team’s control. For example, if the team cannot test a machine until they assemble it, this is an internal mandatory dependency. The project management team determines which dependencies are internal during the process of sequencing the activities.