What is the purpose of planning?
Identify goal(s) and what needs to be done and ID specific stories against the goal(s)
Planning tickets to bring into Ready for Dev to work on (most of which to complete) in next iteration.
Ditto above, plus check the capacity of the team in the next two weeks (availability etc)
Resolve prioritisation / sequencing
Assessing work in progress on the board against refreshed goals
Planning is not a refinement session - this is what the Refinement session 2 days before is about
Goal(s) for the next Iteration:
Statement:
Focusing on
Post Funding - continue with progression through the sequence of tickets
Cognito work -
ESR problem solving
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
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)
These are the issues re ESR:
The current TIS->ESR problem raised on Friday - this is a live incident
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, but also would like to do some UR to understand
A wider issue over data flows between TIS Admin, TSS and ESR.
Goal(s) for the next Iteration:
Statement:
Focusing on
Team - Post Funding
Cognito work
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 | TIS21-3273 - Getting issue details... STATUS TIS21-5812 - Getting issue details... STATUS 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 | TIS21-2486 - Getting issue details... STATUS 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: TIS21-5752 - Getting issue details... STATUS |
4 | Programme Membership | In flight
|
5 | TIS assessment |
|
6 | ESR | TIS21-5806 - Getting issue details... STATUS ongoing |
17 | Data work | From last iteration and continue into new iteration: TIS21-5752 - Getting issue details... STATUS |
11 | Retro actions | TIS21-6069 - Getting issue details... STATUS TIS21-6070 - Getting issue details... STATUS |
| BAs and UR work LTFT Alpha | TIS21-5438 - Getting issue details... STATUS 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 | |
Add Comment