Skip to content

PMI-SP : Schedule Monitoring and Controlling (Domain 3)

PMI – PMI-SP : Certified Scheduling Professional - Domain 3 - Schedule Monitoring and Controlling

25 questionsmedium

Project schedule monitoring and controlling is the most rigorous and technically demanding phase of the project lifecycle. Representing 35% of the PMI-SP examination (approximately 53 scored questions), Domain 3 focuses on the active maintenance of the schedule model, the measurement of performance against established baselines, and the implementation of corrective actions to ensure project objectives are met. A professional scheduler must transition from the theoretical design of Domain 2 (Planning) to the objective reality of execution, using quantitative data to inform stakeholder decision-making.

1. Domain 3 Overview: The Science of Schedule Performance

Domain 3, Schedule Monitoring and Controlling, acts as the closed-loop feedback mechanism for project management. While Domain 1 establishes the strategy and Domain 2 builds the baseline, Domain 3 is where the scheduler verifies the integrity of the plan against actual progress. The core objective of this domain is to provide a “truth-based” view of the project’s health.

The performance of Domain 3 is built upon six critical tasks defined by the PMI-SP Exam Content Outline (ECO):

  • Task 3.1: Updating and reviewing project progress periodically to reflect the current reality of the work.
  • Task 3.2: Reporting on resource utilization and availability to identify and mitigate potential bottlenecks.
  • Task 3.3: Performing schedule analysis and audits to evaluate network integrity and ensure the model remains dynamic and logical.
  • Task 3.4: Identifying alternative project execution options to mitigate delays and recover the critical path.
  • Task 3.5: Establishing a new Performance Measurement Baseline (PMB) only when re-baselining is formally approved through change control.
  • Task 3.6: Maintaining an accurate schedule and facilitating forensic schedule analysis to support claims or lessons learned.

A scheduler’s failure in this domain leads to “schedule entropy,” where a once-sound baseline decays into a list of activities that no longer reflect the logical dependencies or resource constraints of the project.

2. Collecting Actual Progress Data and the Role of the Data Date

The accuracy of any schedule update is entirely dependent on the quality of the raw data collected as of the Data Date (also known as the Status Date or Report Date). This date serves as the chronological boundary: everything before the Data Date is history (actuals), and everything after the Data Date is the forecast (remaining work).

Key Data Points for Collection

To maintain absolute source fidelity in the schedule model, the scheduler must collect specific data points for every active or completed activity:

  • Actual Start (AS): The recorded date and time an activity truly began. Once an AS is entered, the activity is “in progress.”
  • Actual Finish (AF): The date the activity was completed. Entering an AF removes the activity from future logic calculations, although its historical impact remains.
  • Percent Complete: A measure of progress. Schedulers must distinguish between “Physical Percent Complete” (actual work done) and “Duration Percent Complete” (time elapsed).
  • Remaining Duration (RD): This is the most critical forecast element. It is not necessarily the original duration minus elapsed time; it is the scheduler’s current best estimate of how much longer the task will take to complete from the Data Date.

Data Integrity and the Status Cycle

Periodic updates (weekly, bi-weekly, or monthly) are essential. During the update cycle, the scheduler must ensure that no “out-of-sequence” work is hidden. If an activity starts before its predecessors are finished, the logic must be analyzed to determine if the relationship was incorrect or if the work is being performed out of sequence.

3. Updating the Schedule Model and Managing Baseline Deviations

Updating the schedule model is a two-step process: recording what has happened and re-calculating what is yet to happen. This process identifies Baseline Deviations, which are the differences between the Performance Measurement Baseline (PMB) and the current schedule model.

Maintaining the Performance Measurement Baseline (PMB)

The PMB is the approved version of the schedule that serves as the benchmark for performance. As updates occur, the current schedule will inevitably drift from the baseline.

  • Performance Measurement: Schedulers use variance analysis to compare the baseline start/finish dates to current forecast start/finish dates.
  • Re-baselining (Task 3.5): Re-baselining is not a tool to hide delays. It must only occur when there is a formal change in project scope or a significant, approved change in execution strategy. Re-baselining requires formal change control approval to maintain a traceable schedule history.
  • Current Schedule vs. Baseline: Schedulers often maintain multiple “baseline instances” to compare current performance against the original contract baseline and the most recently approved re-baseline.

4. Earned Value Management (EVM) Cost-Schedule Metrics

Earned Value Management (EVM) is the primary quantitative tool for measuring schedule and cost performance. While cost engineers focus on the financial aspects, the PMI-SP focuses on how these metrics indicate the health of the project timeline.

Foundational EVM Components

