The Importance of the Sprint Review

In addition to planning and execution, regular review of completed work is a fundamental pillar of agile.

In Scrum, this event is formalized as the Sprint Review, which is held at the end of each Sprint.

Its main purpose is to inspect the Product Increment developed during the Sprint and adapt the Product Backlog if necessary, based on the feedback obtained.

It is a collaborative working session, not a mere formal presentation, where the Scrum Team (Product Owner, Scrum Master, Development Team) and key stakeholders meet to discuss what has been achieved and decide on next steps.

This review ensures transparency on progress and allows to adjust the direction of the product on an ongoing basis.

Demonstrating Increment to Stakeholders

A central component of the Sprint Review is the demonstration of "Done" work.

The Development Team shows what they have built during the Sprint, focusing on the functional and potentially deliverable Increment of the product.

It is crucial to invite all relevant stakeholders to this session so they can see the progress first hand.

The demo should not focus on code or technical aspects inaccessible to non-technical audiences, unless that is the only way to show value (such as an API), and in that case, understanding should be ensured.

The goal is to show tangible, functional results that allow stakeholders to evaluate the value delivered.

Collect Feedback and Adjust the Backlog

Beyond the demonstration, the Sprint Review is an invaluable opportunity to collect direct feedback from stakeholders on the Increment presented.

This feedback is essential to validate whether the work performed meets needs and expectations.

Based on this feedback, as well as market changes or new ideas, the Product Owner can adjust the Backlog by reprioritizing items, adding new ones or modifying existing ones.

This continuous adaptation of the backlog ensures that the team is always working on what is most valuable based on the latest information.

Suggestions or new requests that arise during the review are noted ("parked") to be evaluated and prioritized later by the Product Owner, not discussed in depth at that time.

Best Practices (Focus on "Done", Avoid Excessive Presentations)

For the Sprint Review to be effective, some best practices should be followed:

Focus on "Done:" Only work that fully meets the Definition of "Done" (DoD) should be demonstrated. Half-done work is saved for the next review.

Minimal Preparation: Avoid spending too much time creating elaborate presentations or slides.

The focus is on the actual product demonstration and conversation. Pre-recording complex demos can be helpful to save time.

Active Collaboration: Foster an environment where stakeholders ask questions and offer constructive f