Reassessing and Identifying Non-Occurring Risk Events in the AFD Project

B.

Risks that are now outdated should be closed by the project manager, there is no need to keep record of that.

Incorrect Answers: A: Risks do not go into the issue log, but the risk register.

C: Identified risks are already in the risk register.

D: Risks with low probability and low impact go on the risk watchlist.

As the project manager of the AFD project, you are responsible for managing risks associated with the project. Risk assessment is an ongoing process throughout the project lifecycle, and it involves identifying, analyzing, and evaluating potential risks to the project objectives.

During the risk reassessment process, you may identify risk events that have not happened and whose relevance to the project has passed. These risks are often referred to as outdated risks, and they can be removed from the risk register to avoid cluttering the risk management process.

The correct answer to the question is B. Close the outdated risks. Closing outdated risks means removing them from the risk register and any other risk management documentation. Doing so allows the project team to focus on managing current and relevant risks to the project's objectives.

Adding outdated risks to the issues log (option A) or the risk register (option C) is not appropriate because it creates unnecessary documentation that can obscure current risks. Furthermore, risks that have no relevance to the project objectives should not be given priority and be included in a low-priority watch-list (option D).

In summary, the best approach to managing outdated risks is to close them, removing them from the risk register and any other risk management documentation to avoid cluttering the risk management process and allowing the team to focus on managing current and relevant risks to the project's objectives.