Sprint 2 Review (2019-09-18 to 2019-10-01)

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
Andy D - 2, Ola - 2, Simon - 1.
Total team availability this Sprint	93.5%

POs present a review of Sprint goals and other committed work

Sprint Goal:

Improve placement planner user experience by reducing the number of clicks required to find overlapping placements and trainee information.
Develop a solution to pull relevant data direct from GMC, rather than via 3rd party.
Start bringing in data from ESR into the new system design.

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

Area	Item	Demo - from Prod URL where feasible
ESR Bi-directional Project Ongoing Maintenance and support	Tweaks to Duplicate issue
	New Messaging Infrastructure
	File and message splitter service	Build and Tooling: Plan: Progress: RabbitMQ Management — Watch Video
	Data structure design	Message Format and Examples Initial Data thoughts
	Not yet complete: Create function to notify splitter service when a file arrives in azure blob storage
TIS Development	All Comments in the assessments tabs need to be readable	Before: https://www.loom.com/share/ae5eb8f1abd64f6b80a7aeb338edb84d After: https://www.loom.com/share/12c06e6cebd247e5a883618b153eb417
	Auto-populate Funding body when creating/updating a new funding episode in a post and selecting the Funding type	https://www.loom.com/share/768fa16291f24f64a1b0e48045b87d21
	OOP/055/SWLSTG - the UI for this post is constantly refreshing	https://apps.tis.nhs.uk/admin/posts/edit-post/39839
	Warning Pop up when allocating more than one trainee to a post number within the same time period.	https://www.loom.com/share/31c6f3c08f0e47acb9e72386b6e89f3b
	Error message when Creating/Updating a Post with an existing NPN to be surfaced on FE rather than a 400 Error	https://www.loom.com/share/f1d87569db1e4dbbbd61d3b3ccd90e38
	Use the GMC's List of Registered Medical Professionals.	Specifically, for the GMC status, Start date and End date, pull it from the GMC based on the Doctor's Surname and GMC number instead of someone in HEE entering these. No service yet. There is a Secure File Transer Service (website that allows downloading files over HTTPS). We've looked into the data set and are talking with the GMC about being a Pilot user of an automated service.
	Add 'N/A' option to 'training pathway'
	Bulk Upload Post Fundings to Posts failing - Reason for import failure not accurate	Some findings/observations: 1. Initially it was the data error. Those funding body were not there in the reference db. After reference db got updated, these errors were eradicated. 2. What happened to those `missing` records in different envs. Those missing records are the `same` records in different rows of the excel as we were using same postId For example in the attached file it will be only `2` rows Row 254 is counted as 1 and the rest will be 1. So total row is 2
Other

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)

Sprint Goal (achieved? / ):

Improve placement planner user experience by reducing the number of clicks required to find overlapping placements and trainee information.
Develop a solution to pull relevant data direct from GMC, rather than via 3rd party.
Start bringing in data from ESR into the new system design.

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

Next Sprint priorities

TIS21 Confluence Space

Sprint 2 Review (2019-09-18 to 2019-10-01)

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

POs present a review of Sprint goals and other committed work

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

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

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)

Sprint Goal (achieved? / ):

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

Next Sprint priorities

Related content