Page Comparison

Availability

(assume Team Availability Calendar is up to date, otherwise, everyone was available for 8.5 days of the 2-week Sprint)

Full team availability 8.5-day Sprint * 9 dev team members (adjusted as below)	76.5 days
Simon -5, Andy D -3, Liban -2, Jay -1.
Total team availability this Sprint	86%

POs present a review of Sprint goals and other committed work

Sprint Goal: Improve the efficiency of development to better enable the team to build a better product for our end users.

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

Live Issues:

Jira Legacy

server	System JIRA
columns	type,summary,story points (effort),assignee,created,status
maximumIssues	20
jqlQuery	project = TISNEW AND issuetype in (LiveDefect) AND Sprint = 219 order by created DESC
serverId	4c843cd5-e5a9-329d-ae88-66091fcfe3c7

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')

Item	Demo - from Prod URL where feasible	Demo link
1.	Add Field to indicate whether trainee is CCT (Certificate of Completion of Training) or CESR (Certificate of Eligibility for Specialist Registration)
2.	Change the person owner rebuild Jenkins job to call an endpoint Can we re-title this to be descriptive of benefit to the user, please?
3.	Coding standards / style
4.	SYNC SERVICE: API Endpoints for each routine and basic web interface to launch them Can we re-title this to be descriptive of benefit to the user, please?
5.	Bulk Upload for People not updating NI number for existing trainees
6.	As a TIS user I want the application to work quickly through use of Angular AoT
7.	New CI/CD Pipeline to run ONLY the AoT branch against a Stage-like environment Can we re-title this to be descriptive of benefit to the user, please?Create a new staging server for testing the Angular AoT Changes whilst still using the staging database, so that we are not affecting the normal stage environment.

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)

Review Sprint Goal: Respond to user feedback on PPT and data in NDW to make both more usable.

POs present the roadmap: https://ext.prodpad.com/ext/roadmap/d8a231e0ec66a7a9ead4f1464ab24fca5b816dbf

Next Sprint priorities