Although the team member was absent, they possess expert knowledge that may impact project outcomes. The appropriate course of action is to schedule a meeting to hear their concerns and determine whether any adjustments are necessary. This aligns with stakeholder engagement best practices and the PMBOK Guide's principle of team collaboration and empowerment.
Option A discourages engagement and feedback.
Option C focuses on compliance rather than collaboration.
Option D misclassifies this situation as a risk when it is a communication and engagement issue.
Reference:
PMBOK Guide - Seventh Edition, Stakeholder Engagement and Team Performance Domains Agile Practice Guide, Chapter 4: Team Collaboration and Feedback
-

For a project in a remote rural area, especially one nearing completion, the most effective communication method with the local community would likely be through newspapers. This approach is suitable for reaching a broad audience in a locality where digital communication channels like social media or email may not be as accessible or frequently used. Newspapers are a traditional and reliable means of communication that can effectively convey important updates to all segments of the local population, including those who may not have access to or prefer not to use digital media.
The PMBOK Guide emphasizes the need to tailor communication methods to the stakeholders' needs and the context of the project1. It suggests that the format of communication should depend on the type of stakeholder, and various ways should be tailored to each group1. This is supported by the Professional in Business Analysis (PBA) reference materials, which advocate for the analysis of stakeholder needs and the selection of an engagement approach that best suits stakeholders' needs for effective communication and collaboration2.

In Agile (particularly Scrum), the Product Owner is solely responsible for backlog prioritization. The Scrum Master facilitates the process but does not have authority over content decisions. When a conflict arises about prioritization, the resolution lies in re-establishing role clarity-not in the project manager stepping in to override roles.
The correct action is to reinforce Agile roles and responsibilities, particularly that the Product Owner owns prioritization. This aligns with the Agile Practice Guide and the Scrum Guide.
Option B may be helpful but delays resolution and misses the fundamental answer.
Option C incorrectly shifts authority to the Scrum Master.
Option D bypasses the Agile team structure and disrespects team autonomy.
Reference:
Agile Practice Guide, Ch. 3: Roles and Responsibilities in Agile Teams
Scrum Guide: Product Owner Responsibilities