PMP Practice: Implement Resolution Strategies

The conflict between Kenji and Lila stems from a deeper systemic issue: the team has not transparently discussed how accumulated technical debt is impacting their ability to deliver value. The 25% velocity drop is a warning signal that the team's technical foundation is eroding. The most effective approach is to help the team see the connection between technical health and sustainable delivery, then collaboratively decide on a path forward. This addresses the root cause of the conflict rather than suppressing it or imposing a solution. In agile environments, the team is empowered to self-organize around sustainable practices, and the retrospective is precisely the forum for surfacing and resolving these tensions. By facilitating a data-informed discussion, the project manager helps the team make an informed decision that balances immediate delivery pressure with long-term capability.

**Why not A:** Proposing a 15% compromise by splitting the difference does not address the underlying issue. An arbitrary midpoint between two positions may not reflect the actual technical debt impact on velocity or the real feature delivery needs. Effective resolution requires understanding the root cause, not mechanical compromise.

**Why not B:** Asking both developers to take the discussion offline dismisses the conflict rather than addressing it. The retrospective is precisely the right forum for discussing process and technical concerns, and redirecting the conversation away from this venue signals that the team should avoid difficult topics.

**Why not D:** Escalating the prioritization decision to the product owner removes the team's involvement in understanding and solving the problem. The product owner can decide backlog order, but the team needs to collectively understand how technical debt is affecting their velocity to make sustainable commitments going forward.