According to the PMBOK Guide, a retrospective meeting is a process of reviewing and analyzing the past performance of a project team, especially in an agile or hybrid environment. The purpose of the retrospective meeting is to identify the strengths and weaknesses of the team, the lessons learned, and the improvement actions for the future. The project manager should facilitate the retrospective meeting and encourage the team to share their feedback, opinions, and suggestions. If the project team's performance has declined for the last three iterations, the project manager should focus on remediation not merely on correcting symptoms. This means that the project manager should help the team to find the root causes of the performance issues, and implement effective solutions that address the underlying problems, not just the superficial symptoms. For example, if the team is facing communication challenges, the project manager should not just provide more communication tools, but also improve the communication processes, protocols, and skills of the team.
Focusing on remediation not merely on correcting symptoms will help the team to improve their performance and prevent recurrence of the same issues. Comparing the team's performance against other project teams is not a good option, as it may demoralize the team, create unhealthy competition, and ignore the unique context and challenges of each project. Identifying potential failure points based on the iteration workload is a useful technique, but it is not enough to improve the team's performance. The project manager should also analyze the actual failure points and the reasons behind them, and take corrective and preventive actions accordingly.
Motivating the team to perform better is a desirable outcome, but it is not a specific action that the project manager should do. The project manager should use various motivational techniques, such as recognition, rewards, empowerment, and feedback, to inspire the team and enhance their morale and engagement. References: PMBOK Guide, 6th edition, pages 18-19, 686-687, 723-724.

Explanation:

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.
References:
PMBOK Guide - Seventh Edition, Stakeholder Engagement and Team Performance Domains Agile Practice Guide, Chapter 4: Team Collaboration and Feedback
-

This is a People domain question because it deals with communication, team dynamics, leadership, and concern resolution. PMI's PMP Examination Content Outline stresses that project leaders should support team performance, address and remove impediments, and use leadership approaches that help teams function effectively. Daily standups are intended to promote transparency and surface issues quickly, but when one individual repeatedly raises doubts, the project manager should first understand the underlying concern in a focused discussion rather than letting the standup become a prolonged debate.
Option A is not the best first step because daily standups are meant to be short and coordination-focused, not deep problem-solving sessions. Option B is premature because the project manager has not yet diagnosed the real issue. Option D is too escalatory for an initial team-level concern. The strongest PMI-aligned first action is to meet privately with the individual to understand the concern, assess whether the risk response strategy has a valid gap, and then determine the proper action. This reflects servant leadership, active listening, and issue resolution at the lowest appropriate level before escalation.

In situations of conflict, it is important for the project manager to address the issue constructively. Cultivating self-awareness through emotional intelligence (EI) can help team members understand their own emotions and those of others, which is crucial in resolving conflicts. This approach aligns with the PMBOK guide's recommendations on conflict management, which suggest that problem-solving and collaboration are effective strategies for dealing with team conflicts12. By fostering EI, the project manager can facilitate a more harmonious work environment and mitigate the negative impact on the project. References: = PMI's resources on conflict management and resolution strategies1; PMBOK Guide's section on conflict resolution2.