PMI-RMP · Question #500
A project manager was informed that the testing of the latest component in the project's software update release was not successful. As a result, 1he delivery timelines for the software release wifi b
The correct answer is B. Reassess risks with a new assumptions and constraints analysis.. Because the failed testing risk was never captured, it was likely rooted in an unchallenged assumption or an unexamined constraint-for example, assuming the component would pass testing. Reassessing risks using an assumptions and constraints analysis directly targets the root cau
Question
A project manager was informed that the testing of the latest component in the project's software update release was not successful. As a result, 1he delivery timelines for the software release wifi be delayed, The project manager did not previously capture this as a risk to the project. What should the project manager do next to avoid similar risks?
Options
- AAdd contingencies to other tasks to mitigate similar risks.
- BReassess risks with a new assumptions and constraints analysis.
- CReview the risk response plan looking for lessons learned.
- DLog the event in the issue log and update the project management plan.
How the community answered
(16 responses)- A6% (1)
- B75% (12)
- C13% (2)
- D6% (1)
Explanation
Because the failed testing risk was never captured, it was likely rooted in an unchallenged assumption or an unexamined constraint-for example, assuming the component would pass testing. Reassessing risks using an assumptions and constraints analysis directly targets the root cause: identifying hidden assumptions that, if wrong, could generate similar unforeseen risks. Option A (adding contingency) treats the symptom, not the cause. Option C (reviewing the risk response plan) is not useful because no response plan existed for this risk. Option D (logging in the issue log) is appropriate for managing the current problem but does not help prevent similar risks in the future.
Topics
Community Discussion
No community discussion yet for this question.