PMI Updated CAPM Exam Questions and Answers by ziggy

According to the PMBOK® Guide and the Standard for Project Management, the Perform Integrated Change Control process is the definitive process for reviewing all change requests, approving changes, and managing changes to deliverables, project documents, and the project management plan.

As per PMI standards, every change request—whether it involves corrective action, preventive action, defect repair, or updates to formally controlled documents—must be processed through this specific process. The key activities within this process include:

Reviewing: Assessing the change ' s impact on all project constraints (Scope, Schedule, Cost, Quality, Resources, and Risk).

Disposition: The formal decision-making step where the Change Control Board (CCB) or the Project Manager approves, rejects, or defers the change.

Communication: Ensuring that the results of the change request (disposition) are communicated to stakeholders and recorded in the Change Log.

The other options are incorrect based on the following PMI definitions:

Control Quality: This process is concerned with the correctness of deliverables and meeting the quality requirements. While it may result in a change request (for defect repair), it does not process the disposition of that change.

Control Scope: This process monitors the status of the project and product scope. Like other control processes, it may generate change requests to keep the project on track, but the actual approval happens in Integrated Change Control.

Monitor and Control Project Work: This is a high-level process used to track, review, and report the overall progress of the project. It provides the work performance reports that serve as inputs to the change control process but does not handle the disposition of individual changes.

As per the PMI Lexicon of Project Management Terms, Perform Integrated Change Control ensures that no change is made to the project ' s baselines without a formal assessment and approval, maintaining the integrity of the project plan.

According to the PMBOK® Guide and the PMI Lexicon of Project Management Terms, the definition of risk is centered on the concept of " uncertainty. "

Definition of Individual Project Risk: An uncertain event or condition that, if it occurs, has a positive or negative effect on one or more project objectives (such as scope, schedule, cost, and quality).

The " Effect of Uncertainty " : This specific phrasing— " the effect of uncertainty " —is the standard definition used by both PMI and ISO 31000. It acknowledges that risk is not just about the event itself, but how the lack of certainty regarding that event influences the ability of the organization to reach its goals.

Positive vs. Negative: Organizations view risk as a " double-edged sword. " While many people equate risk only with threats (negative), professional project management recognizes opportunities (positive risks) as well. Therefore, defining it simply as a " negative impact " (as in options C and D) is incomplete.

Organizational Risk Appetite: How an organization perceives these uncertainties depends on its Risk Appetite (the degree of uncertainty it is willing to take on) and Risk Threshold (the level of impact at which a stakeholder may have a specific interest).

Comparison with other options:

A. events that will inevitably impact...: Risk is by definition uncertain. If an event is " inevitable " (100% probability), it is no longer a risk; it is a fact or an issue that must be managed as a known constraint.

C. events which could have a negative impact...: This describes Threats. While correct in a narrow sense, it ignores the " Opportunities " side of risk management (positive risks).

D. the negative impact of undesired events...: Similar to option C, this focuses exclusively on the negative aspect. Professional project management seeks to maximize opportunities just as much as it seeks to minimize threats.

According to the PMBOK® Guide, specifically within the Manage Project Knowledge and Monitor and Control Project Work processes, the project manager uses several logs and registers to track the " health " of the project. The Issue Log is the specific document designed to track problems and ensure accountability for their resolution.

An issue is defined as a current condition or situation that may have an impact on the project objectives (unlike a risk, which is a future event). The Issue Log is a project document where all the issues are recorded and tracked.

Accountability: It specifically identifies the owner (the person responsible for resolving the issue).

Target Dates: It includes a " target date " or " resolution date " to ensure the problem does not linger and impact the schedule.

Status Tracking: It monitors the current status (Open, In Progress, Resolved, or Closed) and the final resolution applied.

A. Project Plan: This is a formal, approved document used to guide project execution and control. While it contains many subsidiary plans, it is a high-level strategic document, not a tracking tool for day-to-day " specific problems and concerns. "

B. Responsibility Matrix: Also known as a RACI Chart (Responsible, Accountable, Consulted, Informed), this document links work packages or activities to project team members. It tells you who is responsible for tasks, but it does not track problems (issues) or their specific resolution dates.

D. Scope Document: The Project Scope Statement describes the project scope, major deliverables, assumptions, and constraints. It defines " what " is being built, not " who " is fixing " problems " during the building process.

For the exam, it is vital to distinguish between these two:

Risk Register: Deals with uncertain future events. It contains triggers and planned responses.

Issue Log: Deals with certain current events. It contains owners and resolution dates.

According to the PMBOK® Guide, Co-location (also referred to as " tight matrix " ) is a specific tool and technique used in the Develop Project Team process.

The rationale is as follows:

Definition: Co-location involves placing many or all of the most active project team members in the same physical location to enhance their ability to perform as a team.

Purpose: The primary goal is to improve communication, reduce conflict, and help build a sense of community. By being in the same room, team members can utilize informal communication channels and develop stronger working relationships, which is the core objective of the " Develop Project Team " process.

Distinction from other processes:

Develop Human Resource Plan (Planning): Focuses on identifying roles, responsibilities, and reporting relationships.

Acquire Project Team (Executing): Focuses on gaining the human resources necessary to complete project assignments.

Manage Project Team (Executing): Focuses on tracking team member performance, providing feedback, and managing changes to optimize project performance.

While co-location may influence how a team is managed, the act of physically bringing the team together to foster development is explicitly categorized under Develop Project Team.