Versions Compared

Old Version 1

changes.mady.by.user Andy Nash

Saved on

compared with

New Version 2

changes.mady.by.user Andy Dingley

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-09-15 AND created <= 2021-09-28) OR (status changed to done after "2021/09/14 11:00")) order by created DESC
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7

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

TISSS

Reval

TIS

Reference data management improvements

Andy Dingley

Previously many reference types could not be properly managed due the status field being missing.
Creation required help from the TIS team to set the status properly and it was not possible to change the status of many of the reference types.

The status field has now been added to most of the reference types, there are a few outliers remaining (e.g. Specialty Group) that will be addressed separately.

In addition, the “Role Category” field has been added to the Role reference type so that it can be properly managed.

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

0.7

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

0.6

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

0.3

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

1.0

...

Reinstated KR#3 in Iteration #6 as we were able able to begin the 2nd Pilot this Quarter. Well done everyone involved!

...

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

...