Explanation
According to the PMP reference materials, a project scope is the description of the project's deliverables, boundaries, and acceptance criteria12. A project scope is based on various assumptions, which are factors that are considered to be true or certain for planning purposes, but may change later12. Assumptions are documented in the assumptions log, which is a project document that records the assumptions and constraints of the project12. When assumptions change, they may affect the project scope, schedule, cost, quality, or risks, and may require changes to the project management plan or other project documents12. Changes are documented in the change log, which is a project document that records the details of all changes that occur during the project life cycle12.
According to the best practices for change control process, a change control process is a process used to manage change requests for projects and big initiatives34. It involves creating a change log where project change requests are tracked and reviewed by a change control board, which is a group of people from the project team that meets regularly to consider changes to the project34. The change control board decides on the viability of the change request or makes recommendations accordingly, and communicates the decision to the project team and the client34. The change control process helps to ensure that changes are aligned with the project objectives, stakeholder expectations, and customer demand, and that they are implemented with the least amount of disruption to the project plan34.
Based on these principles and practices, the best answer is B, which is to update the assumptions log and change log, and implement the change control process. Thisanswer follows the guidelines for managing changes that affect the project scope and other aspects of the project, and helps to maintain the project's alignment with the planned business value. The other options are not the best actions to take for this scenario, as they either do not address the root cause of the problem, or they are not appropriate or effective for the situation. Delivering what was planned in the project management document according to the specifications (A) may not be possible or desirable, as it may not meet the customer's needs or expectations, or it may result in poor quality or wasted resources. Informing the client that the project cannot meet the project timeline and additional costs will be incurred may not be accurate or helpful, as it may not reflect the actual impact of the changes, or it may damage the client's trust and satisfaction. Reporting on the changed assumptions to the project sponsor and seeking support to prioritize the change requests (D) may not be sufficient or necessary, as it may not involve the other stakeholders or the change control board, or it may delay the change management process. References: 1: Develop Project Management Plan - Project Management Institute 2: Project Scope Management - Project Management Knowledge 3: What Is a Change Control Process? (with Example Change Log ... - Asana 4: Change Control Board: Roles, Responsibilities & Processes - ProjectManager