An experienced and the only developer on a software implementation project will be on leave for several weeks. The risk of this critical resource's availability was added to the risk register. Conting

Question

Options

• AUpdate the risk register to indicate the risk has occurred and close out the expired risk from the
• BUpdate, continuously monitor, and communicate the residual and secondary risks of the backup
• CHire a permanent developer to support the project, and work with the backup resource to eliminate
• DHire another developer to support the project, contingent on when the experienced developer

• A
  4% (1)
• B
  73% (19)
• C
  8% (2)
• D
  15% (4)

Explanation

The contingency plan (having a backup developer shadow the experienced developer) has been activated and is in progress. The risk manager's next responsibility is to monitor the ongoing situation, which includes tracking residual risks (risks that remain even after the response is applied, such as the backup developer not being fully ready) and secondary risks (new risks introduced by the response itself, such as productivity loss during the shadowing period). The risk register and communication plan should be updated accordingly. Options C and D (hiring a permanent or additional developer) are premature escalations not supported by the current scenario. Option A incorrectly treats the risk as closed when it is still actively unfolding.

No community discussion yet for this question.