According to the PMBOKGuide 7th Edition, one of the principles of project management is to "focus on value". This means that the project manager should deliver products, services, or results that meet the needs and expectations of the customer and other stakeholders. One of the ways to achieve this is to use an adaptive or agile approach, which allows for frequent feedback and collaboration with the customer. Working with the product owner to define the minimum viable product(s) (MVPs) is an example of an agile technique that helps to deliver value early and often, and to validate the customer's requirements. MVPs are versions of the product that have enough features to satisfy the customer's needs and provide feedback for future development.
Therefore, this option is the best approach to remove the impediment of the customer's unclear requirements.
The other options are not as effective because they do not address the root cause of the problem, which is the lack of customer involvement and validation. Following a predictive approach may lead to delivering a product that does not meet the customer's needs or expectations, and may result in rework or waste.
Reinforcing the negotiation and soft skills of the team may help to improve the communication and relationship with the customer, but it does not ensure that the product will deliver value. Developing and monitoring a plan with due dates may help to manage the schedule, but it does not guarantee that the product will satisfy the customer's requirements. References: : PMBOKGuide 7th Edition, PMI, 2021, p. 9 : Agile Practice Guide, PMI, 2017, pp. 25-26

According to the PMBOK Guide, an issue log is a project document that records and tracks any issues that arise during the project and how they are resolved. It is part of the project communications management knowledge area and the monitor communications process. A project manager should update the issue log whenever a new issue is identified, analyzed, or resolved. Updating the issue log and defining the mitigation strategy is the immediate action that the project manager should take to improve the situation of a new team member impacting the project performance. This will help to document the issue, communicate it to the relevant stakeholders, and plan how to address it effectively. Communicating the issue to the human resources department (A) may be a subsequent action, but not the immediate one. Providing additional training to the new hire (B) may be a possible mitigation strategy, but not an action to take before updating the issue log.
Increasing team cohesiveness by sharing information and experiences openly may be a good practice for team development, but not a direct response to the issue at hand. References: PMBOK Guide, 6th edition, pages 377-378, 529-530.

According to the PMBOKGuide, an agile coach is a person who guides, mentors, teaches, and facilitates a team in adopting and improving agile practices and principles. The agile coach should also foster a culture of collaboration, trust, feedback, and continuous improvement within the team. When a team member is openly criticized by others during a standup meeting, the agile coach should intervene and address the situation as soon as possible. The agile coach should emphasize the ground rules of the standup meeting, such as respecting each other, being supportive, and focusing on the work. The agile coach should then redirect the attention of the team to today's activities and impediments, and help them find solutions and remove blockers.
This way, the agile coach can prevent the conflict from escalating, maintain a positive team atmosphere, and ensure the team's progress and alignment. Letting the discussion go on, addressing the team members involved during the next sprint retrospective, or avoiding the discussion by referring to the team charter are not effective ways to deal with the situation. These options may ignore, postpone, or evade the issue, which could harm the team's morale, performance, and relationships. References: PMBOKGuide, 6th edition, pages 52, 335,
540-541.

Explanation/Reference:
Explanation:
Cost of quality involves both the cost of conformance and the cost of non-conformance. Examples of the cost of conformance are divided into two categories prevention costs and appraisal cots (includes inspections). Costs of non-conformance include internal failure costs and external failure costs.

Explanation/Reference:
Explanation:
A no-cost settlement can be used in lieu of formal termination procedures when the seller has indicated that such an arrangement is acceptable, no buyer property has been furnished under the contract, no payments are due the seller, no other obligations are outstanding, and the product or service can be readily obtained elsewhere.