The risk has already been identified, evaluated by the project team and its impact already determined as to have conflit with the scope. The next thing to do is to inform the customer and discuss raised concerns with him on the impact this change will have on the scope.

In this scenario, the project team has identified risks to the delivery date and informed the project manager that some of the requested functions are in conflict with the agreed scope. Therefore, the project manager should discuss the situation with the team to assess the impact of the change, estimate the effort required to implement the new functionality, and evaluate the risks and benefits of approving the change request. Then, the project manager should raise a change request to the customer and seek their approval before proceeding with the change.

The risk identified and the associated impact should be discussed with the customer along with scope creep concerns. Even after this, if the customer wants to go ahead with the reqs, then a CR should be raised and change control process should be followed.

Option A, discussing with the customer the risks identified and team’s concerns, seems to be the most appropriate. This approach ensures that the customer is fully aware of the implications of their request and can make an informed decision.

Discuss with the customer the risks identified and team's concerns

C. Ask the customer to go live and add the new functionality in the backlog

The key is "the requested functions are in conflict with the agreed scope"; if not conflict, you can evaluated and raise change request, but it is conflicted, then you should to identify and make it clear with the customer first. May customer did not recognize the conflict, if they know, they have not required it yet.

A. Giving the customer the impact of the changes or additional scope.

Answer is B - Assess and raise a change request. Change Control Board will review and approve or reject!!

B is the ans

A is the correct answer since the requests are not in line with the scope therefore you cannot opt for B and estimate efforts of something that totally contradicts the main deliverables.

A - The project manager should first understand the customer's request. The next step would be to assess the impact (B)

I am going with A because of one small wording issue with B. 'Raise a change request' in option B would not be the right course of action. It's the PM's responsibility to first evaluate the impact of the change to the project. In this case it could negatively impact the schedule and deviates from the original scope so shouldn't the PM speak with the customer first prior to submitting the change request?

For any change, first do the impact analysis and effort estimation, and then submit change request to CCB to decide and then take action accordingly. For option A, Customer may say that this functionality is important for the product. Hence, if the risk is identified, instead of discussing with customer only, we should do the analysis and create a risk response or use contingency/management reserve for the risk management. Hence, we should follow the change control process.

A. Discuss with the customer the risks identified and team's concerns

voted a

B. No need to discuss team's concerns with the customer.