PMP Practice: Outline Escalation Paths and Thresholds

This scenario requires balancing two legitimate but competing needs: the sponsor's requirement for executive-level predictability and reporting (typical of organizational governance expectations) and the project's intrinsic need for adaptability given rapidly evolving user expectations and frequent pivots. A hybrid governance model addresses both by establishing a predictable cadence for executive oversight and budget management at the organizational level, while empowering the team to work adaptively at the delivery level. The monthly steering meetings provide the sponsor with the visibility and control points needed for board reporting, while two-week sprints with continuous feedback allow the team to respond to the fast-changing AI landscape. This is appropriate for projects where organizational governance needs don't align perfectly with optimal delivery approaches. The key closing fact is that the sponsor needs board reporting predictability AND the product requires frequent pivots based on user feedback—only a hybrid approach satisfies both constraints.

**Why not A:** Eliminating the monthly steering committee meetings to align with adaptive principles disregards the sponsor's legitimate organizational need for budget oversight and board-level reporting, and misapplies agile principles to the governance context. Agile principles govern team delivery practices, not organizational governance requirements. A project manager who unilaterally eliminates executive oversight mechanisms would undermine the sponsor's ability to fulfill their organizational accountability and would damage the PM's relationship with the sponsor.

**Why not B:** Delaying governance decisions until after the first prototype is complete squanders the early development time when establishing clear working agreements and decision-making processes is most valuable. By the time the first prototype exists, the team will have already developed patterns and assumptions about how decisions get made. Governance decisions made retroactively are harder to implement and create friction with teams already operating under informal norms. The scenario's competitive pressure also makes delay costly.

**Why not D:** Implementing a traditional phase-gate structure with baseline approvals and formal change control is misaligned with the project's characteristics. The scenario explicitly states that specific features and UI designs are still being explored, that the development team is effective in two-week iterations, and that rapid market response is essential. A phase-gate approach would require locking scope before it is sufficiently understood, restrict the team's ability to incorporate user feedback, and slow delivery in a market where competitor speed is a direct threat to success.