Midway through the project you received an executed change order for this project, adding thirty-three days to the contract for weather delays.
In its simplest form, how would your next project update display the changed condition?
A. After Activity 1000, add a new Activity 1050 with a start-to-start relationship to Activity 1000, and tie the end of this new activity with a finish-to-finish relationship to the final activity of the project.
B. After Activity 1000, add a new Activity 1010 with a finish-to-start relationship to Activity 1000, and tie the end of this new activity with a finish-to-start relationship to the final activity of the project.
C. After Activity 1001, add a new Activity 1011 with a finish-to-start relationship to Activity 1000, and tie the end of this new activity with a finish-to-start relationship to the final activity of the project.
Explanation:
Scenario Overview:
A change order has been approved, adding 33 days for weather delays. This requires updating the schedule to reflect the extended contract duration.
Impact on Scheduling:
The simplest and cleanest way to include the change is to create a new activity that represents the delay (e.g., Activity 1050).
The new activity is linked to Activity 1000 using a start-to-start (SS) relationship. This ensures the delay begins in parallel with the original contract start.
The finish-to-finish (FF) relationship with the final activity ensures that the extended duration impacts the project's overall timeline.
Cross-Verification with PSP Principles:
PSP principles emphasize the importance of maintaining logical integrity and clarity when updating schedules for change orders (Ref: PSP Study Guide, Chapter 2B: Schedule Maintenance/Controlling). This method ensures traceability of the delay without affecting activity logic unnecessarily.
