One of the most important events in Scrum is the sprint review, or sprint demo.

This is when the team gathers to show off the work completed in the sprint.

Stakeholders or clients from outside the team are usually invited and

given the opportunity to see the team's progress and ask questions or

provide feedback on the direction of the work.

Do you remember how the Agile Manifesto declares the value of working software

over comprehensive documentation?

The sprint review centers around demonstrating

potentially shippable product.

The team demonstrates the result of each product backlog item, or

user story showing how it works in software.

The sprint review does not have to be a long meeting.

I prefer short sprint reviews of a half an hour or less.

I find that stakeholders are more happy to attend,

if they know the event will be brief and a good use of their time.

The product owner should also have an opportunity

to gather feedback from the stakeholders.

This can happen as stakeholders ask questions during the sprint review or

in followup conversations with the stakeholders.

The sprint review is generally a celebration of the team's successes and

a demonstration of working software.

However, transparency is valued, and the team should also acknowledge the work

the team committed to that did not get finished.

And the challenges they discovered.

This will help keep stakeholders up to date and informed, and

also help the team work together to make better estimates on future work.