PMP Practice: Value servant leadership

This scenario requires the project manager to address a conflict that has already damaged team dynamics and performance over multiple sprints. The retrospective revealed the conflict publicly and ended without resolution, indicating the issue has escalated beyond what the team can self-manage. The correct approach combines individual listening sessions to understand root causes without the defensiveness of a group setting, followed by a facilitated collaborative resolution focused on working agreements. This servant leadership approach addresses both the interpersonal relationship and the underlying process breakdown around technical decisions. The scenario's closing facts make this the clear best choice: the conflict is public, has persisted for two sprints, caused significant velocity decline, and prevented the retrospective from being productive. These factors eliminate reactive approaches that avoid direct engagement.

**Why not B:** This response abdicates the project manager's responsibility to manage team dynamics. In agile environments, the project manager or scrum master should address team conflicts directly as a servant leader. Escalating to functional managers delays resolution, sends the message that the PM cannot handle team issues, and does not address the technical decision-making process breakdown. The scenario shows the conflict is impacting the entire team's performance, making it a project-level concern requiring PM intervention.

**Why not C:** While separation might provide short-term relief, it does not resolve the underlying conflict and creates inefficiencies in an agile team that should be cross-functional and collaborative. This approach avoids the problem rather than solving it, prevents knowledge sharing, and may create further resentment. The scenario indicates the conflict involves technical decision-making processes that affect the whole team, so separating the individuals leaves the root cause unaddressed.

**Why not D:** This approach is confrontational rather than collaborative and likely to increase defensiveness without addressing root causes. Simply restating expectations does not resolve the existing conflict or repair the damaged relationship. The scenario shows this has been building for two sprints and became public in the retrospective, indicating the individuals are already aware of professional expectations but lack a mechanism to resolve their technical disagreements constructively.