A project manager is leading a project at a contracting company, and the project team just completed an iteration. The product passed inspection, but an additional feature was added to the product. The customer notices the additional feature and thinks it will introduce new risks to the product. What should the project manager do to avoid this situation in the future?

While collaborating with the customer to assess the value of a feature is beneficial, it does not address the need for a formal change control process. This approach may lead to additional features being added without proper evaluation, potentially increasing risks rather than mitigating them.

Frequent reviews are important for maintaining alignment with the customer's needs, but they do not adequately replace a change control process. These reviews might highlight issues in the current product but could fail to prevent the introduction of new risks due to unapproved changes.

Managing the scope baseline is a critical aspect of project management, but it is not a standalone solution for preventing risks from new features. This option emphasizes scope management without directly addressing how to handle changes effectively through a formal process, leaving room for potential misunderstandings and risk exposure.