Sprint 76 Review (2019-06-25)

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 * 8 dev team members (adjusted as below)	64 days
Andy -3, Yafang, JohnO, Simon -1, Ola, Jay, Pepe, John
Total team availability this Sprint	94%

POs present a review of Sprint goals and other committed work

Sprint Goal: Complete Placement Planning Tool MVP ready for use outside East Mids pilot and begin stabilising Reval.

Plus other committed-to work:

Remove/Create tabs in Manage Connection have reduced visibility when displaying the record count
Remove jHipster from Admins UI FE - removal of dependencies / libraries. Part 1
Replace backend query param sanitizer
Remove the Synchronisation jobs within TCS and build a separate Synchronisation service
ESR - Produce Full Notification Files (DNF) for all Local Offices after 14/03
Service status (Database, Admin Page, Incident Log Admin Page, Microservice)

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:

type	summary	story points (effort)	assignee	created	status

Loading...

Refresh

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.	Extend logic for Programme role for Placement Planner users
2.	Move revalidations' GMC outcome status updating from Revalidation to the GMC Sync
3.	Remove jHipster from Admins UI FE - removal of dependencies / libraries. Part 1
4.	Replace backend query param sanitizer	Previous Site search: Loom Video Current Site search: Live Create Post page
5.	Remove the Synchronisation jobs within TCS and build a separate Synchronisation service
6.	Remove/Create tabs in Manage Connection have reduced visibility when displaying the record count
7.	ESR - Produce Full Notification Files (DNF) for all Local Offices after 14/03	Nothing to demo. The DNF files were produced on 18th June 2019 and included in the ESR upload on the 19th June 2019.
8.	Service status
9.

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