PMI-RMP Exam Preparation Material | PMI Risk Management Professional

Explanation:
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.
Reference: 1: How To Exploit and Enhance Project Opportunities - Project Risk Coach 2 2: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) C Sixth Edition, page 443-4451

Explanation:
To determine the total story points for the entire initiative, we must sum up the estimates provided in the backlog from the email exhibit.
The backlog includes the following user stories with their respective story point estimates:
New log-in screen C 6
Save passwords C 4
Defect fixing C triaged top 10 C 8
Accessibility C color blind C 4
Increase security C 21
Shopping cart C 7
Accept credit card payments C 5
Accept bank drafts C 9
New sort order C 3
Add AI chatbot C 5
Total story points calculation:
6 + 4 + 8 + 4 + 21 + 7 + 5 + 9 + 3 + 5 = 72 story points
Thus, the total number of story points for the initiative is 72, making option A the correct answer.
Reference: Agile estimation techniques suggest using story points to estimate the effort required for backlog items.
The PMI Agile Practice Guide explains that story points represent the complexity, effort, and risk associated with a user story.
Agile teams use story point estimation to gauge work effort without associating it with time directly. This approach ensures that the team has a clear understanding of the overall workload and can manage risks effectively.

Explanation:
The correct answer is D. Update the project stakeholders and seek their input on the resulting secondary risk.
This question describes a secondary risk, which is a new risk that arises as a direct result of implementing a risk response. The original equipment-failure risk was successfully mitigated, but the use of alternative machinery introduced another issue. In standard risk management practice, once a secondary risk is identified, it must be documented, assessed, communicated, and managed through the normal risk process. Because this new risk can affect project objectives and may require additional response planning, relevant stakeholders should be informed and involved in determining the best course of action.
Option D is the best answer because secondary risks should not be ignored or delayed unnecessarily. Stakeholder input is important to evaluate the impact of the new issue, determine acceptable response options, and align decisions with project priorities and risk thresholds.
Why the other options are incorrect:
A. Assign a risk owner and develop the risk mitigations at the next scheduled risk meeting. Assigning an owner and planning mitigation are valid activities, but waiting until the next scheduled meeting may delay needed action. The question asks what the risk manager should do now after identifying the secondary risk. Immediate stakeholder communication is more appropriate.
B. Continue with the project as the risk identified is inconsequential.
The scenario does not support the conclusion that the secondary risk is insignificant. Assuming it is inconsequential without analysis would be poor risk practice.
C. Assign risk responsibility to the project manager to determine how to proceed.
Risk responsibility should be assigned to the most appropriate owner, not automatically to the project manager. Also, the correct first step is broader communication and engagement around the newly emerged secondary risk.
Best-practice reasoning:
Secondary risks are a recognized output of risk response actions. They should be captured and processed like any other identified risk. Transparent stakeholder communication is especially important when a response action creates new uncertainty.
Reference-aligned basis:
This answer is consistent with standard risk management guidance that emphasizes:
risk responses can generate secondary risks,
newly identified risks should be communicated and assessed,
stakeholders should be engaged when new risks emerge from implemented responses.
Reference: PMI, A Guide to the Project Management Body of Knowledge (PMBOK® Guide), Implement Risk Responses and Monitor Risks
PMI, Practice Standard for Project Risk Management
ISO 31000, communication, consultation, and risk treatment principles

Explanation:
The project manager should reassess risks by conducting a new assumptions and constraints analysis. This will help identify any previously overlooked risks and ensure that the risk register is
comprehensive and up-to-date.

Explanation:
Comprehensive and Detailed In-Depth
Extreme Programming (XP) emphasizes continuous feedback, early testing, and adaptive planning. When discrepancies arise, XP encourages identifying root causes and taking corrective actions without delaying value delivery.
Option D: Run a spike, identify what went wrong during implementation, and request a change to enhance value delivery (Correct Answer).
A spike is a time-boxed research activity used to explore a problem, test assumptions, and mitigate uncertainty in XP methodology.
By running a spike, the team analyzes what went wrong in implementation and applies the findings to ensure future iterations align with customer needs.
The PMI-RMP Guide states that “proactive risk response planning helps teams course-correct and maintain delivery momentum” (PMI-RMP Exam Prep Study Guide, 2021, p. 142).
The Agile Practice Guide supports the use of spikes, highlighting that “spikes allow agile teams to validate uncertainties in requirements, leading to more informed decision-making” (PMI & Agile Alliance, 2017, p. 89).
Option A: Release this version and leave changes to be done at the end of the project phase (Incorrect).
XP emphasizes continuous improvement and early defect resolution rather than postponing fixes.
Leaving changes until later may increase technical debt and reduce user satisfaction.
Option B: Arrange a workshop where all ideas will be discussed and take corrective actions ensuring value delivery (Partially Correct but Not the Best Answer).
While workshops help gather feedback, they do not provide technical validation of what went wrong.
A spike (Option D) is a better approach because it directly investigates the issue and leads to actionable changes.
Option C: Ask the development team to brainstorm and come up with suggestions that will improve the delivery date (Incorrect).
Brainstorming may generate ideas but does not analyze the root cause of the discrepancies. Without a structured approach like a spike, there is a risk of guessing rather than using data-driven solutions.
Final Verdict:
The best answer is D (Run a spike, identify what went wrong during implementation, and request a
change to enhance value delivery) because a spike provides empirical insights, leading to more
effective corrective actions.
Reference: PMI. Agile Practice Guide (2017). PMI & Agile Alliance.
PMI. PMI-RMP Exam Prep Study Guide (2021).