In accordance with the PMBOK Guide and the Agile Practice Guide, risk management in adaptive environments is not a one-time event or restricted to specific phases. It is an ongoing, continuous process integrated into the heart of the delivery cycle.
* Continuous Risk Assessment: In Agile, high-variability environments mean that risks emerge and change rapidly. Therefore, risks are identified, monitored, and prioritized during every iteration (Sprint).
* The Risk-Adjusted Backlog: The Product Backlog is frequently reprioritized based on both value and risk. High-risk items are often moved to earlier iterations (a concept known as " failing fast " ) to resolve uncertainty before significant investment is made.
* Ceremony Integration:
* Iteration Planning: Risks are considered when selecting items for the Sprint.
* Daily Stand-ups: Emerging risks or " impediments " are identified daily.
* Review and Retrospectives: These sessions are used to identify new risks related to the product or the team ' s processes and to adjust the risk management approach for the next iteration.
Analysis of Other Options:
* A. Only during the initiation and Closing phases: This is incorrect for any methodology. Restricting risk management to the start and end of a project leaves the entire execution phase vulnerable to unmanaged threats.
* B. During the initiation and Planning phases: This describes a traditional, " up-front " planning mindset.
In Agile, planning is continuous (progressive elaboration), so risk management must be as well.
* D. Throughout the Planning process group and retrospective meeting: While the retrospective is a key part of the process, risk management isn ' t limited to " Process Groups " (which is more of a predictive terminology) or just the retrospective. It happens throughout the entire duration of every iteration.