MetricDefinitionFormula/Calculation
Planned Value (PV)The authorized budget assigned to scheduled work.Planned % Complete × BAC
Earned Value (EV)The measure of work performed expressed in terms of the budget authorized for that work.Actual % Complete × BAC
Actual Cost (AC)The realized cost incurred for the work performed.Total expenditures to date
Budget at Completion (BAC)The total planned budget for the project.Sum of all PVs

Performance Indices and Variances

These metrics tell the scheduler if the project is ahead or behind and if it is efficient or inefficient.

  • Schedule Variance (SV): $SV = EV - PV$. A positive SV indicates you are ahead of the planned value; a negative SV indicates you are behind.
  • Schedule Performance Index (SPI): $SPI = EV / PV$.
    • $SPI > 1.0$: Performance is ahead of schedule (efficient).
    • $SPI < 1.0$: Performance is behind schedule (inefficient).
  • Cost Variance (CV): $CV = EV - AC$. Positive is favorable; negative is over budget.
  • Cost Performance Index (CPI): $CPI = EV / AC$.
    • $CPI > 1.0$: Cost efficiency (under budget).
    • $CPI < 1.0$: Cost inefficiency (over budget).

5. Forecasting Metrics: EAC, ETC, and VAC

Schedulers must use current performance data to predict future outcomes. This is critical for Task 3.4 (Identifying alternative execution options).

Estimate at Completion (EAC)

EAC is the total projected cost of the project at completion based on current performance. The exam requires understanding which formula to apply based on the scenario:

  1. Typical Current Rate (CPI continues): Used when current variances are seen as typical of future performance.
    • $EAC = BAC / CPI$
  2. One-Time Blip (Plan continues): Used when the current variance is an anomaly and future work will follow the original plan.
    • $EAC = AC + (BAC - EV)$
  3. Pessimistic Rate (CPI and SPI driven): Used when both cost and schedule performance impact the remaining work.
    • $EAC = AC + [(BAC - EV) / (CPI \times SPI)]$

Secondary Forecasting Metrics

  • Estimate to Complete (ETC): How much more money/time is needed? $ETC = EAC - AC$.
  • Variance at Completion (VAC): The projected final variance. $VAC = BAC - EAC$. A positive VAC is a projected surplus; a negative VAC is a projected deficit.

6. The To-Complete Performance Index (TCPI)

The TCPI is a comparative metric that indicates the level of efficiency required to reach a specific financial or temporal goal (either the original BAC or a revised EAC).

TCPI Calculations

  • To meet the original Budget (BAC):
    • $TCPI = (BAC - EV) / (BAC - AC)$
  • To meet a revised Estimate at Completion (EAC):
    • $TCPI = (BAC - EV) / (EAC - AC)$

Interpreting TCPI

  • TCPI > 1.0: The project must perform more efficiently than it has to date to meet the target. This is often a warning sign that the target is unrealistic.
  • TCPI < 1.0: The project can afford to be less efficient than it has been and still meet the target.

7. Earned Schedule Management (ESM): Time-Based Metrics

Traditional EVM measures schedule variance in currency (e.g., “we are $5,000 behind schedule”), which can be confusing to stakeholders. Earned Schedule Management (ESM) translates these values into units of time (e.g., “we are 2 weeks behind schedule”).

Core ESM Concepts

ESM uses the Earned Schedule (ES)—the point in time when the current level of Earned Value should have been achieved.

  • Time-Based Schedule Variance [SV(t)]: $SV(t) = ES - AT$ (where $AT$ is Actual Time). This identifies how many time units the project is ahead or behind.
  • Time-Based Schedule Performance Index [SPI(t)]: $SPI(t) = ES / AT$. Like the standard SPI, a value below 1.0 indicates a time-based delay.
  • Independent Estimate at Completion [IEAC(t)]: A forecast of the total project duration based on time-efficiency.
  • Time-Based VAC [VAC(t)]: The difference between the planned duration and the IEAC(t).

ESM is particularly useful in the later stages of a project, where traditional SPI tends to gravitate toward 1.0 regardless of actual lateness, whereas SPI(t) continues to provide an accurate measure of time-performance.

8. Addressing Out-of-Sequence (OOS) Logic

A major technical hurdle in schedule monitoring is Out-of-Sequence (OOS) Progress. This occurs when an activity begins or finishes before all its predecessors are complete. This violates the intended network logic and requires the scheduler to make a methodological choice.

Management Techniques for OOS Logic

  1. Retained Logic: The remaining duration of the out-of-sequence activity cannot start until its predecessors are finished. This preserves the network integrity and reflects the original plan, even if some work was done early.
  2. Progress Override: The software ignores the predecessor logic and allows the remaining duration to be scheduled immediately after the Data Date. This reflects a “real-world” scenario where the logic was apparently unnecessary, but it can lead to dangerous assumptions about future dependencies.

Professional schedulers must analyze OOS events (Task 3.3) to determine if the project’s logic needs to be permanently modified to reflect a new execution reality.

