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
