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 3 Next »

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:

key summary created updated status
Loading...
Refresh

Incident logs

New incidents this iteration:
2021-08-30 GMC sync failed
2021-08-26 TIS down

Left over incidents now fully closed:
2021-08-17 ESR Integration database unavailable
2021-08-02 Placements not being exported to ESR

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

Implement sign-up and sign-in via an authenticator app

john o

Trainee’s FormRs added to metabase for rudimentary reporting

Andy Dingley / Ashley Ransoo / James Harris

https://build.tis.nhs.uk/metabase/dashboard/27

Large trusts able to be synced without manual intervention

Andy Dingley

Some trusts were too large to be properly handled by the self-service sync process, which keeps trainee data up to date with TIS changes. A workaround was available but this required manual intervention and monitoring by the TIS team.

Trainee data related to trust changes are now individually queued and the update is then done one-by-one so that all updates can eventually be processed.

The per-trainee update time is expected to be slightly slower with the approach, but it is more consistent, reliable and gives us the ability to scale in the future (updating a higher number of simultaneous trainees).

Reval

TIS

ESR

NIMDTA

Objective Key Results (OKRs) 2021/22 Q2:

OKR

1st
Iteration

2nd
Iteration

3rd
Iteration

4th
Iteration

5th
Iteration

6th
Iteration

7th
Iteration

Objective: Solve MFA and prepare for the second live pilot

Key Result#1: Run an experiment with existing pilot Trainees on using an Authenticator App. Get sufficient feedback to develop it into a solution for the next pilot.

Too early to score

0.1

0.5

0.6

0.6

Key Result#2: Coordinate Prepare for a 2nd pilot (confirm with teams running ARCPs - ask monthly. Any number would be insightful, ideally between 30-50).

Too early to score

0.1

0.1

0.2

0.3

Key Result#3: Run the 2nd pilot to include live ARCP Form R completion via the app (with associated HEE admin unlocking of Form Rs submitted in error, if needed).

Too early to score

0.1

0.1

0.1

n/a

n/a

n/a

Key Result#4: Ensure data from all fields in Form R is stored in a format enabling it to be extracted on demand for the purposes of reporting.

Too early to score

0.5

0.6

0.6

0.6

Following on from a TISSS call (2021-08-17) where it was confirmed that running the 2nd TISSS pilot within this Quarter was not going to be possible, we removed it from the KR list for our OKRs. Spare effort we have as a result will go towards supporting other services and looking at where we can take KR#4.

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 Review. We absolutely don’t want to stand still. We’re very happy applying the 12th Agile principle of ‘becoming more productive’ to our 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!

  • No labels