The PMI Risk Management Professional (PMI-RMP) Exam (PMI-RMP)

To determine whether to purchase the new component, we can perform an Expected Monetary Value (EMV) analysis for both scenarios: purchasing the component and not purchasing it.

1. Purchasing the New Component:

Probability of Success: 70% (0.7)

Profit if Successful: US$500,000

EMV of Success: 0.7 * $500,000 = $350,000

Probability of Failure: 30% (0.3)

Additional Cost if Failed: US$50,000

EMV of Failure: 0.3 * (-$50,000) = -$15,000

Cost of Component: -$100,000

Total EMV: $350,000 (success) - $15,000 (failure) - $100,000 (cost) = $235,000

2. Not Purchasing the New Component:

Probability of Failure: 80% (0.8)

Cost if Failed: US$250,000

EMV of Failure: 0.8 * (-$250,000) = -$200,000

Probability of Success: 20% (0.2)

Profit if Successful: US$0 (assuming no additional profit without the component)

EMV of Success: 0.2 * $0 = $0

Total EMV: $0 (success) - $200,000 (failure) = -$200,000

Comparing the two scenarios, purchasing the new component yields a positive EMV of $235,000, whereas not purchasing it results in a negative EMV of -$200,000. Therefore, from a risk management perspective, it is advisable to purchase the new component.

PMI Risk Management Study Guide References:

The PMI-RMP Exam Preparation Study Guide discusses the application of Expected Monetary Value (EMV) analysis in decision-making under uncertainty, providing a structured approach to evaluate potential financial outcomes.

The risk manager should update the risk register with both the opportunities and threats identified during the SWOT analysis. This will help in tracking and managing all potential risks throughout the project lifecycle.

Update the risk register with the identified risks Comprehensive and Detailed Explanation: According to the PMI Risk Management Professional (PMI-RMP)® Examination Content Outline1, one of the tasks in the domain of Risk Identification is to update the risk register with identified risks, causes, categories, and potential responses1. A risk register is a document used to track and report on project risks and opportunities throughout the project’s life cycle2. In this scenario, the risk manager should update the risk register with the identified risks, both opportunities and threats, that result from the SWOT analysis. The risk manager should also include the causes, categories, and potential responses for each risk, as well as other relevant information such as probability, impact, priority, owner, etc. The risk manager should not add only the threats to the risk register, because opportunities are also a type of risk that can have a positive effect on the project objectives and should be recorded and managed accordingly3. The risk manager should not utilize different tools to identify the risks, because the SWOT analysis is a valid and useful tool for risk identification and there is no indication that it was insufficient or inappropriate for the project context4. The risk manager should not plan risk responses to the threats, because that is a separate process that comes after risk identification and requires further analysis and evaluation of the risks5. References: 1: PMI Risk Management Professional (PMI-RMP)® Examination Content Outline, page 82: Risk Register in Project Management - Project Management Academy63: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 3974: How to Perform a SWOT Analysis - Project Risk Coach25: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 440.

In this scenario, the program manager is using the " Exploit " risk response strategy, which is aimed at ensuring that an opportunity is realized. By transferring all resources to the project and arranging for overtime pay, the program manager is taking proactive steps to ensure the project is completed early, thereby securing the large bonus. According to PMI, the " Exploit " strategy is used when the objective is to ensure that the opportunity is realized, typically involving actions that maximize the chances of achieving the desired outcome​.

When a project requires detailed and exhaustive planning to ensure the product ' s characteristics and quality, a predictive approach (also known as a waterfall approach) is the most appropriate. This approach involves planning out the project in detail upfront, including the scope, schedule, and costs, which aligns with the need for thorough planning mentioned in the scenario. The predictive approach is best suited for projects where requirements are well-understood and unlikely to change, allowing for careful management of risks through detailed plans​.

When risks are not as originally described, it ' s essential to revisit the project’s assumptions and constraints to reassess their impact and update the response plan accordingly. This step ensures that the risk management process remains accurate and relevant, allowing the project team to adapt to changing conditions effectively. PMI guidelines emphasize the importance of regularly reviewing and updating risk assessments to reflect any changes in the project ' s environment or scope​.

The project manager should consult or review project contracts, lessons learned registers from analogous projects, and the risk management plan to develop an effective risk planning for the project.

