2021/2: Q1 | Review#2 (2021-04-13 to 2021-04-27)

Welcome

  • Overviews of the iteration

  • Any interruptions / Live Defects

  • Team going through what they’ve achieved during the iteration

  • Feedback from those on the call on what we have done (constructive criticism / praise / questions)

  • Collaboration with those on the call on what to do next

  • Ask questions:

- out loud on the call - really, we’d appreciate you doing this!;
- write in the Team meeting chat; or
- fill in the post-Review survey after the call
(for questions that occur after the call is over, or if you don’t want to ask the question during the call for whatever reason, and
for letting us know whether the Review meets your expectations, or whether you have some suggestions for improvement)

  • Overviews of the iteration

  • Any interruptions / Live Defects

  • Team going through what they’ve achieved during the iteration

  • Feedback from those on the call on what we have done (constructive criticism / praise / questions)

  • Collaboration with those on the call on what to do next

  • Ask questions:

- out loud on the call - really, we’d appreciate you doing this!;
- write in the Team meeting chat; or
- fill in the post-Review survey after the call
(for questions that occur after the call is over, or if you don’t want to ask the question during the call for whatever reason, and
for letting us know whether the Review meets your expectations, or whether you have some suggestions for improvement)

Live Issues:

key summary created updated status
Loading...
Refresh

 

Incident logs

 

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

Area

Description

Team Representative

Demo - from Prod URL where feasible

Area

Description

Team Representative

Demo - from Prod URL where feasible

TISSS

Data syncing from TIS blocked by Curricula marked as deleted

@Andy Dingley

Two curricula exist with a status of “DELETED”, this status was not correctly handled by the TIS → TISSS sync process and caused an error.
Currently, any record that causes an error will cause a halt to syncing data to TISSS until the error is resolved.

FormR part B COVID declaration not shown on live environment

@Andy Dingley

The COVID declaration was set up as a toggle-able feature, which unfortunately had not been turned on in the live environment.
This has now been enabled and additional measures taken to ensure that the test and live environments stay consistent in this regard.

FormR Part B - Declaration Type dropdown has no options.

@Andy Dingley

The values for the dropdown are taken from a set of reference data, the live environment had no values included in our reference data.
The missing data has now been added and additional measures taken to ensure that the test and live environments stay consistent.

FormR Part B - Covid Change Circumstance dropdown has no options.

@Andy Dingley

The values for the dropdown are taken from a set of reference data, the live environment had no values included in our reference data.
The missing data has now been added and additional measures taken to ensure that the test and live environments stay consistent.

Unable to save or submit forms in live environment

@Andy Dingley

The live application did not have the correct permissions granted to it, it mistakenly had the same permissions as the test environment. This caused save and submit to fail as it tried to access live resource with test permissions.
The permissions used when processing forms has now been properly split so distinct permissions are used in both test and live.

Specialties now being synced between TIS and TISSS

@Marcello Fabbri (Unlicensed)

 

Form R - Amend date range validation from + or - 10 years to 25 years

(e.g. Programme Start date - part A; Type of work Start date - part B)

@Steven Howard

Live demo

Relabel the Sensitive data heading to Registration details.

Instead of GMC, GDC, PH, use the full label or registration body name to make them clearer.

@Steven Howard

Live demo

Support Query - selectable local office
(which includes abbreviating LO names in drop-down list so they can be viewed on mobile devices)

@Steven Howard

Live demo

Form R Part B bug fix (Date of Previous Revalidation)

@Steven Howard

Before
Complete Form R Part B (section 1) and save a draft - leaving Date of Previous Revalidation blank (which is fine because it is not mandatory). When you reopen draft form and try to proceed to the next section then you get this strange error message that prevents you from doing so.

After
(live demo)

 

TISSS Feedback - "X" (close) button not functioning

@Steven Howard

Before:

After:

(live demo)

Reval

Syncing TIS and GMC data into Reval WIP

@Cai Willis

Discussion of ongoing work to synchronize TIS and GMC data into Reval (Where we are up to)

 

 

 

TIS

Add Sentry Alerting the the NDW-ETL

@Edward Barclay

The NDW-ETL service will now notify the developers and Data/TIS leads once the connections to the databases has been interrupted by way of sending a slack notification through sentry, allowing for quicker and more efficient responses

Make sure the Dev team can restart failed jobs

@Joseph (Pepe) Kelly

What we’ve done:

  • Created users in additional environments (esp. Northern Ireland)

  • Applied permissions to groups in preference to users where possible

Objective Key Results (OKRs) Financial Q1

OKR

1st
Iteration

2nd
Iteration

3rd
Iteration

4th
Iteration

5th
Iteration

6th
Iteration

Objective: Support Trainees with their use of TIS Self-service

Key Result#1: No unresolved 'serious' queries (combining # of queries with their nature)
* ”serious” = preventing Trainees using the app, or preventing us from moving to the next stage of roll out of the App to other LOs. Syncing of data while not instant, should be near real-time, rather than overnight. Resolution of serious queries to be in place by the end of the pilot.

too early

too early

 

 

 

 

Key Result#2: Trainees score overall experience and satisfaction of TIS Self-service at 6 or higher

too early

too early

 

 

 

 

Key Result#3: 70% of Trainees engage with TIS Self-service as part of the initial pilot

too early

too early

 

 

 

 

Key Result#4: Admins surveyed indicate their overall experience and satisfaction is 6 or higher

too early

too early

 

 

 

 

*TIS Self-service MVP:
Trainees:

  • have a login to TISSS and know what to use it for, and can reset their passwords

  • can access their personal details held on TIS

  • can see their current and future Programme and curriculum membership they are training on

  • can ensure placement details are accurate and have a way of knowing where they are going to be training next

  • have visibility of their assessments including upcoming ones

  • are able to complete their Form R Parts A and B electronically

  • are able to receive support when they have queries regarding using Trainee Self Service or Submitting specific forms

HEE Admins:

  • are able to access submitted Form R's and unlock / un-submit them

TIS Dev team roadmap:

Feedback

We really do welcome any feedback you have for us - whether it be negative or positive, or whether it be a suggestion of something we could try/incorporate in a future Sprint Review. We absolutely don’t want to stand still. We’re very happy applying the 12th Agile principle of ‘becoming more productive’ to our Sprint Reviews themselves! Your contributions to this survey are entirely anonymous, should you wish to include anything others might perceive as controversial. We welcome any and all feedback, as long as it is constructive!