PDF PMI-RMP Study Guide

According to the PMI Risk Management Professional (PMI-RMP)® Examination Content Outline1, one of the tasks in the domain of Risk Identification is to review the stakeholder register and stakeholder engagement plan to communicate and solicit stakeholder input on risks throughout the project life cycle1. The stakeholder register is a project document that identifies the project stakeholders, their roles, interests, expectations, influence, and communication requirements2. The stakeholder engagement plan is a component of the project management plan that describes the strategies and actions to promote productive involvement of stakeholders in project decision making and execution3. In this scenario, the risk manager should review these documents to address the concerns of some stakeholders who are complaining that their opinions were not considered in the risk identification process. The risk manager should communicate with the stakeholders according to their preferences and needs, and solicit their input on the project risks using various tools and techniques, such as interviews, surveys, brainstorming, etc. The risk manager should also update the stakeholder register and stakeholder engagement plan as needed to reflect any changes in the stakeholder community or their expectations. The risk manager should not refer to the requirements documentation to confirm stakeholder requirements as they relate to risks, because that is not a direct way to address the stakeholders’ concerns, and it may not capture all the potential risks that the stakeholders may identify4. The risk manager should not refer to the project charter to find guidelines and stakeholder communication channels, because the project charter is a high-level document that does not provide detailed information on how to communicate and engage with the stakeholders5. The risk manager should not rewrite the risk register to include the additional possible risks and inform the stakeholders, because that is a premature and presumptuous action that may not reflect the actual views and inputs of the stakeholders, and it may create more confusion and dissatisfaction among them6. References: 1: PMI Risk Management Professional (PMI-RMP)® Examination Content Outline, page 82: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 5133: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 5184: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 1525: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 776: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 414.

Documenting the results of the risk monitoring and controlling process is important for creating lessons learned. This helps future projects by providing a reference for risk management practices and experiences.

The documentation of the results of monitoring and controlling risks is a valuable source of information for lessons learned. Lessons learned are the documented information that reflects both the positive and negative experiences of a project. They represent the organization’s commitment to project management excellence and the project manager’s opportunity to learn from the actual experiences of others. By documenting the results of monitoring and controlling risks, the project team can capture the effectiveness of the risk responses, the changes in the risk exposure, the root causes of the risks, the best practices and the lessons learned for future projects. This documentation can help to improve the risk management process, enhance the project performance, and increase the organizational knowledge base. References: PMI Risk Management Professional (PMI-RMP) Examination Content Outline and Specifications1, page 10; A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 406; Lessons learned - PMI.

The risk manager should choose to exploit opportunities, as this response aims to maximize the positive effects of opportunities, which can help recover the project's contingency reserve and profit margin.

Exploit is a positive risk response strategy that aims to ensure that the opportunity is realized 1. It involves eliminating the uncertainty associated with a particular upside risk and making it happen 2. For example, if there is an opportunity to reduce the project cost by using a cheaper supplier, the project manager can exploit it by signing a contract with the supplier and securing the savings. Exploit is the opposite of avoid, which is a negative risk response strategy that seeks to eliminate the threat or protect the project from its impact 2.

The other options are not appropriate for taking full advantage of opportunities. Mitigate is a negative risk response strategy that reduces the probability and/or impact of a threat 2. It is the opposite of enhance, which is a positive risk response strategy that increases the probability and/or impact of an opportunity 1. Accept is a risk response strategy that involves acknowledging the risk and not taking any action unless the risk occurs 2. It can be applied to both threats and opportunities, but it does not actively pursue them. Transfer is a negative risk response strategy that shifts the impact of a threat to a third party, along with ownership of the response 2. It is the opposite of share, which is a positive risk response strategy that allocates ownership of an opportunity to a third party who is best able to capture it for the benefit of the project 1.

References: 1: How To Exploit and Enhance Project Opportunities - Project Risk Coach 2 2: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 443-4451

After verifying the effectiveness of the risk responses, the next step is to close out the risk response actions and communicate the results to relevant stakeholders. This ensures that the project team and stakeholders are aware of how risks have been managed and that any lessons learned can be applied to future projects. This aligns with PMI's emphasis on communication and documentation in risk management to ensure transparency and continuous improvement​.