Page Comparison

PO present a review of Sprint goals and other committed work

Sprint Goal:

Enabling the validation and automated testing of updates to personal data received by ESR, to ensure data in TIS is updated as expected and the information about a trainee is up to date, accurate and complete especially for the TIS ESR applicant process
As a trainee, when I open the trainee interface, I can see all my current and future training information

POs supported by Dev team provide a 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:

None

Jira Legacy

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

Dev team demo 'done' work contributing to those goals (no reference to specific Jira tickets, and no reference to work not 'done')

Demo

Area

Demo - from Prod URL where feasible

ESR Bi-directional

ESR

Where we

were (Sprint 10)

Where we are now

are now

Image Added

No change in user functionality, set up testing environment, improved robustness and validation of data storage. The end result is making sure the Bi-Directional personal data is transfered back correctly to TIS from ESR in a way which is testable and repeatable.

Integration Environment Powerpoint

View file

name	integration env.pptx
height	250

Trainee-UI:

Display current and future placements

Trainee UI

Image Added Image Added

Live demo on local environment

Nothern Ireland On boarding:

Spike: Northern Ireland - Admins access to TIS

NI

Discussion and PoC

Plan/Outcomes of the Spike:

Generalise the users as their generic names i.e. ‘Admin’, ‘TIS Admin’ rather than calling them as HEE Admin,

NIMDTA Admin or HEE TIS Admin, NIMDTA TIS Admin. This can be done if we add Entity (Nation/Country) layer

in the User Management.

Nothern Ireland can be considered as one of the Local offices.
Users, trainees and Local offices will be associated with the Entity not with roles or permission.
Update the SQL and Elastic Search queries to filter data based on Entity.
Need a seperate environment for testing the deployment of NI.

Revalidation

TIS

Disabled the inactive curriculums while adding a curriculum in the program membership.

TIS

Jira Legacy

server	System JIRA
serverId	4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key	TISNEW-3386

TIS

Demo from stage

TIS

If no value has been provided for a GMC/GDC/PH number form the TIS UI, then they should be sent and saved as nulls in the database.

If GMC/GDC/PH numbers are entered with extra white spaces (leading, trailing and extra middle.) then it should be removed when saving or at least prompt the user to correct before saving.

TIS,

Bulk Upload

Frontend validation:

Jira Legacy

server	System JIRA
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key	TISNEW-3696

TIS,

Bulk Upload

Frontend validation:

https://www.loom.com/share/c11214276d2345e7aac91fa4674d4d055e884841c9de4250b4844b7a178cc653

Bulk upload:

View file

name	TIS People Import Template-fail.xls
height	250

Database update:https://build.tis.nhs.uk/metabase/question/304

Updated all empty string values to NULL, and removed all of the whitespaces.

When registration numbers are exported to NDW, there wouldn't be any extra whitespaces and empty string values.

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? / ):

Enabling the validation and automated testing of updates to personal data received by ESR, to ensure data in TIS is updated as expected and the information about a trainee is up to date, accurate and complete especially for the TIS ESR applicant process
As a trainee, when I open the trainee interface, I can see all my current and future training information

Current Priorities

- Overall and next sprint

Versions Compared

Old Version 5

New Version Current

Key

PO present a review of Sprint goals and other committed work

POs supported by Dev team provide a 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 reference to specific Jira tickets, and no 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? / ):

Current Priorities