A team implementing a third‑party hosted system is asked just before go-live to add functionality. The team identified risks to the delivery date and said some requested functions conflict with the agreed scope. What should the project manager do?

The project manager's primary responsibility is to manage stakeholder expectations and project scope. By discussing the identified risks and scope conflicts with the customer, the project manager facilitates an informed decision. This approach ensures transparency and allows the customer to understand the implications of their request on the project's timeline and agreed-upon deliverables. Estimating effort and submitting a change request (option B) is a subsequent step, not the immediate first action when risks and conflicts are identified. Asking the customer to proceed with go-live and add functionality to the backlog (option C) is a possible solution but should be a joint decision after discussing the issues, not a unilateral directive. Instructing the team to deliver new functionality by the original go-live date (option D) is unrealistic and ignores the identified risks and scope conflicts, potentially leading to project failure and team burnout.