A project manager is working in an environment where requirements are not very clear and may change during the project. In addition, the project has several stakeholders and is technically complex…

Occasional risk identification is insufficient in an environment with unclear and changing requirements; risk activities must be continuous and frequent in adaptive approaches.

Reviewing requirements and using cross-functional teams are general agile practices but do not constitute a specific risk management strategy for complex, uncertain environments.

Including contingency reserves and frequently updating the project management plan is a predictive risk management approach and does not leverage agile's iterative feedback loops to manage evolving requirements.

Agile risk management relies on short feedback cycles through iterative development - by frequently reviewing incremental work products, the team surfaces risks early, and by continuously updating and reprioritizing requirements, the team adapts to new information, reducing uncertainty and managing risk dynamically rather than through static risk registers.