PMI-CAPM Practice Questions

The Estimate Activity Resources process involves estimating the team resources and the type and quantities of materials, equipment, and supplies necessary to perform project work. The resource calendar is a critical input because it identifies the working days, shifts, and availability of specific resources. This information directly influences the estimation of the quantity and duration for which a resource is needed, ensuring the estimates are realistic and aligned with resource constraints.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Project Management Institute. Section 9.2.1.2

Project Documents

p. 315.

2. Shtub

A. (2016). Project Management: Processes

Methodologies

and Economics (3rd ed.). Pearson. Chapter 5

"The Project and the Organization

" discusses resource availability and calendars as fundamental components for planning. (Note: This aligns with the principles taught in university-level project management courses).

Pre-assignment of project team members occurs when individuals are selected for the team before the formal resource acquisition process begins. This is common when the project's approval or success is contingent on the expertise of specific people. A primary example is when a project is awarded based on a competitive proposal that explicitly named and promised certain individuals as part of the project team. This commitment ensures that the required expertise, as promised to the client or stakeholders, is secured for the project from its inception.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Project Management Institute. Section 9.3.2.2

"Pre-Assignment

" p. 330. The guide states

"This situation can occur if the project is the result of specific people being promised as part of a competitive proposal

if the project is dependent upon the expertise of particular persons

or if some staff assignments are defined within the project charter."

2. Syracuse University. (n.d.). PMP/CAPM Exam Prep Courseware. School of Information Studies. In the module on Project Resource Management

the course materials explain that pre-assignment is a tool and technique in the Acquire Resources process

often necessary when specific staff are named in a contract or proposal to win the project.

Benchmarking is a data-gathering technique used in the Plan Quality Management process. It involves the comparison of actual or planned project practices, processes, and quality standards to those of comparable projects or organizations. The primary purpose is to identify best practices, generate ideas for improvement, and establish a basis for measuring performance. This process helps the project team set realistic and achievable quality goals by learning from the successes and failures of others, which directly aligns with the activity described in the question.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Project Management Institute. Section 8.1.2.3

Data Gathering

p. 280. The text states

"Benchmarking. Benchmarking involves comparing actual or planned project practices or the project’s quality standards to those of comparable projects to identify best practices

generate ideas for improvement

and provide a basis for measuring performance."

2. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Project Management Institute. Section 4.2.3

Models

p. 160. This edition defines benchmarking as "A comparison of an organization’s or project’s performance to the performance of other organizations or projects in the same or a different industry."

3. Eppinger

S. D. (2001). Benchmarking in Project Management. MIT Sloan School of Management. MIT Sloan Working Paper 4192-01. This paper defines benchmarking as "the process of identifying

understanding

and adapting outstanding practices from other organizations to help your organization improve its performance."

A project lifecycle is the series of phases that a project passes through from its initiation to its closure. These phases provide the fundamental framework for managing the project. While the names and number of phases are determined by the management and control needs of the organization(s) involved, they are typically sequential. However, in some project situations, phases can overlap to compress the schedule, a practice known as fast-tracking. This structure of sequential and sometimes overlapping phases is the core definition of a project lifecycle.

1. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Project Management Institute. Section 2.5.2

Development Approach and Life Cycle Performance Domain

p. 53.

2. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Project Management Institute. Section 1.2.4.1

Project Life Cycle

p. 19.

3. Shenhar

A. J.

& Dvir

D. (2007). Reinventing Project Management: The Diamond Approach to Successful Growth and Innovation. Harvard Business School Press. Chapter 2

"The Project Life Cycle

" discusses the sequence of phases from start to finish.

The Perform Integrated Change Control process is responsible for reviewing all change requests, evaluating their impact, and then approving, rejecting, or deferring them. A primary output of this decision-making process is the updated status of these change requests. This status is formally recorded in the change log, which is a project document updated as part of this process. This ensures that the disposition of all change requests is communicated to relevant stakeholders.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Project Management Institute. Section 4.6

Perform Integrated Change Control

p. 113.

2. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Project Management Institute. Section 4.6.3.2

Change Log

p. 120. The text states

"The status of all change requests...are recorded in the change log."

3. Vargas

R. V. (2019). Practical Guide to the PMBOK® Guide (6th ed.). CRC Press. This academic text

which analyzes the PMBOK

confirms that the change log

which contains the status of change requests

is an output of the Perform Integrated Change Control process. (Chapter 4

Integration Management).

A win-lose reward system creates a competitive environment where only one person or a select few can win, meaning others must lose. This structure pits team members against each other, incentivizing individual achievement often at the expense of group collaboration. Such internal competition can erode trust, hinder open communication, and create resentment, all of which are detrimental to building and maintaining team cohesiveness. The primary goal of a project team is to work collaboratively toward a common objective, a principle that win-lose rewards directly undermine.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Project Management Institute. Section 9.4.2.5

Recognition and Rewards. The guide states that rewards are effective when they satisfy a need and are valued by the individual. It emphasizes rewarding desirable behavior; a win-lose system promotes competition

