PMI Updated CAPM Exam Questions and Answers by youssef

According to the PMBOK® Guide, specifically within the Monitor and Control Project Work process, the Schedule Performance Index (SPI) is a measure of schedule efficiency expressed as the ratio of earned value to planned value.

The Formula: The SPI is calculated using the following equation:

$$SPI = \frac{EV}{PV}$$

The Calculation:

Given Earned Value ($EV$) = $30$

Given Planned Value ($PV$) = $15$

$SPI = \frac{30}{15} = 2.0$

Interpreting the Result:

SPI > 1.0: Indicates that more work was completed than was originally planned. The project is ahead of schedule.

SPI < 1.0: Indicates that less work was completed than was planned. The project is behind schedule.

SPI = 1.0: Indicates that the project is exactly on schedule.

Context: An SPI of $2.0$ means the project team is performing at $200\%$ efficiency relative to the schedule. For every hour of work planned, two hours ' worth of work (in terms of value) has been accomplished.

Analysis of other options:

Option B (45): This is the result of adding $EV$ and $PV$ ($30 + 15$), which has no standard meaning in Earned Value Management.

Option C (0.5): This is the result of dividing $PV$ by $EV$ ($15 / 30$). This is the inverse of the SPI formula and is incorrect.

Option D (15): This is the result of $EV - PV$ ($30 - 15$), which is the formula for Schedule Variance (SV), not the index.

Per PMI standards, the Schedule Performance Index (SPI) is a critical metric for determining the efficiency of the project team ' s use of time, and in this specific case, the value of 2.0 indicates exceptionally high schedule performance.

According to the PMBOK® Guide (Project Management Body of Knowledge), specifically within the Project Schedule Management knowledge area and the Sequence Activities process, project managers use leads and lags to refine the relationships between activities:

Lead (Option A): A lead is the amount of time a successor activity can be advanced with respect to a predecessor activity. In this scenario, " Painting " is the successor to " Preparing the walls. " Usually, these might have a Finish-to-Start (FS) relationship. However, if you can start the preparation while the paint is being chosen (essentially overlapping the tasks), you are accelerating the start of the successor. This overlap is a lead, often expressed as a negative value in scheduling software (e.g., FS - 2 days).

Lag (Option B): A lag is the amount of time a successor activity will be delayed with respect to a predecessor activity. An example of a lag in this context would be waiting 24 hours for the primer to dry before applying the final coat of paint. It is a required waiting time, not an overlap.

Mandatory Dependency (Option C): Also known as " hard logic, " this is a relationship inherent in the nature of the work (e.g., you cannot paint a wall that does not exist). Choosing paint and preparing walls are not physically dependent on each other in a way that requires one to be 100% finished before the other can begin.

Internal Dependency (Option D): This involves a precedence relationship between project activities that are generally within the project team ' s control. While this scenario is an internal dependency, the specific timing mechanism described (doing them at the same time to save time) is specifically defined as a lead.

In the PMI framework, using a lead is a technique often used during Schedule Compression (specifically Fast Tracking) to shorten the overall project duration by performing activities in parallel that would normally be done in sequence.

The PMBOK® Guide (7th Edition) introduced eight Project Performance Domains, which are groups of related activities that are critical for the effective delivery of project outcomes.

Why Choice D is correct:

Defining the Work: The Planning Performance Domain involves the initial, ongoing, and evolving coordination required to deliver the project ' s products and outcomes.

Scope Breakdown: Creating the Work Breakdown Structure (WBS) is a foundational planning activity. It involves organizing and defining the total scope of the project.

Baseline Creation: The WBS is a key component of the Scope Baseline (along with the WBS Dictionary and the Project Scope Statement). You cannot accurately plan for cost, schedule, or resources without first decomposing the work into manageable work packages via the WBS.

Iterative Nature: Planning is not a one-time event; as the project progresses and more information becomes available, the WBS may be refined within this domain.

Analysis of other options:

A (Development approach and life cycle): This domain focuses on determining whether the project will use a Predictive, Adaptive, or Hybrid approach and defining the phases of the project. While this decision influences how you build the WBS, it is not the domain where the WBS itself is developed.

B (Delivery performance): This domain focuses on delivering the scope and quality that the project was undertaken to achieve. It is about the result of the work and meeting requirements, rather than the structural planning of the work.

C (Project work): This domain is associated with managing the physical and logistical aspects of the project, such as managing resources, maintaining a productive environment, and managing the flow of work. It is more about the " execution " and " monitoring " of the work rather than the hierarchical decomposition of the scope.

Key Concept: The Project Management Institute (PMI) emphasizes that the Planning Performance Domain (Choice D) is where the project team establishes the roadmap. The WBS is the structural skeleton of that roadmap, ensuring that every piece of work is accounted for so that budgets and schedules can be built with precision.

In accordance with the PMBOK® Guide (Project Cost Management), the Estimate Costs process involves developing an approximation of the monetary resources needed to complete project work. Vendor bid analysis is a recognized tool and technique used to assist in this estimation.

Function of Vendor Bid Analysis: When project deliverables are to be purchased from outside the organization, the project team can use the bids submitted by qualified vendors to help estimate what the project costs should be. This involves analyzing the various bids to determine the " should-cost " of the work based on the responses from the marketplace.

Cost Estimating Context: It provides a reality check against internal bottom-up or analogous estimates. If a vendor ' s bid is significantly different from the internal estimate, it may indicate that the project scope was misunderstood or that the internal estimate was flawed.

Other Tools and Techniques: Other primary tools in this process include Analogous Estimating, Parametric Estimating, Bottom-up Estimating, Three-Point Estimating, and Data Analysis (specifically Alternative Analysis and Reserve Analysis).

Analysis of Distractors:

A. Acquisition: This is a tool and technique used in the Acquire Resources process (Project Resource Management). it refers to the actual act of obtaining team members, facilities, equipment, or materials, rather than estimating their cost.

B. Earned value management (EVM): This is a methodology used in the Control Costs process. While it uses cost estimates as a baseline, EVM is a monitoring and controlling technique used to measure project performance and progress.

D. Forecasting: This is an output or a technique used in Control Costs to predict future cost performance (e.g., Estimate at Completion - EAC) based on current work performance data. It is not used to create the initial estimates for the project activities.