6.6.1. Sample Scenario: Conflicting Stakeholder Expectations

Scenario: Midway through a project, the sponsor expects the team to prioritize a new feature request, while the original scope agreement (signed off by the steering committee) doesn't include it. The team is unsure whether to proceed.

Reasoning: This tests Business Environment task 3 (manage and control changes) intersecting with People task 5 (align stakeholder expectations). The correct instinct is neither "do what the sponsor says" (bypasses change control) nor "refuse and cite the signed scope" (ignores legitimate stakeholder engagement) — it's to route the request through the formal change-control process while facilitating a stakeholder discussion to align expectations about the trade-offs (schedule, cost, or scope impact) of accepting it.