which is often an undesirable behavior for team unity.

2. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Project Management Institute. Section 2.8

Team. This section emphasizes creating a "collaborative project team environment" and fostering "trust

respect

and transparent communication

" all of which are compromised by a competitive win-lose reward structure.

3. Johnson

D. W.

& Johnson

R. T. (1989). Cooperation and competition: Theory and research. Interaction Book Company. Chapter 3

"Interpersonal Interaction: The Basic Unit of Social Life

" details how competitive (win-lose) goal structures promote opposition and obstructiveness among individuals

whereas cooperative structures promote mutual assistance and support

which are essential for cohesiveness.

A process is officially defined as a set of interrelated actions and activities performed to create a pre-specified product, service, or result. Each process is characterized by its inputs, the tools and techniques that can be applied, and the resulting outputs. Project management itself is accomplished through the application and integration of various project management processes, which are logically grouped into Process Groups (e.g., Initiating, Planning, Executing, Monitoring and Controlling, and Closing). The question provides the exact definition of a process as used by the Project Management Institute (PMI).

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Project Management Institute. Glossary

p. 715. The entry for "Process" states: "A set of interrelated actions and activities performed to create a pre-specified product

service

or result."

2. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Project Management Institute. Glossary

p. 248. The definition for "Process" remains consistent: "A set of interrelated actions and activities performed to create a prespecified product

service

or result."

3. Shenhar

A. J.

& Dvir

D. (2007). Reinventing Project Management: The Diamond Approach to Successful Growth and Innovation. Harvard Business School Press. Chapter 2

"The Traditional Scope-Triangle-Process (STP) Approach

" discusses how projects are executed through a series of processes.

4. MIT OpenCourseWare. (2012). 1.040/1.401/ESD.054J Project Management

Fall 2012. Massachusetts Institute of Technology. Lecture 2 notes distinguish between projects

programs

and portfolios

defining a project as a temporary endeavor that is accomplished via a series of processes.

The risk response strategy described is Transfer. This strategy involves shifting the ownership of a threat to a third party to manage the risk and bear the impact if it occurs. By outsourcing the development of a specific part of the system, the project team is transferring the responsibility and potential negative consequences of the talent-gap risk to the external vendor. The vendor, through a contractual agreement, now assumes the risk associated with delivering that component successfully. This does not eliminate the risk but moves the direct responsibility for its management.

1. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition. Section 2.8.3.2

"Responses to Threats

" p. 103. The guide defines Transfer as a strategy for threats where ownership and impact are shifted to a third party

with outsourcing being a common example.

2. Project Management Institute. (2021). The Standard for Project Management (ANSI/PMI 99-001-2021). Section 2.8

"Uncertainty

" p. 53. This standard outlines that dealing with uncertainty involves selecting and implementing appropriate strategies to address risks

such as transferring them.

3. MIT OpenCourseWare. (2006). 1.040J / ESD.051J Project Management

Fall 2006. Lecture 10: Risk Management

Slide 21. This university material defines the "Transfer" strategy for threats as shifting risk to a third party through mechanisms like contracts

which is the basis of outsourcing.

The Procurement Statement of Work (SOW) is a formal document that provides a narrative description of the products, services, or results to be supplied under a contract. It is specifically developed from the project scope baseline, which includes the WBS, WBS dictionary, and project scope statement. The SOW's purpose is to define only the specific portion of the project's scope that will be performed by a seller. This ensures that potential sellers have a clear, complete, and concise understanding of the work required, allowing them to determine if they can meet the requirements and to prepare an appropriate response.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Section 12.1.3.1

Procurement Statement of Work. Newtown Square

PA: Project Management Institute. "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."

2. MIT OpenCourseWare. (2012). ESD.36J System Project Management

Lecture 11: Project Execution: Procurement & Contracts. Massachusetts Institute of Technology. This courseware explains that the SOW is a critical procurement document that details the specific work to be performed by a contractor

derived from the project's overall requirements and scope.

Resource leveling is a schedule optimization technique applied after the initial schedule is created using the critical path method (CPM). Its primary purpose is to resolve resource over-allocations or shortages by adjusting the schedule. When resources are critically constrained, resource leveling will delay activities (even critical ones) until the required resources are available. This process often changes the original critical path and extends the project's overall duration to create a feasible schedule based on resource availability.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Section 6.5.2.4

Resource Optimization. "Resource leveling. A resource optimization technique in which adjustments are made to the project schedule to optimize the allocation of resources and which may affect the critical path."

2. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Section 4.3

Models. This section lists scheduling models which include the critical path method and resource optimization techniques (leveling and smoothing) as methods used in project management.

3. Vanhoucke

M. (2012). Project Management with Dynamic Scheduling: Baseline Scheduling

Risk Analysis and Project Control. Springer Science & Business Media. Chapter 3

Section 3.1

"The Resource-Constrained Project Scheduling Problem". This academic text discusses how resource leveling is a primary method to address resource constraints after an initial schedule

such as one derived from CPM

is established. (DOI: https://doi.org/10.1007/978-3-642-25175-7)