A team charter is a document that is developed in a group setting that clarifies team direction while establishing boundaries. It is developed early during the forming of the team. The charter should be developed in a group session to encourage understanding and buy-in. The team charter has two purposes. First, it serves as a source of information for people who are not part of the team. Second, it serves as a reference for team members. In this case, the project manager is having trouble with meetings not going according to plan and ending in arguments. A team charter could have helped prevent this situation by setting clear expectations for team behavior, roles and responsibilities, and decision-making processes. References: Professional in Business Analysis Reference Materials source and documents

The project manager should agree on the criteria to prioritize risks before developing a risk response strategy.
This is because not all risks have the same level of impact or probability on the project objectives, and therefore require different levels of attention and response. By agreeing on the criteria to prioritize risks, such as expected monetary value, risk score, risk urgency, or stakeholder tolerance, the project manager can rank the risks according to their importance and focus on the ones that pose the most threat or opportunity to the project. This will help the project manager allocate resources, time, and budget more effectively and efficiently to address the risks. The project manager should also involve the relevant stakeholders, such as sponsors, SMEs, and team members, in the risk prioritization process to ensure their input and buy- in. References: (Professional in Business Analysis Reference Materials source and documents) PMBOK Guide, 6th edition, Section 11.4.1, "Perform Qualitative Risk Analysis: Inputs" PMBOK Guide, 6th edition, Section 11.4.2, "Perform Qualitative Risk Analysis: Tools and Techniques" PMBOK Guide, 6th edition, Section 11.4.3, "Perform Qualitative Risk Analysis: Outputs" PMI-PBA Guide, 1st edition, Section 5.3.1, "Prioritize Requirements: Inputs" PMI-PBA Guide, 1st edition, Section 5.3.2, "Prioritize Requirements: Tools and Techniques" PMI-PBA Guide, 1st edition, Section 5.3.3, "Prioritize Requirements: Outputs"

In an agile project, it is important to respect the team's decision-making process. If a decision is made by a majority vote, as agreed upon by the team, the project lead should note their disagreement and the reasons for it but allow the team to proceed with the decision. This approach aligns with agile principles, which emphasize team collaboration and empowerment1. It is also consistent with the PMBOK Guide's guidance on stakeholder engagement and managing project teams2.
References:
The PMP Examination Content Outline, which provides a framework for the role of the project manager and the importance of team decision-making processes1.
The PMBOK Guide, which includes guidelines on stakeholder engagement and project team management2.
Professional in Business Analysis Reference Materials, which support the use of documentation to record project decisions and the rationale behind them3.

The project manager should next review the quality management plan. The quality management plan is a component of the project management plan that describes how the project team will implement the quality policy and satisfy the quality requirements for the project and its deliverables1. It includes the quality standards, quality objectives, quality roles and responsibilities, quality tools and techniques, quality metrics, quality audits, and quality control and validation activities1. By reviewing the quality management plan, the project manager can identify the root cause of the quality issues, determine the corrective and preventive actions, and ensure the compliance with the quality expectations of the key stakeholder.
Option A is not the best answer because reviewing the stakeholder engagement plan is not the next thing to do. The stakeholder engagement plan is a component of the project management plan that identifies the strategies and actions required to promote productive involvement of stakeholders in project decisions and execution2. It is important to review and update the stakeholder engagement plan throughout the project, but it is not the priority when the deliverables are not functioning as expected.
Option C is not the best answer because reviewing the requirements traceability matrix is not the next thing to do. The requirements traceability matrix is a project document that links the project requirements to their origin and tracks them throughout the project life cycle3. It helps to ensure that each requirement adds business value and is aligned with the project objectives. It is useful to review the requirements traceability matrix during the project planning and monitoring, but it is not the main focus when the deliverables are not meeting the quality standards.
Option D is not the best answer because reviewing the work breakdown structure (WBS) is not the next thing to do. The WBS is a project document that decomposes the project scope into smaller, more manageable components called work packages4. It defines and organizes the project work and deliverables. It is helpful to review the WBS during the project planning and execution, but it is not the most relevant document when the deliverables are not functioning as expected. References: 1: PMBOK Guide, 7th Edition, Section 8.1.3.1, Quality Management Plan 2: PMBOK Guide, 7th Edition, Section 13.1.3.1, Stakeholder Engagement Plan 3:
PMBOK Guide, 7th Edition, Section 5.2.3.1, Requirements Traceability Matrix 4: PMBOK Guide, 7th Edition, Section 5.4.3.1, Work Breakdown Structure