Versions Compared

Old Version 16

changes.mady.by.user Andy Nash

Saved on

compared with

New Version Current

changes.mady.by.user Joseph (Pepe) Kelly

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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)

Live Issues:

Jira Legacy
serverSystem JIRA
columnskey,summary,created,updated,status
maximumIssues20
jqlQueryproject = TIS21 AND issuetype = LiveDefect AND created >= 2021-04-27 AND created <= 2021-05-11 order by created DESC
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7

Incident logs

2021-05-10 Intermittent 'Service unavailable' messages

[No log for the SSL Certificate - a change we made overwrote the updating of the SSL (security) Certificate which rendered the app unfindable. It’s now been changed back]

2021-04-28 PersonOwner sync job failed affecting Person Search

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

TISSS

Display unsupported browser message on Internet Explorer

Steven Howard

Demo from prod

Mitigated issues with multiple draft forms being submitted

Steven Howard / Andy Dingley

When multiple draft forms of the same type (e.g. Form R Part A) existed it caused an “infinite spinner” to be displayed instead of loading the list of forms.

Two fixes have been put in place to mitigate this problem
1. When multiple draft forms exist, the latest is chosen and the forms list now displays as normal.
2. When saving a draft the button is disabled to avoid the user accidentally sending multiple copies when double-clicking the button.

It is still possible in extreme circumstances to create duplicate draft forms, the outcome of which is the trainee still being prompted to complete their draft form even after submitted it.
Unfortunately we have some technical limitations to resolve before we can fully avoid this issue but the above mitigations should make it almost impossible during normal usage.

We will monitor for any instances of duplicate drafts during the pilot to help guide priority for further work.

SMS Multi factor authentication

Steven Howard

Demo from prod


Date of birth defaulting to 01/01/1800 when none in TIS

Edward Barclay

Image RemovedImage Added

Reval

Syncing Doctor’s Data from TIS and GMC for differerent connections' logic

Cai Willis

Discussion of current progress of sync process deployment to staging environment

TIS

Unable to save placements (Posts with leading/trailing space)

Reuben Roberts

We identified a problem finding posts with leading (or trailing) space:

Image RemovedImage Added

  • Show Form R tab on prod (but not on NIMDTA) to enable TIS Admins to access submitted Form R’s

  • Display Form R Part B nested data (Type of Work)

john o

Demo from prod

PersonOwner Sync Job made more resilient

Marcello Fabbri (Unlicensed)

ESR

Support the August rotation up to 12 week Code of Practice

Joseph (Pepe) Kelly

Customisable queryqueries in https://build.tis.nhs.uk/metabase/collection/102

Image Added

Objective Key Results (OKRs) Financial Q1

3 week TISSS pilot
24 May - 14 June

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

too early

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

too early

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

too early

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

too early

too early

too early

...

Info

*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:

Trello card
urlhttps://trello.com/b/I2KstFzF/tis-interim-roadmap?menu=filter&filter=label:TIS%20Self-service

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!

...