Download Latest PMI-RMP Questions

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.

PMBOK® Guide1, Project interdependency management2, Interdependencies among projects in project portfolio management3, Mastering PMI-RMP Domains, Tasks, and Enablers for Effective Risk4

According to the PMBOK® Guide, a scope change request is a formal proposal to modify any project document, deliverable, or baseline. It is an output of the Perform Integrated Change Control process, which is the process of reviewing all change requests, approving changes, and managing changes to the deliverables, organizational process assets, project documents, and the project management plan. A scope change request may introduce new risks or affect existing risks on the project, which may impact the project objectives, such as scope, schedule, cost, and quality.

The risk manager should support the project manager with the scope change request by evaluating any new risks that are introduced due to the change in scope. This is because the risk manager is responsible for planning, implementing, and monitoring the risk management activities on the project, as well as communicating and reporting the risk information to the project manager and other stakeholders. The risk manager should use the appropriate risk identification and analysis techniques, such as brainstorming, interviews, checklists, SWOT analysis, cause and effect diagrams, probability and impact assessment, etc., to identify and evaluate the new risks that may arise from the scope change. The risk manager should also document the new risks in the risk register, which is a project document that contains the details of all identified individual project risks and other relevant information.

The other options are not valid for what the risk manager should do to support the project manager with the scope change request:

Update the risk management plan to reflect the scope change: This is not a valid option because the risk management plan is a component of the project management plan, which describes how risk management activities will be structured and performed on the project. It is an output of the Plan Risk Management process, which is the process of defining how to conduct risk management activities for a project. The risk management plan should not be updated to reflect the scope change, but rather to reflect any changes in the risk management approach, methodology, roles and responsibilities, budget, timing, risk categories, definitions, reporting formats, etc. The risk management plan should be updated only when there is a change in the risk management process, not in the project scope.

Reassess the identified risks that impact the project scope: This is not a valid option because reassessing the identified risks that impact the project scope is part of the Monitor Risks process, which is the process of implementing risk response plans, tracking identified risks, monitoring residual risks, identifying new risks, and evaluating risk process effectiveness throughout the project. The risk manager should not reassess the identified risks that impact the project scope before evaluating any new risks that are introduced due to the change in scope. The risk manager should first identify and analyze the new risks, and then reassess the existing risks to determine if they are still valid, relevant, and prioritized.

Update the risk register to identify, analyze, and plan a response for any new risk: This is not a valid option because updating the risk register to identify, analyze, and plan a response for any new risk is a combination of several risk management processes, such as Identify Risks, Perform Qualitative Risk Analysis, Perform Quantitative Risk Analysis, and Plan Risk Responses. The risk manager should not update the risk register to identify, analyze, and plan a response for any new risk in one step, but rather follow the sequential and iterative risk management processes to ensure a comprehensive and consistent risk management approach. The risk manager should also coordinate and communicate with the project manager and other stakeholders when updating the risk register, as well as obtain their approval and input.

PMBOK® Guide1, Risk Management Professional (PMI-RMP)® Cert Guide1

Residual risk refers to the remaining risk after implementing risk responses or controls. In this scenario, despite the policy requiring complex passwords and regular updates, some employees ' inability to comply increases the likelihood of password compromise. This non-compliance elevates the residual risk beyond acceptable levels. The risk manager should reassess the residual risk to determine its current status and evaluate whether additional controls or actions are necessary to mitigate the heightened threat. This reassessment ensures that the organization ' s risk management strategies remain effective and aligned with its security objectives.

PMI Risk Management Study Guide References:

The PMI-RMP Exam Preparation Study Guide defines residual risk as " the risk that remains after risk responses have been implemented, " highlighting the need for continuous monitoring and reassessment to address any changes in risk exposure.