Set up a meeting in early next week (the week commencing Nov 18)
Target: have a step by step switchover plan alongside the rollback plan
Comms - discuss with Rob
Can we draft and send comms next week (the week commencing Nov 18) ?
Only send comms about Prod changes
Users will have to use a valid email after switchover
We will also need to notify users on the upcoming changes on Stage (maybe banner on the app)3. Stage switchover
Target date: Nov 26
We expect to switchover on 26th and then let the key users finish the tests on the same day, and then verify rollback plan.
Identify key users to do extended testing.
Failure: if deployment fails, and we cannot get Stage fully ready for testing until afternoon, we have to agree to roll back, and then notify users. This will result in a 2nd deployment on Stage on Dec 9
Tobi will be on leave, and we need to seek help from Godstime
Prod switchover:
Target date: Dec 11
Data general
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-1135
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-6642
Data bulk upload
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-1137
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3819
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3822
6
Revalidation performance
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4961
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-6275
flagged!
8
Other work to note
Search
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-6328
flagged
Jenkins –
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-6448
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-2702
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-6674
9
Bugs and live issues
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-6436
BLOCKED
10
Retro
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-6684
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-6760
12
TSS dependencies
13
Roadmap review
________________________________________________
Panel
panelIconId
atlassian-info
panelIcon
:info:
bgColor
#FFEBE6
FOCUS
Post Funding - no development - need to take stock and plan implementation
Keycloak to Cognito - primary focus towards implementation
Revalidation research - should run a ideation session this iteration
Address curriculum bulk upload - raised at review and after inquiry this is the time to do it in the prep new trainees et al.
Set up a meeting in early next week (the week commencing Nov 18)
Target: have a step by step switchover plan alongside the rollback plan
Comms - discuss with Rob
Can we draft and send comms next week (the week commencing Nov 18) ?
Only send comms about Prod changes
Users will have to use a valid email after switchover
We will also need to notify users on the upcoming changes on Stage (maybe banner on the app)3. Stage switchover
Target date: Nov 26
We expect to switchover on 26th and then let the key users finish the tests on the same day, and then verify rollback plan.
Identify key users to do extended testing.
Failure: if deployment fails, and we cannot get Stage fully ready for testing until afternoon, we have to agree to roll back, and then notify users. This will result in a 2nd deployment on Stage on Dec 9
Tobi will be on leave, and we need to seek help from Godstime
Post Funding - continue with progression through the sequence of tickets
Cognito work
Research work - User management research
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
Work lined up for the iteration
Work lined up for the iteration
0
Live Defect
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-6217
Cai to arrange call if need be to support with documentation.
Support
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-6147
1
Post Funding
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3273
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-5812
Ongoing peer review/code review
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-161
2
Cognito Migration
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-6080
yafang to create a ticket for deployment plan as currently we can’t deploy as for when ready. So to reduce interruption we need a deployment plan.
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-2486
for AdHoc refinement this afternoon.
3
Revalidation: UR
Touch base with Ade B
4
Other Tech improvement
From last iteration and continue into new iteration:
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-5752
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3162
brought into iteration by Andy Dingley with Devops input
6
ESR
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-5806
ongoing would require Devops input
17
Data work
From last iteration and continue into new iteration:
Post Funding - continue with progression through the sequence of tickets
ESR problem solving
Cognito work
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:
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
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-
User support - The lack of formalised user support around ESR is an issue - need to understand what users expect in this space
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
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.
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
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
Work lined up for the iteration
Work lined up for the iteration
0
Live Defect
Support
1
Post Funding
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3273
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-5812
Collaborative work between Jay and Yafang but we are mindful that Yafang will be away for the rest of the iteration. Therefore team to step in and support when necessary.
2
Cognito Migration
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-2486
for AdHoc refinement this afternoon.
5887 was collectively agreed to
3
Revalidation: UR
Touch base with Ade B
4
Other Tech improvement
From last iteration and continue into new iteration:
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-5752
4
Programme Membership
In flight
5
TIS assessment
6
ESR
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-5806
ongoing
17
Data work
From last iteration and continue into new iteration:
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-5752
11
Retro actions
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-6069
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-6070
BAs and UR work
LTFT Alpha
Jira Legacy
server
System Jira
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-5438
Cross-team effort, involving Ade B and Ade A .: Naz to guide through the approach we’re taking with Alpha: ? define MVP for both Trainee and Admin
Sarah: User management research to be ticket up for visibility