Mentoring is a recognized approach for enhancing the skills of less-experienced team members. It allows for knowledge transfer and provides the less-experienced members with guidance and support as they grow into their roles. This approach aligns with the PMI's emphasis on team development and the value of leveraging the collective knowledge of the team. By pairing less-experienced members with mentors, the project manager can foster a collaborative environment where all team members can contribute effectively while learning from one another.

This scenario represents the realization of an external risk. When an identified risk occurs, the appropriate action is to follow the response strategy as documented in the risk management plan. The PMBOK Guide - Seventh Edition emphasizes the importance of using the risk response plan to guide actions when risks occur. This avoids delays and ensures a structured response rather than ad hoc decision-making.
Option A may be needed in some cases but is not the project manager's responsibility unless required by law.
Option B ignores the actual disruption caused.
Option D introduces unnecessary delay by deferring action instead of using the pre-approved plan.
Reference:
PMBOK Guide - Seventh Edition, Risk Management Performance Domain
PMBOK Guide - Sixth Edition, Section 11.6: Implement Risk Responses
-

Agile encourages active stakeholder engagement, especially in activities such as sprint reviews and product increment demonstrations. When stakeholders want to be actively involved in reviewing increments, the best course of action is to promote that involvement through events that provide transparency, promote feedback, and ensure alignment with business goals.
According to the Agile Practice Guide, active stakeholder participation is a fundamental component of adaptive approaches. Sprint reviews provide opportunities for inspection and adaptation, and key stakeholders are encouraged to attend.
Option A is useful for general stakeholder mapping but doesn't promote involvement.
Option B addresses documentation, not action.
Option C is too early-stage; they already expressed their needs (involvement).
Reference:
Agile Practice Guide, Section 5.3 - Stakeholder Engagement
PMBOK Guide - Seventh Edition, Stakeholder Performance Domain
-

Agile methodologies emphasize direct, frequent, and transparent communication. Inviting the PMO manager to the daily standup meetings aligns with agile principles, fostering collaboration and ensuring that all parties are informed and engaged in the project's progress. This approach allows for real-time updates and immediate feedback, which is essential for agile projects where adaptability and quick responses to change are critical. The daily standup is a key agile practice that helps the team synchronize activities and plan for the next 24 hours12.
Reference:
Agile Communication: Techniques, Examples and Best Practices - PM-Training1 Unleashing the power of communication in agile transformations - McKinsey2