When a key project deliverable is discovered to be unbudgeted, the project manager should first meet with the team to discuss alternatives. This collaborative approach is recommended as it involves the team in problem- solving and may lead to innovative solutions that the project manager alone might not consider. It is also aligned with the principles of the PMBOK Guide, which emphasizes engaging with the team and stakeholders to address project challenges.
: The answer is verified by discussions found in PMP exam-related forums and aligns with the principles outlined in the PMBOK Guide and the Professional in Business Analysis Reference Materials12.

Explanation:
Predictive:
Requirements: are controlled as requirements and constraints emerge.
Changes: are elaborated frequently during delivery.
Risk and Cost: are continuously involved.
Key Stakeholders: are controlled by detailed planning.
Agile:
Requirements: are defined up-front before development team begins.
Changes: are constrained as much as possible.
Risk and Cost: are incorporated in real-time during delivery.
Key Stakeholders: are involved at specific milestones.
The predictive project approach, often referred to as the waterfall model, is characterized by its sequential phase-to-phase development where requirements and planning are done up-front. In contrast, the agile approach is iterative and incremental, with requirements and solutions evolving through collaboration between self-organizing cross-functional teams.
In the predictive approach:
Requirements are detailed early in the project and changes are managed through a formal process.
Changes are not expected to be frequent and are carefully managed.
Risk and Cost are analyzed and assessed as part of the initial planning.
Key Stakeholders are identified and their needs are addressed through detailed planning.
In the agile approach:
Requirements are often co-created with stakeholders and can evolve as the project progresses.
Changes are expected and embraced as part of the methodology to adapt to evolving needs.
Risk and Cost are managed in real-time, allowing for quick responses to change.
Key Stakeholders are engaged continuously, with their feedback incorporated into the project iteratively.
The PMBOK Guide1 and the Agile Practice Guide provide a framework for understanding these approaches. The PMP Examination Content Outline2 also details the differences between predictive and agile methodologies, emphasizing the importance of choosing the right approach based on the project's needs and environment.

In virtual and culturally diverse teams, inclusivity and engagement are best supported by agreed-upon team norms and working agreements. Ground rules that respect time zones, cultures, and communication styles foster equity and psychological safety.
PMBOK Guide - Seventh Edition and the Agile Practice Guide both emphasize the importance of team agreements, team charters, and cultural awareness in virtual settings.
Option A is supportive but doesn't address inclusion issues directly.
Option B adds bureaucracy and fragmentation.
Option D is one part of inclusion but not a complete solution.
References:
PMBOK Guide - Seventh Edition, Team and Communication Performance Domains Agile Practice Guide, Chapter 4: "Agile Teams and Cultural Considerations"
-

In the event of an unexpected leave, it is important to collaborate with the product owner to reassess and reprioritize the sprint backlog. This approach aligns with the principles of Agile and Scrum methodologies, which emphasize flexibility and adaptability in response to changes. The project lead should avoid forcing the developer to postpone their leave (Option A) or hastily arranging for a replacement (Option B), as these actions may not align with the team's values or long-term productivity. Instead, by working with the product owner, the project lead can ensure that the most critical tasks are addressed and that the team's workflow is not disrupted. This may involve reassigning tasks among the remaining team members or adjusting the sprint goals to accommodate the change in capacity. References: (Based on the Agile principles and Scrum guidelines as outlined in PMI's resources12345.)