SPRINT REVIEW

The sprint review is part of the scrum framework for product development and management. Knowing how to run a sprint review is a prerequisite for any product management or ownership role, but it’s important to make the ceremony more than just a demo of work completed during a sprint.

A sprint review is an informal meeting held at the end of a sprint, during which the team shows what was accomplished while the stakeholders provide feedback.

The updates to increment are demonstrated by assigned people. Usually, these people present are Project Managers, Tech Leads, sometimes developers and rarely others.

Guideline

1. Document the items that are Done
2. These deliverable items are to be added to the list during the Sprint just as the Definition of Done is applicable
3. Items are shown in order and within the timebox of the demo [meeting], which can be up to 1.5 hours. If there are more things to review, it is recommended to have two meetings with a short break in between
4. The list of items is prioritized, and main features and enhancements come first (Sprint priorities are set during the Planning meeting)
5. They should include a name of presenter, a short description, test data (e.g., temporary credentials, mocked data), and noted feedback.
6. The more technical part has to come last, and maybe not all participants have to be involved
7. Deliverables like completed tech design, investigation, or some kind of reports should also be mentioned, but they are not a subject of obligatory demonstration
8. After each item, there should be a Q&A session for up to 10 minutes. Stakeholders should be able to ask questions related only to the particular item
9. The recording of the meeting must be stored as part of a project artifacts for future reference.

Tips

1. Separate end-user and technical parts
2. The samples of test data must be prepared beforehand

Rules

• Attendees include the Scrum team and key stakeholders invited by the Product Owner;
• The meeting facilitator explains what Product Backlog items have been “Done” and what has not been “Done”;
• The Developers may mention what went well during the Sprint, what problems it ran into, and how those problems were solved;
• The Development Team demonstrates the work that it has “Done” and answers questions about the Increment;
• The Product Owner discusses the Product Backlog as it stands. He or she projects likely target and delivery dates based on progress to date (if needed);
• The entire group collaborates on what to do next so that the Sprint Review provides valuable input to subsequent Sprint Planning;
• Review of how the marketplace or potential use of the product might have changed what is the most valuable thing to do next; and,
• Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated releases of functionality or capability of the product.

Template

Sprint Review

Sprint Feedback

1.Feature/Task A

• Presenter:
• Description:
• NOTE:

2. Feature/Task B

• Presenter:
• Description:
• NOTE:

3. …

DevCom is a trusted technology partner for many of the world’s leading enterprises, SMEs and technology innovators. Through every stage of the product life cycle, DevCom is a brain-trust dedicated to forward-thinking.

In case you don’t know where to start your project, you can get in touch with us.

Our Blog: https://devcom.com/articles/