Which additional considerations should the project manager make when managing risks in an agile/adaptive project?

According to the PMBOK® Guide and the Agile Practice Guide, risk management in agile/adaptive environments is not a one-time or infrequent event; it is integrated into the heart of the iterative cycle.

Continuous Risk Management: In adaptive environments, risk is identified, analyzed, and managed during each iteration. Because agile projects deal with high variability and uncertainty, the team reassesses the risk profile frequently—often during iteration planning and daily stand-ups.

Small Batches and Feedback: By breaking the work into small increments (iterations), the team can uncover risks early. Each iteration provides a " fail-fast " opportunity, where technical or requirements-related risks are exposed through the delivery of a working product increment.

Risk-Adjusted Backlog: The project manager and the product owner work together to prioritize the backlog. High-risk items (often called " Risk-Reducers " ) are frequently pulled into early iterations to prove concepts or tackle technical challenges before significant resources are spent.

Why other options are incorrect:

Option A: Adding more risk categories is a matter of tailoring the Risk Management Plan, but it doesn ' t address the specific behavioral or procedural change required by an agile environment.

Option C: While you might refine a probability and impact matrix, simply adding " new values " does not account for the rapid, iterative nature of an adaptive project.

Option D: Increasing reserves is a way to handle financial or schedule impact (Active Acceptance), but it is not the primary management consideration for agile. Agile projects actually aim to reduce the need for large, unknown reserves by providing transparency and frequent course correction.