9. Resource Leveling and Optimization Techniques

Monitoring and controlling is not just about time; it is about the resources required to execute the work (Task 3.2).

Optimization Strategies

  • Resource Leveling: This technique adjusts the start and finish dates of activities to align with resource limits (e.g., you only have two cranes but the schedule needs three). Leveling often consumes float and, if resources are severely constrained, will extend the project finish date.
  • Resource Smoothing: This technique adjusts activities within their allowable float limits. It prevents resources from being over-allocated in specific periods but does not delay the project finish date. It is less aggressive than leveling.
  • Funding Limit Reconciliation: Schedulers must ensure the planned work does not exceed the cash flow or funding limits available at any point in the project. This may require shifting non-critical activities to later periods.

10. Managing Critical Path Shifts and Recovery Actions

As progress is recorded, the Critical Path (the sequence of activities with zero total float) will inevitably shift. Task 3.4 requires the scheduler to identify options to mitigate these delays.

Schedule Compression Techniques

When a project is behind, the scheduler evaluates two primary compression methods:

  • Crashing: Adding resources to critical path activities to shorten their duration.
    • Result: Shortens schedule, but increases cost (higher AC).
    • Constraint: Schedulers must target the lowest-cost crashing options on the critical path first.
  • Fast-Tracking: Performing activities in parallel that were originally planned in sequence.
    • Result: Shortens schedule without adding direct resource costs.
    • Risk: Significantly increases the risk of rework and logic errors.

Corrective and Preventive Actions

Monitoring allows the scheduler to recommend Corrective Actions (to bring current performance back in line with the plan) or Preventive Actions (to ensure future performance does not deviate). These actions are identified through network analysis and audits (Task 3.3).

11. Schedule Conformance Index (SCI) and Health Checks

A high-quality schedule must not only be accurate but also “healthy.” Schedule health checks are formal audits (Task 3.3) used to ensure the model remains a reliable management tool.

Schedule Conformance Index (SCI)

The SCI is a metric used to measure how closely the project team is following the logic of the baseline. It compares the number of activities started/finished in the current period against those that were planned to start/finish in that same period. A low SCI suggests that the team is working “off-plan,” which undermines the predictive value of the schedule.

Network Integrity Audits

Schedulers perform regular audits to look for:

  • Dangling Logic: Activities without predecessors or successors.
  • Constraint Usage: Excessive use of “Must Start On” or “Must Finish On” constraints, which “hard-code” dates and prevent the schedule from being dynamic.
  • Negative Float: Indicates that a constraint is being violated (e.g., the activity is forecasted to finish after its mandatory deadline). Negative float is a signal for immediate corrective action.

Glossary of Key Terms

  1. Actual Cost (AC): Total costs actually incurred and recorded in accomplishing work performed during a given time period.
  2. Actual Finish Date (AF): The point in time that work actually ended on a schedule activity.
  3. Actual Start Date (AS): The point in time that work actually began on a schedule activity.
  4. Baseline: The approved version of a work product that can be changed only through formal change control procedures.
  5. Critical Path: The sequence of activities that represents the longest path through a project, which determines the shortest possible project duration.
  6. Data Date: A point in time when the status of the project is recorded; separates actual data from future forecast data.
  7. Earned Value (EV): The measure of work performed expressed in terms of the budget authorized for that work.
  8. Estimate at Completion (EAC): The expected total cost of completing all work expressed as the sum of the actual cost to date and the estimate to complete.
  9. Free Float: The amount of time that a schedule activity can be delayed without delaying the early start date of any successor.
  10. Negative Float: The amount of time by which a critical path activity misses a hard constraint or contractual deadline.
  11. Out-of-Sequence Progress: Progress recorded for an activity before its predecessors have been completed.
  12. Performance Measurement Baseline (PMB): An integrated scope-schedule-cost plan for the project work against which project execution is compared to measure and manage performance.
  13. Planned Value (PV): The authorized budget assigned to scheduled work.
  14. Remaining Duration: The time, in calendar units, required to complete a schedule activity from the Data Date.
  15. Resource Leveling: A technique in which start and finish dates are adjusted based on resource constraints with the goal of balancing demand for resources with the available supply.
  16. Schedule Conformance Index (SCI): A measure of the degree to which the actual work performed follows the logical sequence of the baseline schedule.
  17. Schedule Performance Index (SPI): A measure of schedule efficiency expressed as the ratio of earned value to planned value.
  18. Schedule Variance (SV): A measure of schedule performance expressed as the difference between the earned value and the planned value.
  19. Total Float: The amount of time that a schedule activity can be delayed or extended from its early start date without delaying the project finish date.

Short-Answer Practice Questions

1. If an activity has an Earned Value (EV) of $10,000 and a Planned Value (PV) of $12,000, what is the Schedule Performance Index (SPI), and what does it indicate?

