PMP Practice: Define Scope

In agile environments, sustainable pace and realistic commitment are essential principles that protect team health and product quality. The scenario provides clear data showing the team's consistent velocity (30-35 story points) cannot support an 52-point commitment. The project manager's role is to facilitate collaboration between the product owner and team to make the best value-based decision. By helping Marcus identify the five highest-value stories for the demo and coaching him to adjust stakeholder expectations, Vikram protects both the team's sustainable pace and the business need. This approach respects the team's professional judgment about capacity while still delivering meaningful value at the conference. The product owner owns prioritization, and the team owns commitment—the PM facilitates the conversation where these meet.

**Why not A:** Negotiating a compromise by splitting the difference between what Marcus wants and what the team can deliver ignores the objective velocity data. The team's historical velocity of 30-35 story points cannot support 52 points regardless of negotiation. Arbitrary compromises that override empirical data undermine agile principles and likely result in overcommitment.

**Why not B:** Supporting the team's five-story commitment is appropriate, but escalating to the program sponsor to resolve the conflict is premature. The disagreement between Marcus and the team is a normal prioritization discussion that the PM should facilitate, not an escalation-level conflict. The PM's role is to help them find alignment through collaborative conversation.

**Why not C:** Encouraging the team to commit to all eight stories and work extra hours violates the agile principle of sustainable pace. Historical velocity data clearly shows the team cannot deliver 52 story points in a sprint. Overcommitting leads to technical debt, burnout, and reduced quality, which would harm both the product and the team long-term.