PMI Updated CAPM Exam Questions and Answers by stephanie

According to the PMBOK® Guide, the Direct and Manage Project Work (referred to in older versions as " Direct and Manage Project Execution " ) is the process of leading and performing the work defined in the project management plan and implementing approved changes to achieve the project ' s objectives.

Outputs from Planning Processes: This is a major input to this process. Because the execution phase is where the project team carries out the work, they must use the various plans and baselines developed during the planning processes to guide their actions. This includes the project management plan itself, which integrates all subsidiary plans (Scope, Schedule, Cost, etc.) and baselines.

The Nature of Execution: Execution is where the " plan " meets " action. " Therefore, the primary driver for what work is performed, how it is performed, and what the standards are, comes directly from the outputs produced during the planning phase.

Other Key Inputs:

Project Management Plan: The comprehensive document that describes how the project will be executed.

Approved Change Requests: These are specific directives to modify the work, often resulting from the Perform Integrated Change Control process.

Organizational Process Assets (OPAs): Procedures, guidelines, and historical data.

Enterprise Environmental Factors (EEFs): Organizational culture and infrastructure.

Analysis of Other Options:

A. Performance reports: These are outputs of the Monitor and Control Project Work process. They are used to communicate status but are not the primary inputs that tell the team how to execute the work.

B. Project charter: While the Charter is the foundation of the project, it is an input to the Develop Project Management Plan and Identify Stakeholders processes. By the time the project is in the " Execution " phase, the more detailed Project Management Plan has superseded the high-level Charter as the primary guiding document.

D. Enterprise environmental factors: While EEFs are listed as an input in many processes, PMI practice questions of this specific nature (Question 638) emphasize that " Outputs from planning processes " is the more specific and comprehensive answer, as it directly provides the " instructions " for the work being directed.

According to the PMBOK® Guide and The Standard for Program Management, a program is defined as a group of related projects, subsidiary programs, and program activities managed in a coordinated manner to obtain benefits not available from managing them individually.

Relationship and Commonality: Projects are grouped into a program when they share common outcomes or a collective capability. For example, a series of projects to develop a new satellite system (launch vehicle, satellite hardware, and ground control software) are grouped because they all contribute to the single outcome of space communication.

Synergy: Managing these projects together allows the organization to optimize the use of shared knowledge, skills, and resources. It also allows for better management of interdependencies and conflicting constraints.

Benefit Realization: The primary focus of program management is on the delivery of the " benefits " and the " collective capability " rather than just the individual project deliverables.

Comparison with other options:

A. Portfolio: A portfolio consists of projects, programs, subsidiary portfolios, and operations managed as a group to achieve strategic objectives. The components of a portfolio do not necessarily have to be related or share common outcomes; they are grouped based on strategic priority and resource allocation.

C. Selection: This refers to the process of " Project Selection, " which is a technique used to decide which projects the organization should invest in, often using net present value (NPV) or internal rate of return (IRR). It is not a grouping of active projects.

D. Sub portfolio: A sub-portfolio is a smaller grouping within a larger portfolio. While it contains projects and programs, the defining characteristic of sharing " common outcomes and collective capability " specifically points to the PMI definition of a program.

According to the PMBOK® Guide, the Monitoring and Controlling Process Group consists of those processes required to track, review, and regulate the progress and performance of the project; identify any areas in which changes to the plan are required; and initiate the corresponding changes.

Key Purpose: The primary benefit of this process group is that project performance is measured and analyzed at regular intervals, appropriate events, or when exception conditions occur, to identify and correct variances from the Project Management Plan.

Continuous Oversight: It provides the project team with insight into the health of the project and highlights any areas requiring additional attention. This includes:

Comparing actual performance against the planned performance.

Assessing performance to determine whether any corrective or preventive actions are indicated.

Reviewing and approving requested changes through the Perform Integrated Change Control process.

Ensuring that only approved changes are implemented.

Scope: This process group is not just limited to the middle of the project; it occurs throughout the entire project life cycle, from initiation through closing.

Comparison with other options:

B. Initiating: This process group is performed to define a new project or a new phase of an existing project by obtaining authorization to start. It focuses on the " Why " and " What " rather than tracking performance.

C. Planning: This group establishes the scope, objectives, and course of action required to attain the objectives. It creates the " blueprint " that the Monitoring and Controlling group will later measure against.

D. Executing: This group consists of processes performed to complete the work defined in the project management plan to satisfy the project requirements. It is about " doing " the work, whereas Monitoring and Controlling is about " checking " the work.

According to the PMBOK® Guide, specifically the Define Scope process, the Project Scope Statement is the primary output that provides a documented description of the project scope, major deliverables, and the work required to create those deliverables.

Detailed Content: While the Project Charter contains high-level information, the Project Scope Statement contains a much more detailed description of the scope components. It explicitly includes:

Product scope description: Progressively elaborates the characteristics of the product, service, or result.

Deliverables: Any unique and verifiable product, result, or capability.

Acceptance criteria: A set of conditions that is required to be met before deliverables are accepted.

Project Exclusions: Explicitly states what is excluded from the project to manage stakeholder expectations (the " out of scope " list).

Assumptions: Factors in the planning process that are considered to be true, real, or certain without proof.

Constraints: Limiting factors that affect the execution of a project, such as budget, schedule, or resources.

Comparison with other options:

A. Project charter: The charter is a high-level document. While it may contain a summary of scope and major deliverables, the " detailed " and " typical " repository for specific assumptions, constraints, and granular deliverables is the Scope Statement.

C. Scope management plan: This is a component of the Project Management Plan that describes how the scope will be defined, developed, monitored, controlled, and validated. It does not contain the actual scope itself.

D. Project document updates: This is a generic output category. While the scope statement is a project document, this option is too broad to be the correct answer for a document defined by these specific contents.