According to the PMBOK Guide, the project manager is responsible for ensuring that the project deliverables meet the acceptance criteria and obtaining formal acceptance of the deliverables from the customer or sponsor1. The project manager should also involve the relevant stakeholders in the validation and acceptance process to ensure their satisfaction and buy-in2. Therefore, the best option is to set up a meeting with stakeholders to validate and confirm acceptance of the deliverables. Option A is incorrect because the project sponsor is not the only stakeholder who needs to approve the deliverables. Option B is incorrect because updating the project management plan and marking the milestone as completed are actions that should be done after obtaining formal acceptance, not before. Option C is incorrect because asking the vendor to validate the agreement for any deviations is not a sufficient way to ensure the quality and compliance of the deliverables. References: 1: PMBOK Guide, 6th edition, section 4.6.3.2, p. 123 2: PMBOK Guide, 6th edition, section 13.4.2.2, p. 529

Agile project management emphasizes the delivery of value to the client in small, incremental stages rather than waiting until the end of the project. This approach allows for more flexibility and adaptability, as changes can be made more easily in response to feedback from the client or changes in the project environment. Therefore, the new project manager should meet with the team to review the backlog and create small iterations that can deliver incremental value to the client. References: Project Management Institute.
(2021). A Guide to the Project Management Body of Knowledge (PMBOK Guide)-Seventh Edition. Project Management Institute.

When discrepancies arise between documented scope and current deliverables, the first step is to understand why and how they occurred. The project manager should work with the team to review the change history and clarify whether these changes were officially approved. This enables informed conversations with stakeholders and potential corrective action.
According to the PMBOK Guide - Seventh Edition (Measurement and Stakeholder Performance Domains), issue resolution starts with identification and root cause analysis before initiating change or communications actions.
Option A addresses communication frequency but not the root cause.
Option C is premature if a valid change was already made.
Option D may be done later but doesn't resolve the current concern.
References:
PMBOK Guide - Seventh Edition, Scope and Stakeholder Performance Domains PMI Change Control Best Practices

When a project is experiencing roadblocks, especially when similar issues have occurred in past projects, it is crucial to review and improve the processes being used. The PMBOK Guide emphasizes the importance of monitoring and controlling project work to meet performance objectives, and this includes making necessary changes to project processes to enhance efficiency and effectiveness1. In this scenario, since the team is following the processes exactly, it indicates that the processes themselves may be contributing to the delays.
Therefore, the project manager should analyze the current processes, identify non-value-adding activities, and seek to eliminate or improve them to overcome the roadblocks and get the project back on track. This approach aligns with the principles of process improvement and value addition, which are central to both Project Management and Business Analysis practices2.
References:
PMBOK Guide, 6th Edition, Project Management Institute.
Business Process Analyst: Roles, Duties & Career Guide, Adaptive US Inc.

The statement of work (SOW) is a document that describes the project scope, deliverables, acceptance criteria, assumptions, and constraints1. It is usually part of the contract between the buyer and the seller2. If the project manager remembers negotiating and agreeing to the deliverable during the tender process, they should look to see if the deliverable is described in the SOW, which would be a contractual obligation for the seller. Requesting a change in the contract, adding the deliverable to the requirements traceability matrix, or terminating the contract are not appropriate actions in this situation. References:
* 1 PMBOK Guide, 6th edition, page 154
* 2 PMBOK Guide, 6th edition, page 473