PMI Updated CAPM Exam Questions and Answers by orlagh

According to the PMBOK® Guide (Project Management Body of Knowledge), specifically within the Project Cost Management knowledge area and the Estimate Costs process:

Activity Cost Estimates (Option A): This is the primary output of the Estimate Costs process. They are defined as quantitative assessments of the probable costs required to complete project work. These estimates can be presented in summary form or in detail and include all resources that will be charged to the project (e.g., direct labor, materials, equipment, services, facilities, and special categories such as inflation allowance or contingency costs).

Earned Value Management (Option B): This is a methodology or a tool and technique used in the Control Costs process. It integrates scope, schedule, and resources to measure project performance and progress. It is not an output consisting of initial cost assessments.

Cost Management Plan (Option C): This is an output of the Plan Cost Management process. It is a component of the project management plan that describes how the project costs will be planned, structured, and controlled. It sets the " rules " for estimation but does not contain the actual quantitative estimates for activities.

Cost Baseline (Option D): This is the approved version of the time-phased project budget. While it is built using the activity cost estimates, it represents the formal benchmark for measuring performance and includes contingency reserves, but it is a higher-level aggregation rather than the raw quantitative assessment of individual activity costs.

In the PMI framework, Activity Cost Estimates provide the granular data necessary to eventually roll up into the work package estimates, which then form the basis for the Cost Baseline.

According to the PMBOK® Guide, specifically within the Estimate Activity Durations process, the Three-Point Estimating technique (based on the Beta/PERT distribution) is used to improve the accuracy of activity duration estimates by considering uncertainty and risk.

The Components:

Optimistic ($O$): 2 months.

Most Likely ($M$): 4 months.

Pessimistic ($P$): 12 months (converted from 1 year to maintain consistent units).

The Formula: The standard Beta distribution (or PERT) formula for the expected duration ($E$) is:

$$E = \frac{O + 4M + P}{6}$$

The Calculation:

$$E = \frac{2 + 4(4) + 12}{6}$$

$$E = \frac{2 + 16 + 12}{6}$$

$$E = \frac{30}{6}$$

$$E = 5 \text{ months}$$

By using this weighted average, the project manager accounts for the fact that the pessimistic estimate (12 months) has a significant impact on the risk profile of the activity, pulling the " Expected " duration higher than the " Most Likely " duration.

Analysis of Other Options:

A. Two: This is simply the optimistic estimate; it does not account for the other variables or the weighted average.

B. Four: This is the " Most Likely " estimate. While it is the most frequent occurrence, the three-point technique is designed to look beyond just the most likely scenario to account for risk.

D. Twelve: This is the pessimistic estimate, representing the worst-case scenario rather than the calculated expected value.

According to the PMBOK® Guide, specifically within the Sequence Activities process of Project Schedule Management, the Precedence Diagramming Method (PDM) is a technique used for constructing a schedule model in which activities are represented by nodes and are graphically linked by one or more logical relationships to show the sequence in which the activities are to be performed.

Finish-to-Start (FS): This is the most commonly used type of precedence relationship. In this relationship, a successor activity cannot start until a predecessor activity has finished.

Example: The " Install Hardware " (Successor) activity cannot start until the " Build Foundation " (Predecessor) activity is finished.

Logical Significance: FS relationships are the default in most project management software because they represent the most intuitive and frequent flow of work in both traditional and agile projects.

Comparison with other options:

A. Start-to-start (SS): A successor activity cannot start until a predecessor activity has started. This is often used for overlapping activities but is less common than FS.

B. Start-to-finish (SF): A successor activity cannot finish until a predecessor activity has started. This is the least commonly used relationship and is rarely seen in standard project schedules.

D. Finish-to-finish (FF): A successor activity cannot finish until a predecessor activity has finished. This is used when activities must conclude at the same time (e.g., " Documentation " cannot finish until " Coding " finishes).

According to the PMBOK® Guide, specifically within the Manage Quality process (Executing Process Group), a Quality Audit is a structured, independent process used to determine if project activities comply with organizational and project policies, processes, and procedures.

Identifying Inefficiencies: The primary objective of a quality audit is to identify inefficient and ineffective policies, processes, and procedures being used on the project. It looks for " non-conformance " and " gaps " in how the work is being performed.

Process Improvement: By identifying these inefficiencies, the audit provides the necessary data to recommend Corrective Actions or Preventive Actions. It aims to share good practices used in other projects and improve the implementation of processes to help the team raise productivity.

Reduced Cost of Quality: Regular quality audits help reduce the overall cost of quality by catching process errors early, thereby reducing rework and increasing the probability of stakeholder acceptance of the final product.

Independent Review: These audits are usually conducted by an external party (such as the internal audit department, a Project Management Office (PMO), or a third-party consultant) to ensure objectivity and technical compliance.

Comparison with other options:

A. Scope audits: This is not a standard PMI term for identifying process inefficiencies. While " audits " exist in procurement or risk, " scope audits " generally refer to verifying deliverables (Validate Scope) rather than analyzing organizational procedures.

B. Scope reviews: These are meetings held during Validate Scope to obtain formal acceptance of completed deliverables from the customer. They focus on the product, not the internal processes of the organization.

D. Control chart: This is a tool used in Control Quality to determine whether or not a process is stable or has predictable performance. While it tracks variance in data, it is a mathematical tool for monitoring stability, not a qualitative review of " ineffective policies. "