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:
Info
Focusing on
Team - Revalidation connections
Continue with the private beta and proactively seek user feedback from all Leads and team (who may have own ideas and insights) - will we get the two outstanding tickets completed? Review where we are and work out next step.
Team availability (e.
Team availability (e.g., Leave & Events):
Stan A/L 25th- 31st Oct
Jay 2nd-8th of November
Non-Kanban work (this iteration):
Rob to run a session on Roadmap
Preparation to meet with Revalidation leads.
Quarterly planning-
Work lined up for the iteration
0
Live Defect
From last iteration:
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-5261
: Cai to arrange huddle this afternoon or tomo
Support
Carried over…
Review sync issues in Revalidation - next step = High Level Estimation
Waiting
1
Revalidation - Connections
From last iteration:
Private Beta in flight
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-5152
Private Beta waiting
2
Other Tech improvement
3
Post funding
Waiting
To be refined
Can we look at getting a delivery plan set up so this work can be prioritised and sequenced alongside rolling user feedback. Epic =
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3273
- we queried the scope around delivery plan. Further conversation to fletch some things. Based on discussion around what our actual focus is.
4
Programme Membership
In flight
5
TIS assessment
6
ESR
If there is capacity/willingness to refine:
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4985
17
Data work
From last iterationIf there is capacity/willingness to refine:
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-48384985
17
Data work
From last iteration:
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4620
Further team discussion when Stan returns from A/L
11
Retro actions
LTFT discovery-AdHoc Huddle
Cross-team effort, involving Ade B and Ade A .
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4612
11
Retro actions
LTFT discovery
Cross-team effort, involving Ade B and Ade A .
5118
Discuss moving time for Y&H as it clashes with the Admin Review
Explode-out revalidation to produce a Revalidation Roadmap (does the team want to start to explore this)?
Goal(s) for the next Iteration:
Statement:
Info
Focusing on
Team - Revalidation connections
Continue with the private beta and proactively seek user feedback from all Leads and team (who may have own ideas and insights) - will we get the two outstanding tickets completed? Review where we are and work out next step.
Team availability (e.g., Leave & Events):
Pepe (A/L) 13th-15th Sept
Yafang (A/L) 15th-22nd of Sept
Cai (A/L) 18th-22nd of Sept
Non-Kanban work (this iteration):
Arrange a call with Revalidation leads ( Connections) to ascertain MVP IF WE FEEL that the F1 ticket and sync work will be advanced in this Iteration.
High priority as part of the MVP- with time box for 2 days. To further liaise with Pepe when back. Can we do this and see what tickets are generated as these will need to be assessed in the context of the MVP for Connections.
2
Revalidation - Connections
Private Beta in flight
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4154
Dev plan to finish this ticket in the next one /two days ready to be presented at Review.
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4690
Private Beta feedback
Need to extend the access to the Private Beta, so looking to Ade B to continue a dialogue and to understand likely posy MVP developments and issues.
3
Revalidation designated body merger
I (Rob) needs to develop a ticket for this work. Tow London designated bodies are to become one. Depending on the size of this work (refinement) will determine when it is to be done, so starting this off will be something ASAP. Placeholder -
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-5060
4
Other Tech improvement
In flight - does this involve us?
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-1209
In for development - does these involve us? Is it a Pepe one?
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3162
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4689
5
Changes to email
Specifically I would like to understand how to update all staff emails to NHS.NET (1) on Keycloak and (2) the Reval users who are different? It would be very helpful to get this understood so we can make sure resources are in place to support the change. We now have a spreadsheet from IT with “old” and “new” so we can map the chnges.
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-5061
6
Post funding
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-95
Next
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4875
Would like to progress refining these tickets as they will be the next in line post MVP.
7
Programme Membership
In flight
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3785
What is next to keep this work progressing?
8
BUGS
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4958
Potential ticket to come in to the iteration- impact audit of GMC end of October/November so would be important to get this work submitted.
Explode-out revalidation to produce a Revalidation Roadmap (does the team want to start to explore this)?
Goal(s) for the next Iteration:
Statement:
Info
Focusing on
Team - Revalidation connections
Continue with the private beta and proactively seek user feedback from all Leads and team (who may have own ideas and insights) - will we get the two outstanding tickets completed? Review where we are and work out next step.
Team availability (e.g., Leave & Events):
Pepe (A/L) 31st of Aug- 15th of September
Yafang (A/L) 1st September
Non-Kanban work (this iteration):
Arrange a call with Revalidation leads ( Connections) to ascertain MVP
TBD:
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4876
HLE session held. Rob has an upcoming call with Stephen Loughran to get an email list if possible.(outcome to help support with GMC’s email query)
Review sync issues in Revalidation - next step = High Level Estimation
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4956
Waiting
1
Revalidation - Connections
From last iteration:
Private Beta in flight
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4154
Private Beta waiting
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4690
Private Beta feedback
?Potential Bug ticket to be raised but further looking at is required.- Cai to email GMC Data
Apart from the above two tickets, is there anything else outstanding? What about the observation that the system is slow?- Investigation ticket to be raised if we don’t already have one( To be created after this planning session). AdHoc refinement.
Explode-out revalidation to produce a Revalidation Roadmap (does the team want to start to explore this)?
Goal(s) for the next Iteration:
Statement:
Info
Focusing on
Team - Revalidation connections
Continue with the private beta and proactively seek user feedback from all Leads and team (who may have own ideas and insights) - will we get the two outstanding tickets completed? Review where we are and work out next step.
Team availability (e.g., Leave & Events):
Steve (A/L) 16th to 18th of August
Jay (A/L) 24th and 25th of August
Cai (A/L) 21st of August
Bank Holiday: 28th of August
Non-Kanban work (this iteration):
Arrange a call with Revalidation leads ( Connections) to ascertain MVP
Explode-out revalidation to produce a Revalidation Roadmap (does the team want to start to explore this)?
Goal(s) for the next Iteration:
Statement:
Info
Focusing on
Team - Revalidation connections
Continue with the private beta and proactively seek user feedback from all Leads and team (who may have own ideas and insights) - will we get the two outstanding tickets completed?
Helpful to understand and get a position on the perception that Recommendations is unstable. Suggestions on how to move this forward? Rob to raise a ticket? Spike, High level estimation to discuss around it.
Feedback from Teams→ Connections Private Beta - TIS21 Confluence Space - Confluence (atlassian.net) >> Can we just give this a quick review, including updating recent feedback if applicable. Question >>> Are the above two tickets what has been ID’ed for the Private Beta? @Ade B - can you establish opinion from the Reval Leads on next steps.
2
Connections user research
Carried over from last Planning → Do we need to tidy up the revalidation material on Confluence? ?Team discussion and suggestion re: Reval materials on confluence? Rob started informally logging this and will share when advanced if that’s of interest?
3
Other Tech improvement
New:
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4862
(Cross-team)
Continuing:
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4739
Post funding
From last iteration:
In flight
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4802
Waiting
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-95
To be refined
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4875
ADHOC refinement ?today/tomorrow
Can we look at getting a delivery plan set up so this work can be prioritised and sequenced alongside rolling user feedback. Epic =
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3273
4
Programme Membership
Waiting
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3785
are we intending to bring this in? It is refined and of medium effort.
? → There’s an improvement that Joseph (Pepe) Kelly looked into about changing the way Conditions Of Joining (acceptance) are mapped -
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4759
3 Amigo in this iteration. Not intending to do this work in this Iteration but it will be good to have it refined.
Email Change
Contended for High Level Estimation and to add related stories so these can be prioritised and developed for future work ---
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4876
Friday HLE to scope out this work. P1
6
ESR
MongoDB contract renewal for ESR: We need a ticket.
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4884
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-213
(Tech Improvement)
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4775
17
Data work
From last iteration:
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4838
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4612
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4688
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4620
- To be 3 Amigo’d on the completion of the 4838
11
Retro actions
From last iteration:
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4781
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4882
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4883
LTFT discovery
cross-team effort, involving Ade B in the first instance. ? Need for team update regarding this work.
Assume 4548 makes this ticket unnecessary for the time being?
#8 > Bring in
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4154
Now that the spike has been completed can this ticket be revise, refined and put in.
2
Connections user research
Proactively seek additional feedback. from users on the UR channel, UR to continue to ensure users are engaging with regular updates on Teams. Olasimbo Babalola → can we do an update after planning on work we are looking at, to keep engagement.
Carried over from last Planning → Do we need to tidy up the revalidation material on Confluence? ?Team discussion and suggestion re: Reval materials on confluence? Rob started informally logging this and will share when advanced if that’s of interest?
3
Other Tech improvement
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4739
Post funding
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4802
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-95
get refined and lined-up (ADHoc? Today or tomorrow)
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4805
for investigation
Can we create a UR channel and add the Leads and other participants so we can get QA as appropriate? Rob happy to set this up to follow previous precedent.
Lunch and learn to be arranged: Catherine to put in team’s calendar
4
Programme Membership
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3785
are we intending to bring this in? It is refined and of medium effort.
There’s an improvement that Joseph (Pepe) Kelly looked into about changing the way Conditions Of Joining (acceptance) are mapped - was this done?
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4759
3 Amigo in this iteration.
Email Change
? Spike for an investigation: How do we update TIS admin and revalidation email to the current NHS.NET email: Get a call with the team: Catherine to arrange.
6
ESR
Prevent irreparable loss of the ESR interface due to MongoDB Atlas contract not being in place from 1st Aug. Rob supporting with this query
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-213
(Tech Improvement) conversation on how we achieve the goal of this ticket- we have a blocker: internal blocker - ensure token has the necessary access Do we have a blocker with this ticket due to its length of stay? Do we need extra pair of hands to help move this ticket on?
#6 > Send to GMC comes up as “Save”, but should be “Submit” so it’s clear what's happening? Create new ticket and to be 3 Amigo with Steve ?today
#7 > Bring in
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4526
– To create a new ticket for a specific filter which is addressing programme owner(P2)
#9 > Dummy record removal
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4690
#8 > Bring in
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4154
Creating of Spike ticket
EDIT 14/07 to add that 4154 spike ticket =
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4769
MVP outstanding --- these have gone back to the backlog. Are they necessary for MVP?
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4040
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4039
Aim to get two above tickets refined this Iteration?
*** can we go through the five Epics and ID any tickets not done and work out whether the still have legs? Mini backlog refinement of MVP related. Catherine and Rob to take time and go through this.
2
Connections user research
Proactively seek additional feedback. from users on the UR channel, UR to continue to ensure users are engaging with regular updates and emails
Do we need to tidy up the revalidation material on Confluence? ?Team discussion and suggestion re: Reval materials on confluence
3
Other Tech improvement
Generate stories from MongoDB: Joseph (Pepe) Kelly to create tickets out of this.
cost optimisation
database design
a major version upgrade
4
Programme Membership
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-2403
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3785
There’s an improvement that Joseph (Pepe) Kelly looked into about changing the way Conditions Of Joining (acceptance) are mapped
Bulk uploads
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4651
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4508
5
Post funding UR
Can we get some priority tickets developed so they can be lined up, please? Catherine, James, Ade B and Ade A, Rob etc. Arrange an hour conversation to work out priority tickets.
6
ESR
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-213
(Tech Improvement) conversation on how we achieve the goal of this ticket- we have a blocker: internal blocker - ensure token has the necessary access
Explode-out revalidation to produce a Revalidation Roadmap (does the team want to start to explore this)?
Goal(s) for the next Iteration:
Statement:
Info
Focusing on
Team - Revalidation connections - Go live with three teams ( Wessex, Nwest, London &KSS)as part and cycle round the UR so we can judge immediate improvements.
Team availability (e.g., Leave & Events):
James Harris (A/L) 6th to the 9th of June
Pepe (A/L): Wed 7th (Today) pm
Jay (A/L) half day on Friday 9th June
? Rob (A/L) next week (TBC)
Non-Kanban work (this iteration):
ESR meeting TBA (Rob leading on this)
Work lined up for the iteration
Work lined up for the iteration
Work lined up for the iteration
0
Live Defect
1
Revalidation - Connections
This Iteration:
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4548
Bring in
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4526
– this needs to be refined. It will address a shortfall in usability of the Discrepancy list by having a default filtering by DB. It will also introduce filtering from which we can iterate based on feedback.
Need to review the user research and cycle round any improvements ASAP. These may occur in these two weeks.
>>> Carry on with logic tickets. Do we need to review and clear tickets no longer required etc. (3 Amigos) on the logic tickets this iteration.
>>> Get three teams on production, which should happen today.
2
Connections user research
We need an epic created for this work, so that we can capture and ticket-up things that we agree need to be done either as part of immediate improvement, or for later prioritisation.
Capturing UR work / integrating it into JIRA.
Ade B:
Stage environment
Is there anything we need to do on Stage to synchronise with the GMC update of their Test system?
Would need planning and refinement re: GMC update of stage environment.
TIS
Monitoring and Logging ticket - add Sentry to TCS (& Reference).
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4560
3
Tech improvement
MongoDB:
Updating docs & planning with external expertise to do a subset of:
cost optimisation
database design
a major version upgrade
4
Programme Membership
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-2403
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-2399
(should be mostly Reviews)
Bulk uploads
James would like us to consider these… They are dependent on 2403 (I think). Opinions?
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3822
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-3785
(Tickets to be put in refinement)
5
Post funding UR
When James is back it would be very helpful to start to develop and refine the related user stories, with their priority.
6
ESR
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-213
(Tech Improvement) conversation on how we achieve the goal of this ticket- no current blocker
Explode-out revalidation to produce a Revalidation Roadmap (does the team want to start to explore this)?
Goal(s) for the next Iteration:
Statement:
Info
Focusing on
Team - Revalidation connections - getting towards Live + starting UR
Team availability (e.g., Leave & Events):
Ade A (A/L) 25/5/23
James Harris (A/L) 6/6/23
Rob (A/L) Fri 26 and Tues 30th
Bank Holiday: 29th of May 2023
Non-Kanban work (this iteration):
Discussions: Reval Leads-connection update
Speaking with Wales about what TIS does. Wales are considering alternatives to Intrepid (which was used by HEE & NI before moving to TIS)- Planning to meet again 1st of June
Work lined up for the iteration
Work lined up for the iteration
0
Live Defect
1
Revalidation - Connections
This Iteration:
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4555
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4554
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4548
>>> Carry on with logic tickets. Do we need to review and clear tickets no longer required etc. (3 Amigos) on the logic tickets this iteration.
>>> Have we picked up any other immediate priorities that we need to resolve this iteration?- Clarifying on discrepancies list(for further discussion)
>>> Need to get all Leads on Stage
>>> Prep for one/two teams as early adopters.
2
Connections user research
Can we create an Epic to frame this work? Covers user research and the any improvements that come out of this? This will help with vis Ade B:
3
Tech improvement
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4361
4
Programme Membership
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-2403
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-2399
(should be mostly Reviews)
5
Post funding UR
Session with team on Post Funding (retro action)
Going through needs based on categorisation
Work to start to develop user stories within the Epic. Ade B, James, Catherine and Rob etc( to be considered for next iteration)
6
ESR
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-213
(Tech Improvement) conversation on how we achieve the goal of this ticket- no current blocker
17
Data work
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4567
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4457
11
Retro actions
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4453
? to be discussed with team then( To link this with Stan’s planned work around our Jira dashboard)
Refinement Cross-Team for tickets in backlog TIS21-2399&TIS21-2403. liaising with Trainee team re-moving this tickets forward
Clause: currently not refined-
Cross team refinement
For Yafang and Pepe + trainee team
COJ- trainee team are currently working along side tickets in questioned
? Trainee team need to unblock work to prioritise in order to allow Admin to move work on- Encourage trainee team to bring ? tickets into their own iteration~
7
Technical improvement
9
Post funding UR
User mapping has been done and will be shared with the Team.
Joint working with Data analyst to review feedback of our users
Research plan also to do: to be completed upon Alpha phase
Focus work on this iteration : Post funding, reviewing phase of user feed back
Explode-out revalidation to produce a Revalidation Roadmap
Goal(s) for the next Iteration:
Statement:
Info
Focusing on
Team - Revalidation connections - What value can we deliver?
UR - Post funding Research Plan and user needs to start.
Team availability (e.g., Leave & Events):
Stan(Paternity) 12-18th April
Stan (A/L) 19th-25th April
Cai (A/L) 12th- 14th of April
Steve (A/L) 13th-14th of April
Bank Holiday:
Non-Kanban work (this iteration):
Review survey results. Can we get a call in with Team?
Discussions: Need to get a call in with the team to move work on user management
Work lined up for the iteration
0
Live Defect
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4367
… Just RCA & Actions left?
1
Revalidation - Connections
This Iteration:
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3961
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3962
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3963
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3874
Last Iteration:
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3774
- next work in line (for refinement)
Team meeting to go through Logic tickets and ? re-prioritise as needed and we should put additional tickets into the Ready for Development pile so they can be taken in as required. Currently there is only one ticket
3
TIS (Infrastructure)
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4354
Ongoing work with Pepe and the team
4
Programme Membership
Refinement Cross-Team for tickets in backlog TIS21-2399 &TIS21-2403. liaising with Trainee team re-moving this tickets forward
Clause: currently not refined-
For Admin team to liaise with trainee team re: tickets
7
Technical improvement
High-Level plan & refinement for ESR on ECS work… (Jayanta Saha)
Developers - Designated Body changes - Can we be clear what we doing before 27th to test and investigate and what we are doing after 27th to implement. This may include a tail for further work after the codes have been changed.
Developers - Revalidation connections - What value can we deliver?
Team - To produce a delivery plan for the Connections work.
UR - Resolve what the Revalidation Alpha reporting objectives are?
UR - Post funding Research Plan and user needs to start.
Team availability (e.g., Leave & Events):
Stan(Paternity) 3rd-18th April
Jay (A/L) 13th –31st March
Pepe 4th April TBC
Ade A (A/L) 27th – 31st March
Rob 30th and 31st of March
Easter holiday- 7th and 10th April
Non-Kanban work (this iteration):
Review survey results. Can we get a call in with Team?
Work lined up for the iteration
Work lined up for the iteration
1
Revalidation - Connections
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3774
- next work in line (for
refinement)
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3874
Devs Team meeting to go through Logic tickets and ? re-prioritise as needed
Developers - Designated Body changes - Can we be clear what we doing before 27th to test and investigate and what we are doing after 27th to implement. This may include a tail for further work after the codes have been changed.
Developers - Revalidation connections - What value can we deliver?
Team - To produce a delivery plan for the Connections work.
UR - Resolve what the Revalidation Alpha reporting objectives are?
UR - Post funding Research Plan and user needs to start.
Team availability (e.g., Leave & Events):
Ade A (A/L) 13th -17th March
Stan(A/L) 13th -17th March
Jay (A/L) 13th –31st March
Yafang (A/L) 20th – 24th March
Pepe 22nd-28th March
Ade A (A/L) 27th – 31st March
Non-Kanban work (this iteration):
Review survey results. Can we get a call in with Team?
Explode-out revalidation to produce a Revalidation Roadmap
Goal(s) for the next Iteration:
Statement: Revalidation Connections MVP
Info
Focussing on
Designated Body changes - Can we be clear what we doing before 27th to test and investigate and what we are doing after 27th to implement. This may include a tail for further work after the codes have been changed.
Revalidation connections - What value can we deliver?
To produce a delivery plan for the Connections work. This may determine whether we stop supporting Revalidation V1 on 27th March.
Post funding Research Plan and user needs to start. Is this an epic to be created?
Team availability (e.g., Leave & Events):
User Research Sessions - a number of the team
James H (A/L) 27 Feb- 3rd March
Cai(A/L) 6th -10th of March
Ade A (A/L) 13th -17th March
Stan(A/L) 13th -17th March
Jay (A/L) 13th –31st March
Jay 10th March
Cai 3rd March
Non-Kanban work (this iteration):
Collate ESR work, specifically list of issues. Planning to get a call in. Rob/?Pepe Should happen in the next two weeks, but keeps being bumped. Would like to review Stan’s work as that may help frame the first meeting with ESR Leads.
Review survey results. Can we get a call in with Team.
Work lined up for the iteration
Work lined up for the iteration
1
Revalidation - Connections
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3774
- next work in line (for refinement)
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3874
Look at
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4041
from infrastructure Epic (M effort)
2
Revalidation Connections - Overview
Epic summary
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3592
(2 done and 1 in BL -3734)
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3594
(1 done and 2 BL - 3772 and 3769)
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3595
(1 done and epic completed)
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3596
(Epic not finished with 5 in the BL - 3958; 3961; 3962; 3963; 3964; 3965 *** we must complete refinement of the stories in this Epic ***)
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3735
(2 done, 3 BL - 4041; 4038; 4039; 4040. 1 refinement 3774 (re-sync), 3874 in for dev (above).
Can we devise a sequence of work / plan for how we are going to deliver the MVP and associated change inc. decommissioning V1 >>> the prerequisite is getting the epics completed. <<<
3
Revalidation reporting research / discovery
In progress → UR -
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4013
Next step Alpha? This is primarily data/ user research/? usability testing work so assume no impact on developers (is this a correct assumption)-
Explode-out revalidation to produce a Revalidation Roadmap
Goal(s) for the next Iteration:
Statement:
Info
Focussing on
Revalidation connections - to deliver value
To define the MVP delivery plan so it can be socialised
To continue UR work on reporting into Alpha
Team availability (e.g., Leave & Events):
User Research Sessions - a number of the team
Pepe A/L 7 Feb-20th Feb
Steve A/L 13 Feb -17th Feb
Non-Kanban work (this iteration):
Post funding. Planning to get a call in with James, Ade B, Ade A and Rob
Collate ESR work, specifically list of issues. Planning to get a call in. Rob/?Pepe
Review survey results. Meeting to be planned in to discuss findings with the involvement
Work lined up for the iteration
1
Revalidation - Connections
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3774
- next work in line (for refinement)
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3874
Look at
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4041
from infrastructure Epic (M effort)
2
Revalidation Connections - Overview
Epic summary
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3592
(2 done and 1 in BL -3734)
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3594
(1 done and 2 BL - 3772 and 3769)
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3595
(1 done and epic completed)
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3596
(Epic not finished with 5 in the BL - 3958; 3961; 3962; 3963; 3964; 3965 *** we must complete refinement of the stories in this Epic ***)
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3735
(2 done, 3 BL - 4041; 4038; 4039; 4040. 1 refinement 3774 (re-sync), 3874 in for dev (above).
Can we devise a sequence of work / plan for how we are going to deliver the MVP and associated change inc. decommissioning V1 >>> the prerequisite is getting the epics completed. <<<
3
Revalidation reporting research / discovery
In progress → UR -
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4013
Next step Alpha? This is primarily data/ user research/? usability testing work so assume no impact on developers (is this a correct assumption)-
Explode-out revalidation to produce a Revalidation Roadmap
Goal(s) for the next Iteration:
Statement:
Info
Focussing on
Revalidation connections - to deliver value
To define the MVP delivery plan so it can be socialised
To continue UR work on reporting into Alpha
Team availability (e.g., Leave & Events):
User Research Sessions - a number of the team
Anita on A/L 2nd Feb -10 Feb
13 Feb on A/L
Rob to confirm A/leave next week?
Pepe A/L 7 Feb-20th Feb
Everyone: Hack Retro TBC
Non-Kanban work (this iteration):
Post funding. Planning to get a call in. y
Collate ESR work, specifically list of issues. Planning to get a call in. y
Review survey results (pre-refinement/refinement this iteration). Perhaps Stan can help with result analysis? y
Work lined up for the iteration
1
Revalidation - Connections
Complete →
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4116
Will this unblock the rest of Connections. If so, what next? Investigation
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3774
- next work in line (for refinement)
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3874
Look at
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4041
from infrastructure Epic (M effort)
2
Revalidation Connections - Overview
Epic summary
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3592
(2 done and 1 in BL -3734)
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3594
(1 done and 2 BL - 3772 and 3769)
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3595
(1 done and epic completed)
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3596
(Epic not finished with 5 in the BL - 3958; 3961; 3962; 3963; 3964; 3965 *** we must complete refinement of the stories in this Epic ***)
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-3735
(2 done, 3 BL - 4041; 4038; 4039; 4040. 1 refinement 3774 (re-sync), 3874 in for dev (above).
Can we devise a sequence of work / plan for how we are going to deliver the MVP and associated change inc. decommissioning V1 >>> the prerequisite is getting the epics completed. <<<
3
Revalidation reporting research / discovery
In progress → UR -
Jira Legacy
server
System JIRA
serverId
4c843cd5-e5a9-329d-ae88-66091fcfe3c7
key
TIS21-4013
Next step Alpha? This is primarily data work so assume no impact on developers (is this a correct assumption)-