PMP Practice: Break Down Scope

Haruki Tanaka-Wen is managing a hybrid project for Spaghetti Architecture Corp to develop a telehealth platform. The project uses predictive planning for infrastructure deployment and agile sprints for feature development. During sprint review, three department heads each claim that the patient scheduling module—delivered last sprint—is missing critical functionality they expected. The QA lead confirms the module meets all documented acceptance criteria. The marketing director insists her team explicitly requested SMS appointment reminders during a planning session two months ago, but this requirement appears nowhere in the product backlog or requirements documentation. The CFO is pressuring Haruki to avoid scope changes that would delay the go-live date now three weeks away. What should Haruki do to address this situation most effectively?