According to the PMBOK® Guide, the risk management plan is one of the key inputs for the plan risk management process, which is the first process in the project risk management knowledge area. The risk management plan describes how risk management activities will be structured and performed throughout the project. It includes information such as the methodology, roles and responsibilities, budget, timing, risk categories, definitions of risk probability and impact, probability and impact matrix, revised stakeholders’ risk tolerances, reporting formats, and tracking (page 409). Therefore, option D is the correct answer.

The project contracts are also an important input for the plan risk management process, as they may contain terms and conditions that can create or affect various project risks. For example, contracts may include clauses related to penalties, incentives, warranties, intellectual property rights, termination, force majeure, arbitration, indemnification, etc. The project manager should review the project contracts to identify any potential sources of risk and plan appropriate responses (page 410). Therefore, option A is the correct answer.

The lessons learned registers from analogous projects are another valuable input for the plan risk management process, as they provide historical information and knowledge that can help the project manager identify and analyze risks, as well as plan risk responses. The lessons learned registers may contain information such as the risks that occurred, the root causes of the risks, the risk triggers, the effectiveness of the risk responses, the residual and secondary risks, the risk owners, the risk ratings, the risk trends, etc. The project manager should consult the lessons learned registers from similar or comparable projects to learn from past experiences and avoid repeating mistakes (page 411). Therefore, option B is the correct answer.

The risk register is not an input for the plan risk management process, but an output. The risk register is a document that contains the list of identified risks, their causes, potential responses, and other relevant information. The risk register is created during the identify risks process, which is the second process in the project risk management knowledge area. The risk register is then updated and refined throughout the project as more information becomes available and new risks emerge (page 414). Therefore, option C is incorrect.

The code of regulations is not an input for the plan risk management process, but a type of enterprise environmental factor. Enterprise environmental factors are the conditions, not under the control of the project team, that influence, constrain, or direct the project. The code of regulations refers to the rules and standards that govern the project’s industry, domain, or sector. The code of regulations may affect the project’s scope, schedule, cost, quality, resources, communications, procurement, and risk management. The project manager should consider the code of regulations when planning risk management activities, but it is not an artifact that needs to be reviewed or consulted (page 38). Therefore, option E is incorrect.

According to the PMBOK Guide, one of the tools and techniques for the identify risks process is data gathering. Data gathering is the process of collecting information from various sources to identify potential risks that may affect the project objectives. Some of the data gathering techniques are brainstorming, interviews, checklists, assumption and constraint analysis, and document analysis1. To conduct a risk identification exercise using data gathering techniques, the risk manager should take the following actions:

Arrange a team meeting, review the project’s scope, and discuss dependency mapping. This action can help the risk manager to facilitate a brainstorming session with the project team and other subject matter experts, where they can generate a list of potential risks based on the project scope and the dependencies among the project activities. Dependency mapping is a technique that helps to identify the relationships and interdependencies among the project components, such as tasks, resources, deliverables, and stakeholders2. By reviewing the project scope and discussing the dependency mapping, the risk manager can ensure that the risk identification exercise covers all the relevant aspects of the project and does not miss any important risk sources.

Ensure that all the relevant stakeholders participate. This action can help the risk manager to obtain different perspectives and insights from the stakeholders who have different roles, interests, and expectations in the project. Stakeholders are individuals or groups who can affect or be affected by the project outcomes. They may have valuable information, experience, or expertise that can help to identify potential risks that may not be obvious to the project team. By ensuring that all the relevant stakeholders participate in the risk identification exercise, the risk manager can increase the comprehensiveness and accuracy of the risk identification process and foster stakeholder engagement and buy-in1. References: PMBOK Guide, 6th edition, pages 397-399, 414-4151; Mastering the PMI Risk Management Professional (PMI-RMP) Exam, page 70

The SWOT analysis provides a broad overview of the project ' s strengths, weaknesses, opportunities, and threats. The next step for the interim risk manager is to break down these items into specific risks, categorized as threats (negative risks) or opportunities (positive risks). This classification allows for targeted risk response planning and aligns with PMI ' s risk management processes, which advocate for a clear identification and categorization of risks to derive actionable responses​.

When closing risks as part of the closing process, it is important to update the lessons learned document. This document captures the knowledge and experience gained during the project and can be valuable for future projects.

 Lessons learned is a document that captures the knowledge gained from the project and can help improve the performance of future projects. It is one of the outputs of the project closure process and should include information on the project risks, issues, and responses. Lessons learned can help identify the best practices and lessons to be applied or avoided in similar projects. Updating the lessons learned document is an important part of closing the risks as it can provide valuable insights for risk management. References: PMI, Project Risk Management, 2nd edition, 2019, p. 97-981