2. Define the difference between “Retained Logic” and “Progress Override” in the context of out-of-sequence work.

3. What is the primary difference between Resource Leveling and Resource Smoothing regarding the project’s end date?

4. A project has a BAC of $100,000. Current AC is $50,000 and EV is $40,000. If future variances are expected to be typical, what is the EAC?

5. Why might a scheduler choose to use SPI(t) from Earned Schedule Management rather than a traditional SPI late in a project?

6. What data point is essential to distinguish history from the forecast in a schedule update?

7. How is Total Float calculated during a network pass?

8. What does a To-Complete Performance Index (TCPI) of 1.15 tell a project manager?

9. What is “Crashing” and what is its most common secondary effect?

10. What is indicated by an activity showing Negative Float?


Answer Key and Explanations

  1. Answer: SPI = 0.83. It indicates that the project is performing behind schedule or at only 83% efficiency compared to the plan.
    • Explanation: SPI is calculated as EV/PV ($10,000/$12,000). Any value below 1.0 represents a delay relative to the baseline.
  2. Answer: Retained logic requires predecessors to finish before the remaining work starts; Progress override ignores the logic.
    • Explanation: Retained logic maintains the network’s integrity, while progress override assumes the relationship is no longer valid for that specific task.
  3. Answer: Resource Leveling can delay the end date; Resource Smoothing does not.
    • Explanation: Leveling is driven by resource limits and consumes float, while smoothing only works within the existing float to avoid project delays.
  4. Answer: EAC = $125,000.
    • Explanation: First, calculate CPI (EV/AC = 40/50 = 0.8). Then use the typical formula: EAC = BAC / CPI ($100,000 / 0.8).
  5. Answer: Because traditional SPI always trends toward 1.0 at the end of a project, even if the project is late.
    • Explanation: Traditional SPI uses currency; once the work is done, EV eventually equals PV, hiding the lateness. SPI(t) uses time units to remain accurate.
  6. Answer: The Data Date.
    • Explanation: The Data Date acts as the status point; all progress is recorded up to this date, and all remaining work is scheduled from this date forward.
  7. Answer: Late Start (LS) - Early Start (ES) or Late Finish (LF) - Early Finish (EF).
    • Explanation: Total float is the difference between the earliest and latest an activity can occur without impacting the project completion.
  8. Answer: The project must perform at 115% efficiency to meet the target.
    • Explanation: A TCPI greater than 1.0 indicates that the team must work more efficiently than they have to date to stay within budget.
  9. Answer: Adding resources to the critical path to shorten duration; it increases project cost.
    • Explanation: Crashing is a compression technique that trades money (AC) for time, focusing exclusively on critical activities.
  10. Answer: The activity is projected to miss a mandatory constraint or contractual deadline.
    • Explanation: Negative float only occurs when the calculated finish date is later than a “hard” constraint date applied to the schedule.

Open-Ended/Design Questions

  1. Strategic Analysis: You are managing a large-scale utility framework. A key stakeholder demands a “re-baselining” of the schedule because the project is currently showing an SPI of 0.75. Explain the risks of re-baselining in this scenario and design a set of criteria that must be met before you would agree to establish a new Performance Measurement Baseline.
  2. Resource Optimization: A project team is currently over-allocated on specialized engineers. Compare the implications of using Resource Leveling versus Resource Smoothing in a high-priority project where the completion date is fixed by a regulatory body. Which would you choose and why?
  3. Forensic Evaluation: After a project finishes 3 months late, you are asked to perform a forensic schedule analysis. Detail the specific components of the schedule model you would investigate to determine if the delay was caused by unrealistic logic, resource constraints, or poor performance.
  4. Metric Integration: Contrast the insights provided by traditional EVM metrics (SV/SPI) with those provided by Earned Schedule Management [SV(t)/SPI(t)]. In what specific project scenarios would relying solely on traditional EVM lead to a failure in effective monitoring and controlling?
  5. Compression Logic: You have two options to recover a 2-week delay on the critical path: Crashing a critical activity at a cost of $50,000 or Fast-Tracking two critical activities with a 20% increased risk of rework. Design a decision-making framework to choose the optimal path, considering cost, risk, and stakeholder communication requirements.

Leaderboard

No scores saved yet. Be the first!

25 Questions — PMI – PMI-SP : Certified Scheduling Professional - Domain 3 - Schedule Monitoring and Controlling

