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

Simon

Ola

Ashley

Jay

Joanne

Paul

-9 days

-4 days

-5 days

-4 days

-3 days

-1 day

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:

Complete the Placement Planning Tool;
Consolidating Admins UI to Angular 5;
Improve performance / reduce errors and the requirement to ask users to clear their cookies / log off and log back in again

The following items to be shared by team members during this sprint review

key	summary	type	assignee	status	business value	story points (effort)	priority (bv*sp)

Loading...

Refresh

Item

TIS Ref / Owner

Status

Description of work
Link. e.g. to working software https://apps.tis.nhs.uk/
(note: use Dev for obfuscated data)
Loom video of completed work https://www.useloom.com/

Confluence housekeeping - especially deleting documentation that is out of date. Ongoing
Dev standards (Dev meeting / series of meetings). Ongoing
Pairing / Mobbing
Git-commit messages
Walk-throughs (prep as you go - links?).
Architectural level diagrams

Ongoing

Shortlisting Lead dev in Manchester and DevOps in London.

FSD (Joseph) in London starting on 1 April.

Manchester: Lead Dev, FED, Junior Dev

London: DevOps, FED