This scenario highlights a common project risk: resource dependency on a single skilled team member. The most immediate and practical action is to ensure active collaboration among team members to foster knowledge transfer. Agile and adaptive environments encourage continuous collaboration to mitigate such risks early. Option D reflects proactive risk response and aligns with the Agile principle of shared knowledge and team empowerment.
The Agile Practice Guide (Chapter 4: "Agile Teams and Team Performance") emphasizes the importance of collaboration and cross-functional learning. It promotes the development of T-shaped skills, where individuals develop a broad range of knowledge while maintaining deep expertise in specific areas. This approach allows other team members to step in when needed.
Option A is too long-term and not responsive enough to the current project phase.
Option B might not address the knowledge gap if others are untrained.
Option C is useful but does not solve the immediate knowledge-sharing concern.
Reference:
PMBOK Guide - Seventh Edition, Principles: "Build quality into processes and deliverables" and "Engage stakeholders." Agile Practice Guide, Chapter 4: "Team Composition and Empowerment"
-

In an agile or iterative environment, when external changes such as legal or regulatory updates affect project deliverables, the appropriate action is to assess and reprioritize the product backlog. This ensures alignment with the latest compliance needs while balancing value delivery.
According to the Agile Practice Guide and PMBOK Guide - Seventh Edition, backlog refinement is used to review, adjust, and prioritize features based on changing business and legal contexts.
Option B assumes additional resources are needed without first evaluating impact.
Option C may be done, but the first step is impact analysis.
Option D assumes feasibility before performing analysis.
Reference:
Agile Practice Guide, Chapter 5 - Iteration Planning and Backlog Refinement PMBOK Guide - Seventh Edition, Delivery and Planning Performance Domains

When a change (such as a new regulatory requirement) is introduced, the first step is always to assess the potential impact. This allows the project manager to understand how scope, schedule, cost, or quality may be affected. Only after assessing the impact should changes be formally documented and implemented.
The PMBOK Guide - Seventh Edition emphasizes adaptive planning and impact assessment in response to external change (e.g., legal or regulatory). The guide states: "Assess changes to determine impact before recommending a course of action." Option A (Increase slack) is reactive and premature without assessment.
Option B implies implementation before assessing consequences.
Option C (Consult the plan) might follow, but impact assessment is the most immediate and necessary action.
Reference:
PMBOK Guide - Seventh Edition, System Thinking and Risk Principles
PMBOK Guide - Sixth Edition, Section 4.6: Perform Integrated Change Control
-

When specific individuals are disengaged, the project manager should first conduct one-on-one meetings to understand the root causes. Personalized engagement supports psychological safety and trust, especially in remote settings.
According to the PMBOK Guide - Seventh Edition and Agile Practice Guide, team performance and communication are best improved through direct, empathetic interactions.
Option A could add unnecessary complexity without addressing root causes.
Option B may not be feasible for global teams.
Option D is too general when the issue lies with specific members.
Reference:
PMBOK Guide - Seventh Edition, Team and Communication Performance Domains Agile Practice Guide, Chapter 4 - Working with Distributed Teams

When a stakeholder demands the implementation of requirements that are out of scope without additional cost, the project manager should refer to the project's statement of work (SOW). The SOW is a formal document that defines the work activities, deliverables, and timeline a vendor will execute for a customer. It serves as a legally binding agreement that specifies what is included in the project scope and, by extension, what is not. If the stakeholder's demands are not included in the SOW, they are considered out of scope, and the project manager should clarify this to the stakeholder. Implementing out-of-scope requirements without adjusting the project's cost, time, and resources can lead to scope creep, which can jeopardize the project's success.
: The answer is verified with the principles found in the PMI's A Guide to the Project Management Body of Knowledge (PMBOK Guide) and the Professional in Business Analysis Reference Materials provided by PMI12345.