According to the PMBOK Guide, the project management plan is a formal, approved document that defines how the project is executed, monitored, and controlled1. It integrates and consolidates all of the subsidiary plans and baselines from the project management processes1. One of the inputs to the process of developing the project management plan is the project charter, which provides the high-level description of the project and its boundaries, as well as the high-level requirements, risks, assumptions, and constraints2. Therefore, the project manager should clarify the high-level business requirements with the event organizer as a basis for forming the deliverables list, which is part of the project scope management plan, a component of the project management plan3. The other options are not the best actions for the project manager to complete the task of developing the project management plan. Benchmarking other similar exhibitions' deliverable lists and final outcomes is a technique that can be used to collect requirements, but it is not sufficient to form the deliverables list without clarifying the high-level business requirements first. Initiating a survey to solicit end-customer opinions and prioritize exhibition contents is also a technique to collect requirements, but it is not the first step in developing the project management plan. Initiating an additional services agreement in case the key deliverables list was not clearly stated in the contract is a risk response strategy that can be used to deal with potential scope changes, but it is not a necessary action to develop the project management plan. References:
* 1: PMBOK Guide, 6th edition, page 89
* 2: PMBOK Guide, 6th edition, page 77
* 3: PMBOK Guide, 6th edition, page 131
* : PMBOK Guide, 6th edition, page 148
* : PMBOK Guide, 6th edition, page 443

According to the Project Management Professional (PMP) guidelines, effective communication is crucial for the success of a project. In this scenario, the project manager is facing challenges with the current communication channels. The best course of action is to collaborate with the project team and agree on a suitable communication method that ensures information is shared promptly and effectively. This proactive approach can help avoid delays and negative consequences for project delivery. References: PMBOK Guide, Communication Management. Please refer to the specific sections in the PMBOK Guide and PMP study materials for more detailed information.

In an agile project, it is crucial to ensure that the deliverables meet the customer's expectations and provide value. The project manager should have validated the iteration goals with the customer to ensure alignment with the customer's vision and value requirements. This validation process is a key aspect of agile methodologies, which emphasize customer collaboration and iterative development to refine and deliver a product that meets the customer's needs1234.
References:
PMBOK Guide - Sixth Edition.
"Minimum Viable Product (MVP): What is it & Why it Matters" - Atlassian1.
"MVPs and MBIs" - Project Management Institute2.
"Understanding the Minimum Viable Product (MVP) in Agile Project Management" - MPUG3.
"An Agile Guide to Integrating Customer Feedback" - MeisterTask4.

To avoid the issue of a product not being designed to specifications, it is essential for the project manager to ensure that the customer's requirements are accurately captured and understood. This involves engaging with the customer to elicit detailed requirements, which then guide the design and development of the product. The PMI's standards on requirements management highlight the importance of a thorough needs assessment, elicitation, and analysis of requirements to ensure that the final product aligns with the customer's expectations1. Additionally, the PMI-PBA emphasizes the role of the business analyst in working with stakeholders to define and shape project outputs to drive intended business outcomes2.
: The answer is supported by the principles outlined in the PMI's "Requirements Management: A Practice Guide" and the PMI Professional in Business Analysis (PMI-PBA) certification resources, which stress the significance of capturing customer requirements to deliver products that meet customer standards12.

With repeated vendor delays and no option to replace the vendor, the project manager must actively manage the supplier relationship and develop a realistic recovery plan. Reaching out to the vendor to create a plan (C) is the most effective action: confirm root causes, agree on an achievable delivery schedule, identify acceleration options (expedite shipping, partial deliveries, priority allocation, additional shifts), and define monitoring and escalation checkpoints. This aligns with procurement management and issue management:
collaborate first to restore performance while protecting the 90-day constraint. Threatening penalties (A) may be part of the contract strategy, but leading with penalties can damage collaboration and may not produce a practical recovery plan. Waiting to use contingency funds (B) is reactive and risks missing the hard deadline.
Reviewing lessons learned (D) is helpful, but it does not directly address the immediate supplier performance problem. A vendor recovery plan with clear commitments, accountability, and frequent tracking best supports schedule control under tight constraints.