POs present a review of Sprint goals
Dev team demo 'done' work contributing to those goals (no more reference to specific list of Jira tickets, and no more reference to work not 'done')
POs supported by Dev team provide narrative on why, and what, emergency work was brought into the Sprint and which committed-to tickets were moved out as a result
Stakeholders / Users invited to query / interrogate / applaud (after Sprint Review POs convert consensus inputs into backlog tickets, giving the option to consider them in the coming Sprint Planning)
POs present the roadmap
Stakeholders / Users invited to comment and advise on any changes that should be considered (after Sprint Review, POs coordinate amendments to the roadmap)

Availability

(assume Team Availability Calendar is up to date, otherwise, everyone was available for 9 days of the Sprint

Full team availability 9-day Sprint * 11 dev team members	99 days

Total team absence	-26 days

Sprint Goal / Priorities

Sprint Goal: As a user, I want to be able to log in and use the PPT, So that I can create and update placements on the planner.

The following list was the prioritisation output from Sprint Planning:

Sprint Goal: As a user, I want to understand what is necessitating that I should clear my cookies / log out and log back in again, so that in the future I don't need to
Additional committed work:
1. Show all posts attached to the programme selected in PPT
2. Submissions failing for NCEL trainees in Revalidation
3. Remove status column from main assessments page
4. New feature - Added Date & Amended Date fields to be added to Placements so that it can be populated in NDW
5. West mids posts – add/remove post funding records