During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment.
Artefacts to Inspect
Key artefacts to inspect and review during this event are:
- The Increment of work – As soon as work achieves the Definition of Done it is considered an Increment. Work that hasn’t achieved Done should not be brought to this event. It should be returned to the Product Backlog. The Product Owner will decide whether or not work not Done is still of value to continue with next Sprint.
Artefacts to Adapt
Key artefacts to adapt and rearrange during this event are:
- Product Backlog – Any feedback is documented and put into the Product Backlog.
Elements to Review
Reviewing and discovering what has changed in the stakeholders and the product environment often includes:
- Metrics – Discuss what metrics, such as customer satisfaction, usage index, market trends, tell us about what customers and users might need or want now.
- Progress toward the Product Goal – What do the metrics say about the product goal? Is more investment needed to create the impacts the product is trying to make in the market or the outcomes its delivering for stakeholders?
- How users are using the product or service – What does usage tell us about how we might prioritise work for next Sprint?
- Forecasts, budget and milestones – If things have changed, what is the impact on any original plans?
- User Research – has user research given us any new insights into users’ motivations, wants, needs, or behaviours? Does this impact what we might do in future Sprints?