PMP Practice: Appraise team member performance against key performance indicators

This scenario tests understanding of appropriate performance appraisal approaches in agile environments versus predictive mindsets. In agile teams, collective team performance is emphasized over individual metrics because agile work is inherently collaborative, with pair programming, swarming, and shared ownership. Individual story point tracking undermines collaboration by creating competition and discouraging knowledge-sharing behaviors that benefit long-term team capability. The correct response addresses the product owner's underlying concern about velocity while educating them on agile principles. The scenario's closing facts—that morale is strong, retrospectives are healthy, and the team is deliberately building capability through complex work—indicate the team is functioning well despite flat velocity. The real issue is likely that story point estimates haven't adjusted for increasing complexity, or there's misalignment on whether capability-building is the right strategic focus. A servant leader facilitates this conversation rather than implementing metrics that would damage the collaborative culture. The product owner's request reflects predictive thinking where individual accountability drives performance, which is inappropriate for this agile context.

**Why not A:** Escalating to the sponsor to block the product owner's request is adversarial and bypasses the opportunity for constructive dialogue. The product owner has a legitimate concern about velocity, and the appropriate response is education and collaborative discussion, not organizational escalation to prevent their involvement.

**Why not B:** Conducting individual story point analysis and presenting findings to the product owner directly contradicts agile principles of team-level measurement. Analyzing individual performance creates a competitive dynamic and would validate the product owner's inappropriate request rather than redirecting it toward team-level understanding.

**Why not D:** Implementing individual tracking as requested, even with caveats that it is "informational only," introduces a metric that will inevitably influence behavior. Team members will begin optimizing for individual story point counts rather than collaborating, and the promise that metrics won't impact reviews will not prevent the psychological shift from collective to individual focus.