The project manager should ensure that the team has a common understanding of agile, as this is a key factor for the success of agile projects. Having a common understanding of agile means that the team members and stakeholders share the same vision, values, principles, and practices of agile, and can collaborate effectively and efficiently. Having a common understanding of agile also helps to avoid confusion, conflicts, and waste that may arise from using different agile methodologies or applying them inconsistently. The project manager should facilitate the creation of a common understanding of agile by providing training, coaching, mentoring, and guidance to the team and stakeholders, and by establishing clear and transparent communication channels and feedback loops. References:
PMBOK Guide, 6th edition, page 27: "The project manager should ensure that all project stakeholders have a common understanding of the project objectives, approach, deliverables, and expected outcomes." PMBOK Guide, 6th edition, page 28: "The project manager should ensure that the project team and other stakeholders are familiar with the chosen agile approach and practices, and that they receive the necessary training and coaching." PMBOK Guide, 6th edition, page 29: "The project manager should foster collaboration among team members and stakeholders, and promote self-organization and empowerment within the team." PMBOK Guide, 6th edition, page 30: "The project manager should establish an environment where feedback is welcome and encouraged, and where learning and improvement are continuous."

The project manager should begin by talking with the team member to understand what led to the mistake.
This aligns with PMI's emphasis on servant leadership, respect for individuals, and systems thinking.
Gathering context before taking corrective action ensures fairness and allows root cause identification, which can support appropriate next steps like training, process improvement, or system-level changes.
Option A prematurely documents the issue without understanding it.
Option B may be appropriate later but assumes a skill gap before confirming the cause.
Option D is punitive and fails to explore the root cause or support a high-performing team member.
References:
PMBOK Guide - Seventh Edition, Team Performance Domain
PMI Code of Ethics and Professional Conduct (Respect and Fairness)
-

When a new law is announced that may significantly impact the project budget, the project manager should:
* Consult the risk and issue logs (A): The risk and issue logs contain information about potential risks and issues that could impact the project1. The project manager should consult these logs to understand if this new law was anticipated and what mitigation strategies were planned1.
* Discuss with the project sponsor (D): The project sponsor is typically a key stakeholder who has the authority to make decisions about the project1. The project manager should discuss the impact of the new law with the project sponsor to determine the best course of action1.
: 1

The project manager should communicate individually with the affected team members to negotiate the decision and confirm their willingness to relocate, as this is the most respectful and ethical way to handle the situation. Relocating team members abroad for six months is a major change that will affect their personal and professional lives, and the project manager should consider their needs, preferences, and concerns before making any final decisions. The project manager should also explain the rationale and benefits of the relocation, and offer any support or incentives that may facilitate the transition. Communicating to the whole team, the HR department, or the team members' manager may not be appropriate or sufficient, as the project manager should first consult with the team members directly and obtain their consent. These other communication options may also create unnecessary confusion, resentment, or resistance among the team members or other stakeholders. References: PMBOK Guide, 7th edition, pages 111, 112, 113, 114.

Allowing the resources to periodically choose on which team they would like to work is a technique that fosters self-organization and empowerment among the team members. It also helps to create cross-functional teams that can deliver value faster and more effectively. Self-organization is one of the key principles of agile project management, as it enables the team to adapt to changing requirements and customer needs. The project manager should not prevent the resources from choosing teams, as this would undermine their autonomy and motivation. The project manager should also not assume that the resources will always choose their favorite team, as this may not be the case. The project manager should not indicate that the team members have already been assigned to a team through workforce optimization, as this would imply that the team composition is fixed and cannot be changed. References: Project Management Professional Sample Questions, page 12, question 100. [A Guide to the Project Management Body of Knowledge (PMBOK Guide)], Sixth Edition, page 52, section 2.3.2. [Agile Practice Guide], page 14, section 2.1.2.