When Sprint Review Becomes Status Theater

Sprint review fails quietly. The board shows green. The demo looks confident. The client still cannot accept the work because the path they care about was never finished — only narrated.

On software service teams, the pressure to look “on track” for an account manager often outweighs the pressure to expose incomplete acceptance criteria. Coaches see the same pattern: review agendas that list tickets instead of outcomes, and facilitators who fill silence rather than ask whether Done means client-accepted.

What to change first

Separate shown from accepted on the agenda. A item can be demonstrated and still remain open. Write that distinction into the Definition of Done language your client already signed, not into a new poster nobody reads.

Second, shorten the demo script. If an engineer needs three minutes of preamble before the acceptance path appears, the work is probably not ready for review. Practise saying that in the room before the client joins.

A coaching cue that helps

When a ticket is marked Done but the acceptance path fails live, stop the review. Do not “come back to it.” The discomfort is the teaching moment. Teams that skip it train themselves to hide unfinished work again next sprint.

Facilitation coaching often starts here because review is public. Fixing planning alone will not repair trust once a client has watched unfinished work presented as complete.