Schedule Monitoring and Control

Correct Answer: The project team is prioritizing critical path tasks at the expense of other work

An SPI of 1.2 for critical path activities and 0.8 for non-critical activities reveals a significant pattern in project execution: The team appears to be focusing their efforts on critical path tasks (performing 20% ahead of schedule) while letting non-critical tasks fall behind (performing at 80% of planned progress). This situation clearly indicates that the project team is making a conscious choice to prioritize critical path activities over other work. The resource allocation baseline suggestion is incorrect because the pattern reflects an intentional management strategy rather than a baseline issue. The enhanced productivity answer is incorrect because the pattern shows uneven performance, not overall optimization. The schedule compression techniques answer is incorrect because effective compression would show improved performance across all activities, not just the critical path.

Correct Answer: The project baseline schedule needs to be reviewed and updated

When critical path activities show positive float, this is a clear indication that the baseline schedule needs to be reviewed and updated. Here's why: By definition, critical path activities should have zero float. If they're showing positive float, it means: 1. The network logic is no longer accurate 2. The baseline schedule has become outdated 3. The true critical path may have shifted Why other answers are incorrect: Being ahead of schedule doesn't necessarily relate to critical path activities showing float - this is a logic issue, not a progress issue. Progressive elaboration of network relationships isn't the core issue - the problem is that the existing baseline no longer reflects reality. Schedule compression opportunities aren't indicated by positive float on critical path activities - compression is about reducing duration, while this situation indicates a fundamental schedule logic problem.

Correct Answer: Perform a detailed schedule analysis and implement fast tracking where feasible

When the SPI is consistently below 1.0 (in this case 0.85), it indicates the project is behind schedule. An SPI of 0.85 means the project is only completing 85% of the planned work. The best course of action is to first analyze the schedule in detail to understand the root causes of the delays and then implement fast tracking where possible. This approach is methodical and analytical, addressing the core issue rather than just throwing resources at the problem. Other options are less appropriate because: Simply increasing resources and extending working hours is reactive and may lead to increased costs and potential quality issues. Requesting additional budget to accelerate activities is premature more expensive than necessary before analyzing the situation. Applying schedule compression to all remaining activities is too broad and may affect activities that are not causing the delay, potentially creating new problems.