According to the PMBOK Guide, when using an agile approach, the project manager needs to have a clear understanding of the product vision, the product roadmap, and the product backlog1. The product vision is a brief statement that describes the desired outcome of the project and the value it will deliver to the customers and stakeholders2. The product roadmap is a high-level overview of the product features and deliverables, along with the planned timeline and milestones3. The product backlog is a prioritized list of the product requirements, user stories, and other work items that need to be completed by the project team. These three factors help the project manager to align the project objectives with the customer needs, plan and execute the project iteratively and incrementally, and deliver value early and often1. The other options are not relevant for an agile approach, as they are more suitable for a predictive or waterfall approach. Key performance indicators (KPIs) are metrics that measure the performance of the project against the project objectives.
Schedule performance index (SPI) is a ratio of the earned value to the planned value, indicating how well the project is progressing according to the schedule. These factors are not essential for delivering a product using an agile approach, as they focus more on the adherence to the plan rather than the delivery of value. References:
* 1: PMBOK Guide, 6th edition, page 18
* 2: PMBOK Guide, 6th edition, page 156
* 3: PMBOK Guide, 6th edition, page 157
* : PMBOK Guide, 6th edition, page 158
* : PMBOK Guide, 6th edition, page 33
* : PMBOK Guide, 6th edition, page 267

The project manager should conduct a customer demonstration at the end of each build cycle to help the client understand the value delivered during project execution. This is a common practice in agile projects, where the team showcases the working product increment to the customer and solicits feedback. This way, the customer can see the tangible results of each iteration, validate the alignment with their expectations, and provide input for future improvements. This option aligns with the PMI-PBA practice guide, which states that
"demonstrations are a key technique for validating requirements and obtaining feedback from stakeholders" (p. 67). The other options are not the best choices because they do not effectively communicate the value of the product to the customer. Including a planned value (PV) calculation in the sprint report for each build cycle (option A) may provide a quantitative measure of the project performance, but it does not show the actual functionality or quality of the product. Providing the customer with the refined specification during each build cycle (option C) may reflect the changes or clarifications made to the technical requirements, but it does not demonstrate the working product or its benefits. Showing the customer a sprint burndown chart for each build cycle (option D) may indicate the progress and velocity of the team, but it does not reveal the features or value of the product. References:
* PMI-PBA Practice Guide, p. 67 1
* PMBOK Guide, 6th edition, p. 189 2

The project manager should first become aware of any cultural characteristics of the new supplier that could impact negotiation. This is an important step to ensure effective communication and collaboration with the overseas company, as well as to avoid any misunderstandings or conflicts that could arise from cultural differences. By becoming aware of the new supplier's cultural values, norms, preferences, and expectations, the project manager can adapt their negotiation style and strategy accordingly, and establish a positive and respectful relationship with the new supplier. This option aligns with the PMBOK Guide, 6th edition, which states that "the project manager should be aware of the cultural characteristics of the parties involved in the negotiation and how they may influence the negotiation process and outcome" (p. 480). The other options are not the best choices because they are not the first steps to proceed with the change. Engaging the services of an interpreter who understands the project domain (option A) may be a useful step to facilitate communication with the new supplier, especially if there is a language barrier, but it is not the first step. The project manager should first understand the cultural aspects of the new supplier before engaging an interpreter, as the interpreter may also need to be aware of the cultural nuances and sensitivities. Checking social media to determine if there are any common connections that use the new supplier (option B) may be a helpful step to gather some information or feedback about the new supplier, but it is not the first step. The project manager should first conduct a more formal and reliable assessment of the new supplier's cultural characteristics, rather than relying on social media, which may not provide accurate or relevant information. Requesting assistance from the procurement department on the next steps (option C) may be a necessary step to proceed with the change, but it is not the first step. The project manager should first prepare themselves for the negotiation with the new supplier by becoming aware of their cultural characteristics, before seeking assistance from the procurement department on the contractual and legal aspects of the change. References:
* PMBOK Guide, 6th edition, p. 480 1
* PMBOK Guide, 6th edition, p. 489 2

A cost baseline is the approved version of the projected costs for the entire project. It is fixed, and, along with other aspects of the project baseline, is used as a benchmark for the rest of the project1. A cost baseline includes the cost estimates for all the tasks on the project schedule, plus the contingency reserves for identified risks (known unknowns)2. A cost budget is the cost baseline plus the management reserves for unidentified risks (unknown unknowns)2. Therefore, before determining the cost baseline, the project manager needs to add contingency into the budget to account for inflation and other changes that may affect the project costs. This is different from looking at a previous project, requiring stakeholder approval, or revising the project timeline and scope, which are not necessary steps for creating a cost baseline. References:
* 3: What Exactly is a Cost Baseline in Project Management? | Runn
* 2: Project Cost Management: Cost Baseline vs Budget for PMP Exam

The project manager should ask the SMEs to share the knowledge transfer documents with all other members by placing the documents in the PMIS, as this is the best way to ensure knowledge transfer across the team.
The PMIS is a system that collects, organizes, and distributes project information to the project stakeholders.
By using the PMIS, the project manager can ensure that the process deviations captured by the SMEs are communicated and documented to the rest of the team, and that the team has access to the latest and accurate information. This will also help the project manager to monitor and control the project performance and quality, and to identify and address any issues or risks that may arise from the deviations.