| Table of Contents |
|---|
| Info |
|---|
What is the purpose of planning?
|
Goal(s) for the next Iteration:
Statement:
| Info |
|---|
Focusing on
|
Team availability (e.g., Leave & Events):May Bank Holiday 27th
Yafang A/L : 28th-10th of JuneRob 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
ESR
- we have (1) a live incident to address (data being sent to Trusts in London, KSS and Peninsular (2) an ongoing support issue to understand (data being sent to TIS)Rob to help decide if we put LTFT meeting on the 20th of June on hold? following ESR Query
These are the issues re ESR:
The current TIS->ESR problem raised on Friday - this is a live incident - data being sent to Trusts in London, KSS and Peninsular
The current ESR->TIS problem (address data) which Anita has clocked around support - this has apparently been going on for a year
The lack of formalised user support around ESR is an issue - need to understand what users expect in this space
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
A wider issue over data flows between TIS Admin, TSS and ESR. A simplified view to help people understand the data flows, what d
Goal(s) for the next Iteration:
Statement:
| Info |
|---|
Focusing on
|
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
Work lined up for the iteration |
|---|
Work lined up for the iteration | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0 | Live Defect |
| ||||||||||||||||
| Support | |||||||||||||||||
1 | Post Funding |
| ||||||||||||||||
2 | Cognito Migration |
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:
| ||||||||||||||||
4 | Programme Membership | In flight
| ||||||||||||||||
5 | TIS assessment |
| ||||||||||||||||
6 | ESR |
| ||||||||||||||||
17 | Data work | From last iteration and continue into new iteration:
| ||||||||||||||||
11 | Retro actions |
| ||||||||||||||||
| BAs and UR work LTFT Alpha |
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 Ade Babalola: LTFT Discovery Plan.xls
| ||||||||||||||||
12 | Roadmap review | |||||||||||||||||