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 »

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

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

Typos spotted during the last review have been fixed

‘Minumum’ → ‘Minimum’ (TISSS - Date of Birth validation)

‘Forname’ → ‘Forename’ (TIS - People > Person > FormR)

TISSS

Recreate user directory to update the settings and setup pilot trainee user accounts on new directory

Nothing to demo
We had to recreate the directory that holds the trainee user accounts to allow for longer email addresses. Other settings also changed to enforce MFA and the user migration process improved.

Add latest version of Google Analytics to improve traffic analysis

We have added version 4 of Google Analytics to capture user journeys within a single page application.

Reval

Demo of sync process results

Cai Willis

Demo → show Connected/Disconnected/Exceptions view on staging

TIS

‘Long Term Plan’ Funding Type not showing

Marcello Fabbri (Unlicensed)

Demo on Prod

ESR

Improve monitoring/alerting

Andy Dingley

Nothing to demo.
We have made some improvements to the alerting we have in place and will now be made aware to certain types of issues which were not previously obvious.

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

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

  • No labels