-
Sprint reviews happen at the end of the sprint and involve all squad members.
-
Other stakeholders are optional invites and can join to see how the sprint went.
-
They should take about an hour, although some teams may need longer or shorter.
-
They are run by the squad’s product owner.
-
They cover the following topics:
-
Run through the final state of the Jira board, close the sprint off.
-
What did the team achieve in the sprint?
-
How many points / tickets were done? Jira has charts and reports that can help with this. Record the points achieved in the Capacity spreadsheet - see Squad Capacity Planning
-
Demos
-
Major functional development, or particular interesting developments should be demoed by the developer or QA
-
Demo’s should be around 10minutes or shorter each.
-
There should be 2-4 demos per sprint (some sprints which concentrate on bug fixes may not have demos)
-
Questions are invited, and any bugs found (as tend to happen in demos) or suggestions should be documented in Jira tickets that can be prioritised by the product owner.
-
-
-
Reviews should be recorded. This allows non-participants to watch the demos.
-
After the meeting, the PO updates the Sprint Page (created after the planning) and fills in information on the outcome of the sprint.