According to the PMBOK® Guide (6th and 7th Editions), Project Risk Management is not a one-time event but a continuous and iterative process. While significant risk identification and analysis occur during the Planning Process Group, the project environment is dynamic, and new risks can emerge at any time.
The Standard for Project Management emphasizes that risk management should be conducted throughout the project for the following reasons:
Iterative Nature: As the project progresses and more information becomes available, the team ' s understanding of risks evolves. This requires repeating the Identify Risks, Perform Qualitative Risk Analysis, and Perform Quantitative Risk Analysis processes.
Monitor Risks: This specific process, which belongs to the Monitoring and Controlling Process Group, ensures that existing risk responses are effective and that new risks are identified and analyzed promptly.
Closing: Even during the Closing Process Group, risks related to product handover, liability, or administrative closure must be managed.
Analysis of Distractors:
A (Project Planning): While a significant amount of risk management occurs here (creating the Risk Management Plan and Risk Register), limiting risk management only to the planning phase would leave the project vulnerable to risks that emerge during execution.
B (Monitoring and Controlling): Monitoring and Controlling is a crucial phase for risk management, but it relies on the foundations laid during Planning. Risk management must span both these groups and others.
C (Quality Planning): Risk and Quality are closely related (e.g., a lack of quality is a risk), but Quality Planning is a subset of the project ' s overall management. Risk management is a much broader Knowledge Area that encompasses more than just quality-related uncertainties.
