The transit director wants a private preview of the fare-capping Increment and then to skip Sprint Review so the team does not air dirty laundry in front of riders and partner agencies. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
Sprint Review is the city's tasting table, not a press conference you can cancel when the sauce is spicy. If a director hides the Increment, nobody inspects and nothing adapts. Protect the feedback loop, even when the hallway is powerful.
Full Explanation
Sprint Review exists so stakeholders can inspect the Increment and adapt the Product Backlog. When the transit director wants a private preview of the fare-capping Increment and then to skip Sprint Review so the team does not air dirty laundry in front of riders and partner agencies, the Product Owner should protect Sprint Review. Cancelling Review and sending the director a recorded demo instead removes collaborative inspection and adaptation. Letting the director replace the Product Owner during Review so feedback stays politically safe misplaces accountability. Converting Review into a status meeting with no Increment and only green metrics destroys the event’s purpose. Exam caveat: sensitive previews can happen in addition to Review; they must not replace transparency with the wider stakeholder set Scrum expects. Operational check: keep Sprint Review on the calendar with the working Increment, invite riders and partners as appropriate, capture adaptation items on the Product Backlog, and decline private-only substitution for the civic fare product’s inspection cadence. Keep civic stakeholders focused on inspectable outcomes for residents and operators rather than inbox politics or vanity metrics.