Quality management Question

 The code development phase of a software project is nearly complete when the first code review is conducted. During the review, it is discovered that the application is missing functionality required to complete a key business process. However the product scope never specified this functionality. what should the project manager do?

1. Reject the functionality as it's outside the project's scope

2. Assess the impact on the project of including the functionality, and inform the sponsor

3. Agree to include the functionality in the current release

4. Agree to include the functionality in the next release.

Appreciate inputs and justification as usual. 

Regards,

Riyaz

I go with option 2.

First, since the functionality is required to complete a key business process, the Project Manager ought not reject it on a fiat. However, the PM may not include it automatically as such activity is outside scope. It would require a study of the impact of such inclusion- whether it adds any value, whether other risks might be introduced, whether the team has the resources to carry out such functionality etc, etc.

Thereafter, the PM can inform the customer (before a proper Change Management procedure could follow)

What do experts think?

Option 2 only seems correct to me since PM needs to look at the impact and its a must add functionality.