Expand any question to reveal the correct answer and explanation.

  1. 1 A project has a $BAC$ of $\$200,000$. At the status date, the cumulative $PV$ is $\$120,000$ and the $EV$ is $\$100,000$, with an $AC$ of $\$110,000$. What is the current Schedule Performance Index ($SPI$) and the cost status of the project?

    Calculate efficiency by comparing what was earned against what was planned and what was actually spent.

    $SPI = 0.83$; over budget

    The $SPI$ is calculated as $\frac{EV}{PV}$ ($\frac{100,000}{120,000}$), and since $AC$ ($\frac{110,000}{}$) exceeds $EV$ ($\frac{100,000}{}$), the $CV$ is negative.

    • $SPI = 0.83$; under budget

      While the $SPI$ calculation is correct, the project is actually over budget because the actual costs incurred exceed the value of the work performed.

    • $SPI = 1.20$; over budget

      This value results from dividing $PV$ by $EV$, which is the inverse of the correct efficiency formula.

    • $SPI = 0.91$; under budget

      This index incorrectly uses $AC$ in the denominator for a schedule metric and misinterprets the budget status.

  2. 2 In Earned Schedule Management ($ESM$), if a project is currently at month 10 ($AT = 10$) but the work performed was planned to be finished at month 8 ($ES = 8$), what is the time-based Schedule Variance ($SV(t)$)?

    Subtract the current clock time from the point in the baseline where that value should have been achieved.

    $-2$ months

    The formula $SV(t) = ES - AT$ results in $8 - 10$, indicating the project is two months behind its temporal baseline.

    • $2$ months

      A positive variance would indicate the project is ahead of schedule, but here the earned schedule is less than the actual time.

    • $0.80$ months

      This value represents the Schedule Performance Index ($SPI(t)$) rather than the variance in time units.

    • $-0.20$ months

      This appears to be a percentage or ratio-based calculation error rather than a subtraction of time periods.

  3. 3 When updating a schedule, you find an activity has started before its predecessor finished, violating a Finish-to-Start ($FS$) relationship. If the scheduling software is set to 'Retained Logic,' how will the remaining duration of the successor be treated?

    Consider which setting prioritizes the integrity of the original plan over actual reported parallel progress.

    The remaining duration cannot resume until the predecessor is fully completed.

    Retained logic respects the original network dependencies, preventing the rest of the successor work from occurring until the logic is satisfied.

    • The remaining duration is allowed to continue in parallel with the predecessor.

      This describes the 'Progress Override' approach, which ignores the initial logic to allow parallel execution.

    • The predecessor's remaining duration is automatically reduced to match the successor's start.

      Scheduling tools do not typically alter predecessor durations based on successor progress; they adjust start/finish dates instead.

    • The $FS$ relationship is automatically converted to a Start-to-Start ($SS$) relationship.

      Logic changes must be manually performed by the team; the software only calculates dates based on existing constraints.

  4. 4 An activity has an Early Start ($ES$) of day 5, an Early Finish ($EF$) of day 10, and a Late Start ($LS$) of day 12. What is the Total Float ($TF$) for this activity?

    Find the difference between the earliest and latest possible start times for the task.

    $7$ days

    $TF$ is calculated as $LS - ES$ ($12 - 5$) or $LF - EF$, representing the delay allowed without impacting the project end date.

    • $2$ days

      This might be confused with the difference between $EF$ and $ES$, which relates to the activity's duration.

    • $5$ days

      This value represents the duration of the activity rather than the flexibility in its timing.

    • $17$ days

      This is the sum of start dates, which does not represent any standard scheduling metric or float type.

  5. 5 Which resource optimization technique is most likely to result in an extension of the overall project duration?

    Look for the method that prioritizes resource constraints over the original project deadline.

    Resource Leveling

    Leveling shifts activity dates to accommodate resource limits, often pushing work outside of available float and delaying the finish date.

    • Resource Smoothing

      Smoothing only adjusts activities within their float limits, specifically to avoid changing the project's critical path or finish date.

    • Crashing

      Crashing is a compression technique intended to shorten the project duration by adding resources, not extend it.

    • Fast-Tracking

      Fast-tracking overlaps activities to reduce the total timeline, though it increases the risk of rework.

  6. 6 A project is 50% complete with a $BAC$ of $\$500,000$. The $CPI$ is $0.80$. What is the To-Complete Performance Index ($TCPI$) required to finish the project exactly at the original $BAC$?

    Divide the remaining work by the remaining funds available in the original budget.

    $1.25$

    The formula $\frac{BAC - EV}{BAC - AC}$ involves finding $AC$ first ($EV / CPI = 250,000 / 0.8 = 312,500$); thus, $\frac{250,000}{187,500} = 1.33$ (Wait, re-calculating: $500k - 250k / 500k - 312.5k = 250 / 187.5 = 1.33$).

    • $0.80$

      This is the current efficiency, but $TCPI$ must be higher than current performance if the project is currently over budget.

    • $1.00$

      This represents standard performance, but a project currently over budget requires superior efficiency to return to the original baseline.

  7. 7 According to the Practice Standard for Scheduling, what is a critical consequence of performing a project re-baseline?

    Think about how a reset of the 'benchmark' affects the visibility of previous delays or overruns.

    Past performance statistics are essentially zeroed out from that point forward.

    A re-baseline accepts all completed work as 'on schedule,' meaning previous variances no longer factor into future performance indicators.

    • The original baseline must be deleted to prevent confusion with the new one.

      Good practice dictates archiving the original baseline for historical and forensic purposes, never deleting it.

    • The $SPI$ and $CPI$ will automatically improve due to the reduction in scope.

      Re-baselining reflects a change in the plan, not necessarily a change in scope, and metrics reset based on the new targets.

    • Resource leveling must be disabled to maintain the integrity of the new baseline.

      Resource leveling remains a valid optimization tool regardless of which baseline instance is currently active.

  8. 8 Your schedule analysis reveals several 'Virtual Open Ends.' Which situation most likely caused this health issue?

    Identify a relationship type that triggers the start of a task but fails to constrain its completion.

    Activities linked only with Start-to-Start ($SS$) relationships where the predecessor has started.

    Once the $SS$ lag is satisfied, the successor has no driving logic to finish, causing it to 'float' based only on the data date.

    • The lack of any start or finish milestones for the entire project model.

      This causes traditional open ends (omissions), whereas virtual open ends are caused by specific logic types during updates.

    • Using a project calendar that does not account for weekend work.

      Calendars affect date calculations but do not inherently create logical 'dangling' activities in the network.

    • Implementing a mandatory 'Must Finish On' constraint on every milestone.

      Hard constraints restrict movement and can create negative float, but they do not remove driving logical predecessors.

  9. 9 During a status update, a scheduler notices that the Total Float ($TF$) for the critical path has changed from $0$ to $-5$ days. What does this transition fundamentally indicate?

    Consider the feasibility of a schedule when the 'slack' becomes a deficit.

    The project dates are no longer feasible without modifying the plan or resources.

    Negative float implies that the logic and durations currently in the model cannot meet the required project finish date or constraints.

    • The project is now ahead of schedule by 5 days.

      Positive float indicates a project is ahead or has flexibility; negative float always indicates a delay against requirements.

    • A new critical path has been found that is shorter than the original.

      A shorter path would increase float or keep it at zero; it would not drive the value into negative territory.

    • The resource leveling algorithm has successfully optimized the schedule.

      Successful leveling resolves overallocations; if it results in negative float, the resources are still insufficient to meet the deadline.

  10. 10 A project manager analyzes the $SPI$ at month 3 and finds it is $0.75$. Based on the provided guidelines, what is the best interpretation of this trend?

    Consider the reliability of early project efficiency metrics for forecasting the ultimate outcome.

    Early $SPI$ is a strong predictor of final performance and requires immediate recovery planning.

    Historical data suggests that efficiency trends established in the first third of a project are difficult to reverse without significant intervention.

    • The project will likely recover naturally as team velocity increases in later phases.

      Performance rarely improves on its own; assuming natural recovery often leads to failure to address root causes.

    • The schedule is ahead of target because the $SPI$ is a positive number.

      An $SPI < 1.0$ is an unfavorable indicator, signifying that work is being completed slower than planned.

    • The project is over budget because the index is less than 1.

      $SPI$ is a schedule efficiency metric; cost overruns are measured by the $CPI$ or Cost Variance ($CV$).

  11. 11 In the context of the Critical Path Method ($CPM$), what is the formula for calculating Free Float ($FF$) in a 0-start format?

    Identify the gap between the end of one task and the start of the very next one.

    $FF = \min(ES_{successor}) - EF_{current}$

    This calculates the gap between the earliest start of any following activity and the completion of the current task.

    • $FF = LS - ES$

      This formula defines Total Float ($TF$), which relates to the project end date rather than the immediate successor's start.

    • $FF = EF - ES$

      This calculates the duration of the activity itself, not the flexibility or slack available in the schedule.

    • $FF = \max(LF_{successors}) - EF_{current}$

      Using Late Finish instead of Early Start would misidentify the immediate impact on successor timing.

  12. 12 If a scheduler uses 'Crashing' to recover a project that is behind schedule, what is the primary risk involved?

    Focus on the trade-off between time and resources when 'buying' schedule speed.

    Increased project expenditures.

    Crashing specifically involves adding resources to the critical path, which directly raises the total cost of the project.

    • Significant risk of rework due to parallel tasking.

      This risk is primarily associated with 'Fast-Tracking,' where sequential tasks are performed concurrently.

    • A reduction in the number of critical path activities.

      Crashing often results in more activities becoming critical as their float is consumed by the accelerated timeline.

    • Lowering the Schedule Performance Index ($SPI$).

      Crashing is intended to improve the $SPI$ by increasing the rate at which work is earned ($EV$).

  13. 13 A scheduler identifies an activity as a 'Driving Resource.' What does this mean for the schedule model?

    Think about which resources determine how long a task actually takes.

    The resource availability directly controls the duration of the associated activities.

    Driving resources are those that dictate the pace of work; their limits must be considered during resource leveling algorithms.

    • The resource is only assigned to activities on the critical path.

      Driving resources can be assigned anywhere, but they are identified specifically for their impact on task duration.

    • The resource has the highest hourly rate in the project budget.

      Being a 'driving' resource is a temporal and logical concept, not a financial classification.

    • The resource is authorized to approve all baseline changes.

      Approval authority is part of governance/stakeholder management, not the technical definition of a driving resource in the tool.

  14. 14 Which Earned Value metric should a scheduler prioritize to identify if the project is executing work efficiently relative to the plan, regardless of the budget?

    Look for a ratio-based indicator focused on the timeline.

    $SPI$

    The Schedule Performance Index measures efficiency by comparing work performed ($EV$) to work scheduled ($PV$).

    • $CPI$

      The Cost Performance Index measures financial efficiency, not how well the timeline is being followed.

    • $SV$

      While $SV$ measures schedule, it is a nominal value in currency or hours, whereas indices provide a relative measure of efficiency.

    • $EAC$

      The Estimate at Completion is a forecast of final costs, not a measurement of current schedule execution efficiency.

  15. 15 A project is reported behind schedule. What is the scheduler’s appropriate first step according to standard recovery planning?

    Determine the necessary diagnostic action before taking corrective steps.

    Analyze schedule variance against the baseline to find the cause and affected critical path.

    Diagnosis must precede the cure; the scheduler must understand the root cause before selecting a compression technique.

    • Immediately apply Crashing to all activities in the next phase.

      Crashing should only be applied to critical path activities and only after analyzing cost efficiency.

    • Re-baseline the project to hide the current delays from stakeholders.

      Re-baselining should only be done for significant scope changes or when the current plan is no longer a valid management tool.

    • Move resources from the critical path to non-critical activities.

      This would likely worsen the delay, as the critical path determines the project's overall duration.

  16. 16 In a Start-to-Start ($SS$) relationship with a $+3$ day lag, when can Activity B start?

    Identify the specific trigger point for the lag in this dependency type.

    Three days after Activity A has started.

    An $SS$ lag is calculated from the start of the predecessor, imposing a delay on the start of the successor.

    • Three days after Activity A has finished.

      This describes a Finish-to-Start ($FS$) relationship with a 3-day lag.

    • Three days before Activity A finishes.

      This would be described as a Finish-to-Finish ($FF$) relationship with a $-3$ day lead.

    • Three days after the project start date, regardless of Activity A.

      Relationships are relative to other activities; only constraints like 'Start No Earlier Than' are fixed to dates.

  17. 17 Which of the following is a key reason for using 'Activity Log Notes' during schedule maintenance?

    Consider the value of qualitative data in understanding historical schedule deviations.

    To reconstruct the context of why specific tasks were delayed or logic was changed.

    Logs provide a historical audit trail, which is essential for lessons learned and defending actions during schedule forensics.

    • To replace the need for a formal configuration management plan.

      Notes are a component of the plan, not a substitute for the overall procedures for tracking and traceability.

    • To store the personal contact information of the project team members.

      Schedule logs should focus on technical and procedural data relevant to the schedule model's execution.

    • To automatically calculate the Earned Value of the activity.

      Earned Value is a calculated numeric field; notes are qualitative data fields used for documentation.

  18. 18 A scheduler uses a 120-day baseline. At day 60, $PV$ is 60 days and $EV$ is 45 days. What is the $SPI$ and what does it tell us?

    Divide the value earned by the value that was planned for that time period.

    $SPI = 0.75$; the project is accomplishing 75% of the planned work.

    $SPI$ is $EV / PV$ ($45 / 60 = 0.75$), indicating a significant inefficiency in schedule execution.

    • $SPI = 1.33$; the project is ahead of schedule.

      This results from dividing $PV$ by $EV$, which is the incorrect formula for an efficiency index.

    • $SPI = 0.75$; the project is under budget by 25%.

      $SPI$ relates to schedule progress; budget performance is measured by the $CPI$.

    • $SPI = -15$; the project is 15 days behind schedule.

      This is the Schedule Variance ($SV$), not the Performance Index ($SPI$).

  19. 19 Why is it discouraged to rely solely on a scheduling tool to resolve Out-of-Sequence ($OOS$) logic?

    Consider the role of human expertise in validating project dependencies.

    Only the project team can determine if the original logic was incorrect or needs adjustment.

    Tools apply algorithms (like retained logic), but human judgment is needed to decide if a dependency should be removed or decomposed.

    • Tools are unable to calculate dates once $OOS$ logic is introduced.

      Tools will still calculate dates using specific overrides, but the results may not be valid for project management.

    • The tool will automatically delete the predecessor activity to fix the error.

      Software does not delete user data; it simply flags the violation of assigned logical relationships.

    • Manual resolution is required by PMI to maintain certification status.

      This is a best practice for model integrity, not a regulatory requirement for individual certification.

  20. 20 What is the primary difference between 'Schedule Variance ($SV$)' and 'Schedule Variance in Time ($SV(t)$)'?

    Look at the unit of measurement used in the two different management methodologies.

    $SV$ is measured in monetary units, while $SV(t)$ is measured in time units.

    EVM traditionally uses cost-based values for schedule metrics, whereas ESM provides a variance expressed directly in days or months.

    • $SV$ measures cost overruns, while $SV(t)$ measures schedule delays.

      $SV$ and $SV(t)$ are both schedule metrics; cost overruns are measured by $CV$ (Cost Variance).

    • $SV$ is used for predictive projects, while $SV(t)$ is only used for Agile projects.

      Both are applicable to predictive models to enhance the accuracy of timeline tracking and forecasting.

    • $SV$ is a ratio, while $SV(t)$ is an absolute number.

      Both variances are absolute values (subtraction); their corresponding indices ($SPI$ and $SPI(t)$) are the ratios.

  21. 21 You are auditing a subcontractor's schedule and find a task with a 20-day lag between two finish-to-start activities. Why is this considered a risk?

    Think about the visibility of uncertainty in 'invisible' time delays.

    Risk can consume or extend fixed lags with unanticipated consequences to duration.

    Lags are 'hidden' time; it is better to model them as discrete activities to track their specific risks and uncertainties.

    • Lags automatically create negative float in the network.

      Lags delay successors but only create negative float if the delay exceeds the available project time.

    • Lags are forbidden by the Practice Standard for Scheduling.

      Lags are allowed but should be used sparingly and modeled as activities whenever possible.

    • A lag increases the $SPI$ of the project artificially.

      Lags do not earn value ($EV$); they only affect the timing of when future work can be started ($PV$).

  22. 22 If a project has an $SPI < 1.0$ and a $CPI > 1.0$, what is the most likely status of the project?

    Interpret the meaning of a value less than one and a value greater than one in performance ratios.

    Behind schedule but under budget.

    The schedule index indicates inefficiency ($<1.0$), while the cost index indicates efficiency ($>1.0$).

    • Ahead of schedule but over budget.

      This would require an $SPI > 1.0$ and a $CPI < 1.0$.

    • Behind schedule and over budget.

      This would require both the $SPI$ and the $CPI$ to be less than 1.0.

    • Ahead of schedule and under budget.

      This would require both efficiency indices to be greater than 1.0.

  23. 23 A scheduler identifies 'Near-Critical Paths' during the monitoring phase. Why is this a 'high-difficulty' monitoring task?

    Consider the risk of non-critical activities delaying the project.

    Paths with minimal float are susceptible to becoming the critical path with slight perturbations.

    Vigilant monitoring is required because a small delay on a near-critical path can shift the entire project's completion date.

    • Near-critical paths are required by law to have their own $SPI$ calculation.

      Indices are usually calculated at the project or work package level, not for every specific logical path.

    • The critical path method assumes only one path can ever exist.

      Projects often have multiple paths, including several that are critical or nearly critical.

    • Near-critical paths do not contain any Earned Value.

      All activities in the WBS that are in the schedule model have planned and earned value.

  24. 24 What happens to the $SPI$ as a project reaches 100% completion?

    Think about the behavior of a ratio when the numerator and denominator finally become equal.

    It will inevitably move toward 1.0, losing its predictive value.

    As $EV$ eventually equals $PV$ at the end of a project, the $SPI$ becomes 1.0 even if the project finished very late.

    • It becomes the best indicator of the project's final time delay.

      Traditional $SPI$ fails to show late completion; time-based metrics like $SPI(t)$ are needed for that purpose.

    • It drops to $0.0$ once the final activity is archived.

      The index converges to 1.0 because all planned work has finally been earned.

    • It is replaced by the $CPI$ as the only valid metric.

      While cost performance remains important, schedule performance tracking at completion uses actual finish dates versus baseline.

  25. 25 When monitoring subcontractor performance, which document provides the governance and approval workflows for schedule changes?

    Identify the functional plan that sets the rules for the scheduling professional's daily work.

    Schedule Management Plan

    This plan defines the tools, thresholds, and processes used for controlling and updating the schedule model.

    • Project Charter

      The charter provides high-level authorization but does not contain detailed procedural workflows for scheduling.

    • Risk Register

      The register lists specific threats and opportunities, not the overarching governance for the schedule tool.

    • Issue Log

      The log records current problems, whereas the management plan dictates how to handle changes to the plan.