A food company is developing a new product using a predictive approach and is now in testing. Based on test feedback the project manager switched to an iterative approach. At the end of one iteration a new regulation is enacted. What should the project manager do next?

The project has shifted to an iterative approach, meaning work is done in cycles. When a new regulation is enacted, the most effective and agile response is to incorporate a compliance verification assessment into the next iteration. This allows the team to address the new requirement within the existing iterative framework, ensuring that subsequent work aligns with the regulation without disrupting the current iteration or immediately halting progress. Raising a change request to modify project scope (A) might be necessary eventually, but the immediate next step in an iterative environment is to assess and plan for compliance within the next cycle. Holding an iteration review (C) is for reviewing the completed work of an iteration, not for addressing new external changes. Restarting testing (D) is premature and inefficient; the first step is to understand and plan for the regulation's impact.