Page Comparison

30 Jul 2024

Goal(s) for the next Iteration:

Statement:

Team availability (e.g., Leave & Events):

Sarah → leave to 7 August (back next Thursday)
Rob → leave Friday 2 August 5 to 7 August (back next Thursday)

__________________________________________________________________________

17 Jul 2024

Goal(s) for the next Iteration:

Statement:

Team availability (e.g., Leave & Events):

Sarah leave 19th - 7 August.
Cai half day Mon 22nd.

Rob may take some
Yafang and James - recruit disruption (next Wed/Thurs)

03 Jul 2024

Goal(s) for the next Iteration:

Statement:

Team availability (e.g., Leave & Events):

Rob off on leave Friday 5 July

Tobi - 15-17 July

Cai one day possible

Ade 11-12 July

19 Jun 2024

Goal(s) for the next Iteration:

Statement:

Team availability (e.g., Leave & Events):

Pepe A/L 19-25th of June

Cai A/L 26th-28th

Non-Kanban work (this iteration):

Support work - wash up around the ESR issues for PEN | LDN | KSS. Seek call with ESR Support to discuss. : Meeting to try understand the cause of what happened.

Handover from Catherine and Ade B.? meeting to be arranged for early next week.

LTFT meeting in London for those able to attend.

GMC Training environment off line Wednesday 19 – Friday 21 June > impact? No impact

05 Jun 2024

Goal(s) for the next Iteration:

Statement:

Team availability (e.g., Leave & Events):

Yafang A/L : 28th-7th of June

Rob : probably Friday 14th June

Jay will be taking a day but TBC

Non-Kanban work (this iteration): *** noting we should be articulating UR in tickets, so will be Kanban ***

• User research for user management to be advanced-? possible workshop with the team but TBC by Sarah

• User research for revalidation to be progressed in lead up a meeting with the revalidation leads- Ade B circulated email to team in preparation for the next leads meeting. Next leads meeting is the 13th

• Still with a proposed LTFT face-to-face meeting 20th June. Catherine to send out Agenda on One-Tis Channel.

• ESR (see below)

These are the issues re ESR:

1. Current problem #1 - The current TIS->ESR problem raised on Friday - this is an incident outside our system but we are supporting the process having said that we have also identified areas we could have acted quicker as a result opportunity for lesson learned therefore there is a need to record actions and event leading to the incident for the purpose of code of practice? confluence page?- Ticket will be created by Pepe with sub tasks to reflects Trusts that required support. Data being sent to Trusts in London, KSS and Peninsular

2. Current problem #2 - The current ESR->TIS problem (address data) which Anita has clocked around support - this has apparently been going on for a year-

3. User support - The lack of formalised user support around ESR is an issue - need to understand what users expect in this space

4. Reporting - A question whether we can produce reports that are more informative - including whether data is flowing ticket around this (6135), but also would like to do some UR to understand other needs or improvements

5. Understanding ESR - A wider issue over data flows between TIS Admin, TSS and ESR. A simplified view to help people understand the data flows, what data flows, and when.

6. Review state of ESR - Re-focus on the state of ESR - not sure of the work burden on this.

Kanban

Implementing

• 3162 - Github M/S (Andy D)

• 5812 - <Post Funding> Sync job fundingStatus H/M

• 5752 - <TIS DB to a managed service>DW to cloud native M/S

• 4648 - TSS investigation M/S for information and feedback?

• 6108 - UM research plan

For development

• 161 - <Post Funding> Reconcile posts with positions H/M

• 6080 - <Keycloak-Cognito> Create existing users H/M

• 4747 - RabbitMQ

• 6070 - Trial run

• Unknown ESR tickets

22 May 2024

Goal(s) for the next Iteration:

Statement:

Team availability (e.g., Leave & Events):

May Bank Holiday 27th

Yafang A/L : 28th-10th of June

Rob Tues 28th and/or 29th Wednesday off

Non-Kanban work (this iteration):

User management team meeting.

Meeting the Oriel team tomorrow to go through outstanding developments from Hicom. It won't affect the board but will hopefully give clarity on timescales for the ticket blocked in the backlog