Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

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

type summary story points (effort) assignee created status
Refresh

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

DemoAreaDemo - from Prod URL where feasible

ESR Bi-directional


ESR

Where we were (Sprint 10)


Where we are now



Trainee-UI:

Display current and future placements

Trainee UI

 

Live demo on local environment

Nothern Ireland On boarding:

Spike: Northern Ireland - Admins access to TIS

NIDiscussion 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.

TISNEW-3386 - Getting issue details... STATUS

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.

TISNEW-3696 - Getting issue details... STATUS

TIS,

Bulk Upload

Frontend validation:

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

Bulk upload:

Database update:

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

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? (thumbs up) / (thumbs down)): 

  • 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

  • No labels

Slack: https://hee-nhs-tis.slack.com/
Jira issues: https://hee-tis.atlassian.net/issues/?filter=14213