Skip to content
All Posts
Agile & Process

The Art of the Sprint Review

17 December 20242 min read

I have a strong opinion about sprint reviews: if you are presenting slides instead of showing working software, you are doing it wrong.

The sprint review exists for one purpose — demonstrating what the team built and getting feedback from stakeholders. Slides, Jira burndown charts, and velocity reports belong in other meetings. The sprint review is show and tell.

What a Good Sprint Review Looks Like

Live demo, every time. Even if the feature is backend-only, find a way to demonstrate it. Hit the API with Postman. Show the database query returning the right results. Show the test passing. Stakeholders need to see something real. It builds confidence that progress is not just tickets moving across a board.

The team presents, not the PM. The developer who built the feature demos it. The QA engineer who tested it explains the edge cases. This gives the team ownership and visibility with stakeholders. My role is to facilitate, manage time, and handle questions that require program context.

Capture feedback in real time. I keep a running document during the review. Every piece of feedback gets captured, attributed, and triaged after the meeting. "That is a great idea" is not a commitment. "I have captured that and we will prioritize it during refinement" is.

Stay within the timebox. Thirty minutes for a two-week sprint. If you cannot demo everything in thirty minutes, you are either building too much or explaining too much. Ruthlessly prioritize what to show — highlight the sprint goal items and skip the minor fixes.

The Trust Dividend

Teams that run good sprint reviews build a trust account with stakeholders. When you inevitably need to have a hard conversation — about a missed deadline, a scope trade-off, or a resource constraint — that trust gives you credibility.

I have managed accounts where the sprint review was the single most important meeting of the sprint. Not standup. Not planning. The review. Because it was the moment where stakeholders saw proof of progress and felt confident in the team.


Back to all posts