A contingency response plan helps the project manager to be prepared for unexpected situations, such as delays in equipment mobilization. This plan should outline alternative actions to take in case of such delays, minimizing the impact on the project.
According to the PMBOK Guide, a contingency response plan is a predefined action that the project team will take if an identified risk event occurs. It is part of the risk response plan, which is the output of the Plan Risk Responses process. The contingency response plan helps the project team to reduce the impact of the risk event on the project objectives, such as scope, schedule, cost, and quality. The contingency response plan should be documented in the risk register, along with the risk triggers, the assigned risk owners, and the allocated contingency reserves.
The project manager for project X should prepare a contingency response plan to avoid the situation of being dependent on the availability of critical equipment from another project, project Y. This is because the equipment mobilization is an external dependency, which is a type of inter-project dependency that occurs when a project relies on another project for a deliverable or resource. Inter-project dependencies are a source of risk for the project, as they may cause delays, conflicts, or changes in the project scope or quality. The project manager should identify, analyze, and monitor the inter-project dependencies, and plan appropriate risk responses to deal with them.
The contingency response plan for the equipment mobilization could include alternative sources of equipment, such as renting, purchasing, or borrowing from other projects or vendors. The contingency response plan could also include schedule adjustments, such as fast-tracking, crashing, or re-sequencing the activities that require the equipment. The contingency response plan should be implemented when the risk trigger occurs, such as the notification of the delay from the other project manager. The project manager should also communicate the contingency response plan to the relevant stakeholders, such as the project sponsor, customer, team members, and other project managers.
The other options are not valid for avoiding the situation in the future:
* Ask the other project manager to officially confirm the new date in writing: This is not a valid option because it does not address the root cause of the problem, which is the dependency on the equipment from another project. Asking for a confirmation in writing may help to document the issue and track the progress, but it does not prevent the situation from happening again. The project manager should plan for the possibility of delays or changes in the equipment availability, and not rely on the other project manager's promises or commitments.
* Request that the other project manager be added to relevant reports: This is not a valid option because it does not address the root cause of the problem, which is the dependency on the equipment from another project. Adding the other project manager to the relevant reports may help to improve the communication and coordination between the projects, but it does not prevent the situation from happening again. The project manager should plan for the possibility of delays or changes in the equipment availability, and not rely on the other project manager's information or updates.
* Request that the other project manager inform if any additional delays are expected: This is not a valid option because it does not address the root cause of the problem, which is the dependency on the equipment from another project. Requesting the other project manager to inform if any additional delays are expected may help to anticipate and prepare for the impact, but it does not prevent the situation from happening again. The project manager should plan for the possibility of delays or changes in the equipment availability, and not rely on the other project manager's forecasts or estimates.
References: PMBOK Guide1, Project interdependency management2, Interdependencies among projects in project portfolio management3, Mastering PMI-RMP Domains, Tasks, and Enablers for Effective Risk4