| Table of Contents |
|---|
What is the purpose of planning?
Identify goal(s) and what needs| 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):
Full capacity
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 |
|---|
Work lined up for the iteration | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
0 | Live Defect |
| ||||||||
| Support | Carried over… Review sync issues in Revalidation - next step = High Level Estimation Waiting
| ||||||||
1 | Revalidation - Connections | From last iteration: Private Beta in flight
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 =
| ||||||||
4 | Programme Membership | In flight
| ||||||||
5 | TIS assessment |
| ||||||||
6 | ESR | |||||||||
17 | Data work | From last iteration: | ||||||||
11 | Retro actions |
| ||||||||
| LTFT discovery | Cross-team effort, involving Ade B and Ade A .
Ade Babalola: LTFT Discovery Plan.xlsx
| ||||||||
12 | Roadmap review | TIS Admin product roadmap.pptx 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 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:
| ||||||||||||||||
Support | Carried over… Review sync issues in Revalidation - next step = High Level Estimation Waiting | |||||||||||||||||
1 | Revalidation - Connections | From last iteration: Private Beta in flight
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 =
| ||||||||||||||||
4 | Programme Membership | In flight | ||||||||||||||||
5 | TIS assessment | |||||||||||||||||
6 | ESR |
If there is capacity/willingness to refine:
| ||||||||||||||||
17 | Data work | From last iteration:
| ||||||||||||||||
11 | Retro actions | |||||||||||||||||
LTFT discovery | Cross-team effort, involving Ade B and Ade A .
Ade Babalola: LTFT Discovery Plan.xlsx
| |||||||||||||||||
12 | Roadmap review | TIS Admin product roadmap.pptx 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 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.
TBD:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Work lined up for the iteration | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0 | Live Defect | From last iteration: Linked to - https://hee-tis.atlassian.net/l/cp/KC01PH24
Linked to - https://hee-tis.atlassian.net/l/cp/4kLjYF8T status?
| ||||||||||||||||||||||||
1 | Connections MVP dependent | In for development Review sync issues in Revalidation
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
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.
| ||||||||||||||||||||||||
4 | Other Tech improvement | In flight - does this involve us?
In for development - does these involve us? Is it a Pepe one?
| ||||||||||||||||||||||||
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.
| ||||||||||||||||||||||||
6 | Post funding |
Next
Would like to progress refining these tickets as they will be the next in line post MVP. | ||||||||||||||||||||||||
7 | Programme Membership | In flight
What is next to keep this work progressing? | ||||||||||||||||||||||||
8 | BUGS |
| ||||||||||||||||||||||||
9 | ESR | In flight
Lining up ---
| ||||||||||||||||||||||||
10 | Data work | In flight
| ||||||||||||||||||||||||
11 | Retro actions |
| ||||||||||||||||||||||||
12 | LTFT discovery |
| ||||||||||||||||||||||||
13 | Roadmap review | TIS Admin product roadmap.pptx 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 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 | ||||||
|---|---|---|---|---|---|---|
|
Work lined up for the iteration | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0 | Live Defect | From last iteration: Linked to - https://hee-tis.atlassian.net/l/cp/KC01PH24
Linked to - https://hee-tis.atlassian.net/l/cp/4kLjYF8T status?
| ||||||||||||||||||||||||
Support | Carried over… Review sync issues in Revalidation - next step = High Level Estimation
Waiting | |||||||||||||||||||||||||
1 | Revalidation - Connections | From last iteration: Private Beta in flight
Private Beta waiting
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. | ||||||||||||||||||||||||
2 | Other Tech improvement | Liaise with Andy Dingley re: https://hee-tis.atlassian.net/browse/TIS21-1209 | ||||||||||||||||||||||||
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 =
| ||||||||||||||||||||||||
4 | Programme Membership | In flight
| ||||||||||||||||||||||||
5 | TIS assessment |
| ||||||||||||||||||||||||
6 | ESR |
If there is capacity/willingness to refine:
| ||||||||||||||||||||||||
17 | Data work | From last iteration:
| ||||||||||||||||||||||||
11 | Retro actions |
| ||||||||||||||||||||||||
LTFT discovery | Watching brief. Cross-team effort, involving Ade B in the first instance. What stage are we in now? research stage(ongoing) -Sending out invites for interviews
Ade Babalola: LTFT Discovery Plan.xlsx
| |||||||||||||||||||||||||
12 | Roadmap review | TIS Admin product roadmap.pptx 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 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
Work lined up for the iteration | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0 | Live Defect | From last iteration: Linked to - https://hee-tis.atlassian.net/l/cp/KC01PH24
Linked to - https://hee-tis.atlassian.net/l/cp/4kLjYF8T status?
| ||||||||||||||||||||||||
Support | Carried over… Review sync issues in Revalidation - next step = High Level Estimation
Waiting
| |||||||||||||||||||||||||
1 | Revalidation - Connections | From last iteration: Private Beta in flight
Private Beta waiting
Private Beta feedback Apart from the above two tickets, is there anything else outstanding? What about the observation that the system is slow?- | ||||||||||||||||||||||||
2 | Other Tech improvement |
Continuing:
| ||||||||||||||||||||||||
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 =
| ||||||||||||||||||||||||
4 | Programme Membership | In flight
TIS Assessment
| ||||||||||||||||||||||||
5 | Email Change |
HLE session held Can we have a session please to work out what next? Rob has an upcoming call with Stephen Loughran to get an email list if possible. | ||||||||||||||||||||||||
6 | ESR |
| ||||||||||||||||||||||||
17 | Data work | From last iteration:
| ||||||||||||||||||||||||
11 | Retro actions |
| ||||||||||||||||||||||||
LTFT discovery | Watching brief. Cross-team effort, involving Ade B in the first instance. | |||||||||||||||||||||||||
12 | Roadmap review | TIS Admin product roadmap.pptx 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 availability (e.g., Leave & Events):
Pepe ~1-2 days TBA
James (A/L) 4th-11th
Steve (A/L) 7th-18th
Team catch up in LONDON 10.08.23
Rob AL 3/4 August
Non-Kanban work (this iteration):
Work lined up for the iteration | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0 | Live Defect | Linked to - https://hee-tis.atlassian.net/l/cp/KC01PH24
| ||||||||||||||||||||||||||||||||
Support | 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. | |||||||||||||||||||||||||||||||||
1 | Revalidation - Connections | From last iteration: Private Beta in flight
Private Beta waiting
Private Beta feedback 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? | ||||||||||||||||||||||||||||||||
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:
Continuing:
| ||||||||||||||||||||||||||||||||
Post funding | From last iteration: In flight
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 =
| |||||||||||||||||||||||||||||||||
4 | Programme Membership | Waiting
? → There’s an improvement that Joseph (Pepe) Kelly looked into about changing the way Conditions Of Joining (acceptance) are mapped -
| ||||||||||||||||||||||||||||||||
| Email Change | Contended for High Level Estimation and to add related stories so these can be prioritised and developed for future work ---
| ||||||||||||||||||||||||||||||||
6 | ESR |
| ||||||||||||||||||||||||||||||||
17 | Data work | From last iteration:
| ||||||||||||||||||||||||||||||||
11 | Retro actions | From last iteration:
| ||||||||||||||||||||||||||||||||
LTFT discovery | cross-team effort, involving Ade B in the first instance. ? Need for team update regarding this work. | |||||||||||||||||||||||||||||||||
12 | Roadmap review | TIS Admin product roadmap.pptx 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 availability (e.g., Leave & Events):
Pepe on A/L 19.7.23 @14:00 to 21.7.23
Jay on A/L 20/7-21/7
Cai, Stan on 24/7
Steve 20/7
Non-Kanban work (this iteration):
Work lined up for the iteration | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0 | Live Defect |
Live Defect: 19.7.23 ticket to be created. | ||||||||||||||||||||||||
1 | Revalidation - Connections | In flight
MVP improvements ready
MVP improvements from feedback Feedback from Teams → Connections Private Beta - TIS21 Confluence Space - Confluence (atlassian.net) Assume 4548 makes this ticket unnecessary for the time being? #8 > Bring 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. 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 |
| ||||||||||||||||||||||||
Post funding |
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 |
There’s an improvement that Joseph (Pepe) Kelly looked into about changing the way Conditions Of Joining (acceptance) are mapped - was this done?
| ||||||||||||||||||||||||
| 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
| ||||||||||||||||||||||||
17 | Data work |
| ||||||||||||||||||||||||
11 | Retro actions |
| ||||||||||||||||||||||||
12 | Roadmap review | TIS Admin product roadmap.pptx 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 availability (e.g., Leave & Events):
Stan (A/L) 5th - 7th of July
Pepe (A/L) 6th July + probably 11th/12th July
Non-Kanban work (this iteration):
Pen Test planning in light of Connections release? Not required.
Rob / Catherine to check up on preferences for London DB merger and support for bulk upload re connections with GMC.
Work lined up for the iteration |
|---|
Work lined up for the iteration |
|---|
Work lined up for the iteration | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0 | Live Defect |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
1 | Revalidation - Connections | In flight
MVP improvements ready
MVP improvements from feedback Feedback from Teams → Connections Private Beta - TIS21 Confluence Space - Confluence (atlassian.net) #13 >
#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
#9 > Dummy record removal
#8 > Bring in
EDIT 14/07 to add that 4154 spike ticket =
MVP outstanding --- these have gone back to the backlog. Are they necessary for MVP?
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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
4 | Programme Membership |
There’s an improvement that Joseph (Pepe) Kelly looked into about changing the way Conditions Of Joining (acceptance) are mapped | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Bulk uploads |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
17 | Data work |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
11 | Retro actions |
Plus to be added from yesterday’s session. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
12 | Roadmap review | TIS Admin product roadmap.pptx 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 availability (e.g., Leave & Events):
Cai (A/L) 26th- 30th of June
Steve (A/L) 23rd of June
Pepe (A/L) 26th -29th of June (TBC)
James H (A/L)29th-3rd of July
Rob (A/L) prob 26-27 June (TBC)
Non-Kanban work (this iteration):
ESR meeting TBA (Rob leading on this)
GMC meeting - cover-off London DB merger, the stage update and support for bulk connections.
Pen Test planning in light of Connections release?
Work lined up for the iteration |
|---|
Work lined up for the iteration | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0 | Live Defect |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
1 | Revalidation - Connections | In flight
MVP improvements ready
MVP outstanding (when are these necessary to be done)?
MVP improvements from feedback Feedback from Teams → Connections Private Beta - TIS21 Confluence Space - Confluence (atlassian.net) #6 > Send to GMC comes up as “Save”, but should be “Submit” so it’s clear what's happening? #9 > Dummy record removal
#7 > Bring in
#8 > Bring in
#13 >
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2 | Connections user research | Get outputs from the UR sessions analysed and socialised so we can confirm suggested improvements and join up with Teams feedback. User journey outputs? Dependency on insights then to plan team feedback session. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3 | Tech improvement | Generate stories from MongoDB: Joseph (Pepe) Kelly suggesting to create tickets out of this? And this aim to come in in this Iteration?
Book second day | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
4 | Programme Membership |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bulk uploads | James would like us to consider these… They are dependent on 2403 (I think). Opinions?
Are we in a position to bring these in? At least to get them refined so they can be lined up.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
5 | Post funding UR | Can we get some priority tickets developed so they can be lined up, please? | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
6 | ESR |
KSS ESR issue(s) to be investigated. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
17 | Data work |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
11 | Retro actions | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
12 | Roadmap review | TIS Admin product roadmap.pptx 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 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:
Bring in
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).
| |||||||||||||||||||||||||||||||||
3 | Tech improvement | MongoDB: Updating docs & planning with external expertise to do a subset of:
| ||||||||||||||||||||||||||||||||
4 | Programme Membership |
| ||||||||||||||||||||||||||||||||
Bulk uploads | James would like us to consider these… They are dependent on 2403 (I think). Opinions?
| |||||||||||||||||||||||||||||||||
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 |
| ||||||||||||||||||||||||||||||||
17 | Data work |
| ||||||||||||||||||||||||||||||||
11 | Retro actions |
| ||||||||||||||||||||||||||||||||
12 | Roadmap review | TIS Admin product roadmap.pptx 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 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:
>>> 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 | ||||||||||||||||||||||||
3 | Tech improvement |
| ||||||||||||||||||||||||
4 | Programme Membership |
| ||||||||||||||||||||||||
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 |
| ||||||||||||||||||||||||
17 | Data work |
| ||||||||||||||||||||||||
11 | Retro actions |
| ||||||||||||||||||||||||
12 | Roadmap review | TIS Admin product roadmap.pptx 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 availability (e.g., Leave & Events):
Yafang15th -19th of May
Bank Holiday: 29th of May 2023
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 with Ade B and Catherine_ to confirm a date?
Speaking with Wales about what TIS does. Wales are considering alternatives to Intrepid (which was used by HEE & NI before moving to TIS)-
Work lined up for the iteration |
|---|
Work lined up for the iteration | ||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0 | Live Defect | |||||||||||||||||||||||||||||||||||||||||
1 | Revalidation - Connections | This Iteration:
| ||||||||||||||||||||||||||||||||||||||||
3 | TIS (Infrastructure) | |||||||||||||||||||||||||||||||||||||||||
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- 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 | ||||||||||||||||||||||||||||||||||||||||
10 | Retro actions |
| ||||||||||||||||||||||||||||||||||||||||
11 | Roadmap review | Can we just sense check? TIS Admin product roadmap.pptx Explode-out revalidation to produce a Revalidation Roadmap | ||||||||||||||||||||||||||||||||||||||||
Goal(s) for the next Iteration:
Statement:
| Info |
|---|
Focusing on
|
Team availability (e.g., Leave & Events):
Stan (A/L) 25-28th April
? Rob (A/L) 5th May
Bank Holiday: 1st of May and 8th of May
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 27/4/23 with Ade B and Catherine
Work lined up for the iteration |
|---|
Work lined up for the iteration | ||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0 | Live Defect | |||||||||||||||||||||||||||||||||||||||||
1 | Revalidation - Connections | This Iteration:
| ||||||||||||||||||||||||||||||||||||||||
3 | TIS (Infrastructure) |
| ||||||||||||||||||||||||||||||||||||||||
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- Cross team refinement For Yafang and Pepe + trainee team
| ||||||||||||||||||||||||||||||||||||||||
7 | Technical improvement | High-Level plan & refinement for ESR on ECS work… (Jayanta Saha)
There is some additional Tech Improvement that doesn’t directly involve services for the Connections MVP similar to
| ||||||||||||||||||||||||||||||||||||||||
9 | Post funding UR | User mapping has been done and will be shared with the Team. Research plan also to do. Focus work on this iteration : Post funding, gathering user feedback~ | ||||||||||||||||||||||||||||||||||||||||
10 | Retro actions |
| ||||||||||||||||||||||||||||||||||||||||
11 | Roadmap review | Can we just sense check? TIS Admin product roadmap.pptx Explode-out revalidation to produce a Revalidation Roadmap | ||||||||||||||||||||||||||||||||||||||||
Goal(s) for the next Iteration:
Statement:
| Info |
|---|
Focusing on
|
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 |
| ||||||||||||||||||||||||||||||||||||||||
1 | Revalidation - Connections | This Iteration:
Last Iteration:
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) |
| ||||||||||||||||||||||||||||||||||||||||
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)
Not refined but need to do (sorry from Joseph (Pepe) Kelly ):
| ||||||||||||||||||||||||||||||||||||||||
9 | Post funding UR | User mapping has been done and will be shared with the Team. Research plan also to do. Start the research: Ongoing work | ||||||||||||||||||||||||||||||||||||||||
10 | Retro actions |
| ||||||||||||||||||||||||||||||||||||||||
11 | Roadmap review | Can we just sense check? TIS Admin product roadmap.pptx Explode-out revalidation to produce a Revalidation Roadmap | ||||||||||||||||||||||||||||||||||||||||
Goal(s) for the next Iteration:
Statement:
| Info |
|---|
Focussing on
|
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 |
refinement)
Devs Team meeting to go through Logic tickets and ? re-prioritise as needed | ||||||||||||||||
2 | Merger | |||||||||||||||||
2 | Revalidation Connections - Overview | Summary of work done and work to do - formation of a delivery plan | ||||||||||||||||
3 | Certification |
| ||||||||||||||||
4 | Programme Membership | Refinement Cross-Team for tickets in backlog TIS21-2399 &TIS21-2403. ? | ||||||||||||||||
5 | Bulk Upload |
| ||||||||||||||||
6 | Data work | |||||||||||||||||
7 | Technical improvement | |||||||||||||||||
8 | Revalidation reporting research / discovery | In progress → UR - Resolve Alpha approach | ||||||||||||||||
9 | Post funding UR | Research plan and user mapping Start the research: Ongoing work | ||||||||||||||||
10 | Retro actions |
| ||||||||||||||||
11 | Roadmap review | Can we just sense check? TIS Admin product roadmap.pptx Explode-out revalidation to produce a Revalidation Roadmap | ||||||||||||||||
Goal(s) for the next Iteration:
Statement:
| Info |
|---|
Focussing on
|
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?
Work lined up for the iteration |
|---|
Work lined up for the iteration | ||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Revalidation - Connections |
| ||||||||||||||||||||||||||||||||||||||||
2 | Merger |
| ||||||||||||||||||||||||||||||||||||||||
2 | Revalidation Connections - Overview | Summary of work done and work to do - formation of a delivery plan | ||||||||||||||||||||||||||||||||||||||||
3 | ESR | Ready → File management →
| ||||||||||||||||||||||||||||||||||||||||
4 | Programme Membership | Refinement Cross-Team for tickets in backlog TIS21-2399 &TIS21-2403. ? | ||||||||||||||||||||||||||||||||||||||||
5 | Bulk Upload |
| ||||||||||||||||||||||||||||||||||||||||
6 | Data work | |||||||||||||||||||||||||||||||||||||||||
7 | Technical improvement | |||||||||||||||||||||||||||||||||||||||||
8 | Revalidation reporting research / discovery | In progress → UR -
Resolve Alpha approach | ||||||||||||||||||||||||||||||||||||||||
9 | Post funding UR | Research plan and user mapping Start the research | ||||||||||||||||||||||||||||||||||||||||
10 | Retro actions |
| ||||||||||||||||||||||||||||||||||||||||
11 | Roadmap review | Can we just sense check? TIS Admin product roadmap.pptx Explode-out revalidation to produce a Revalidation Roadmap | ||||||||||||||||||||||||||||||||||||||||
Goal(s) for the next Iteration:
Statement: Revalidation Connections MVP
| Info |
|---|
Focussing on
|
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 |
Look at
| ||||||||||||||||||||||||||||||||||||||||
2 | Revalidation Connections - Overview | Epic summary
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 -
Next step Alpha? This is primarily data/ user research/? usability testing work so assume no impact on developers (is this a correct assumption)- | ||||||||||||||||||||||||||||||||||||||||
4 | ESR | Ready → File management →
| ||||||||||||||||||||||||||||||||||||||||
5 | Programme Membership | Refinement Cross-Team for tickets in backlog TIS21-2399 &TIS21-2403. | ||||||||||||||||||||||||||||||||||||||||
6 | Bulk Upload |
| ||||||||||||||||||||||||||||||||||||||||
7 | Data work | ESR reporting → | ||||||||||||||||||||||||||||||||||||||||
8 | Technical improvement | |||||||||||||||||||||||||||||||||||||||||
9 | Retro actions | (new) Fiaz liaison →
| ||||||||||||||||||||||||||||||||||||||||
10 | Roadmap review | Can we just sense check? TIS Admin product roadmap.pptx Explode-out revalidation to produce a Revalidation Roadmap | ||||||||||||||||||||||||||||||||||||||||
Goal(s) for the next Iteration:
Statement:
| Info |
|---|
Focussing on
|
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 |
Look at
| ||||||||||||||||||||||||||||||||||||||||
2 | Revalidation Connections - Overview | Epic summary
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 -
Next step Alpha? This is primarily data/ user research/? usability testing work so assume no impact on developers (is this a correct assumption)- | ||||||||||||||||||||||||||||||||||||||||
4 | ESR | Ready → File management →
| ||||||||||||||||||||||||||||||||||||||||
5 | Programme Membership | Refinement Cross-Team for tickets in backlog TIS21-2399 &TIS21-2403. | ||||||||||||||||||||||||||||||||||||||||
6 | Bulk Upload |
| ||||||||||||||||||||||||||||||||||||||||
7 | Data work | ESR reporting →
| ||||||||||||||||||||||||||||||||||||||||
8 | Technical improvement | Trainee team ticket we need sight of →
| ||||||||||||||||||||||||||||||||||||||||
9 | Retro actions | (new) Workshop for Jira →
(new) Fiaz liaison →
| ||||||||||||||||||||||||||||||||||||||||
10 | Roadmap review | Can we just sense check? TIS Admin product roadmap.pptx Explode-out revalidation to produce a Revalidation Roadmap | ||||||||||||||||||||||||||||||||||||||||
Goal(s) for the next Iteration:
Statement:
| Info |
|---|
Focussing on
|
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 →
Look at
| ||||||||||||||||||||||||||||||||||||||||
2 | Revalidation Connections - Overview | Epic summary
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 -
Next step Alpha? This is primarily data work so assume no impact on developers (is this a correct assumption)- | ||||||||||||||||||||||||||||||||||||||||
4 | ESR | Ready → File management →
| ||||||||||||||||||||||||||||||||||||||||
5 | Programme Membership | Refinement Cross-Team for tickets in backlog TIS21-2399 &TIS21-2403. | ||||||||||||||||||||||||||||||||||||||||
6 | Bulk Upload |
| ||||||||||||||||||||||||||||||||||||||||
7 | Data work | ESR reporting →
| ||||||||||||||||||||||||||||||||||||||||
8 | Technical improvement | Trainee team ticket we need sight of →
| ||||||||||||||||||||||||||||||||||||||||
9 | Retro actions | Review attendance →
(new) Workshop for Jira →
(new) Fiaz liaison →
| ||||||||||||||||||||||||||||||||||||||||
10 | Roadmap review | Can we just sense check? TIS Admin product roadmap.pptx Explode-out revalidation to produce a Revalidation Roadmap | ||||||||||||||||||||||||||||||||||||||||
Goal(s) for the next Iteration:
Statement:
| Info |
|---|
Focussing on
|
Team availability (e.g., Leave & Events):
User Research Sessions - a number of the team
Everyone: Hack Day
Non-Kanban work (this iteration):
Recruitment (Tracker) and update from Anita… https://hee-nhs-tis.slack.com/archives/C02EWCJR1MX/p1669895586096139
Post funding. ?
Collate ESR work, specifically list of issues. (Rob)
NI investigation. Ongoing. (Rob)
GMC show and tell - are there thoughts around this?
Want to resurrect user satisfaction survey, but unsure of timings.
Review survey to go out. Perhaps Stan can help with result analysis?
Work lined up for the iteration | ||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Revalidation - Connections | Ready → Maven workflow →
Agree to rapidly refine
Then once 3774 is advanced work through what else is brought onto the Kanban. Look at
| ||||||||||||||||||||||||||||||||||||||||||||||||
2 | Revalidation Connections - Overview | Epic summary
Can we devise a sequence of work / plan for how we are going to deliver the MVP and associated change inc. decommissioning V1 | ||||||||||||||||||||||||||||||||||||||||||||||||
3 | Revalidation-related | Ready → Testing →
| ||||||||||||||||||||||||||||||||||||||||||||||||
4 | Revalidation reporting research / discovery | In porgress → UR -
| ||||||||||||||||||||||||||||||||||||||||||||||||
5 | ESR | Ready → File management →
| ||||||||||||||||||||||||||||||||||||||||||||||||
6 | Programme Refactoring |
| ||||||||||||||||||||||||||||||||||||||||||||||||
7 | Data work | In progress ESR reporting →
ESR reporting →
Revalidation and Metabase →
| ||||||||||||||||||||||||||||||||||||||||||||||||
8 | Technical improvement | We’ve got a couple of stories related to Live Defects. We’ll focus on those and the tech platform for Connections. | ||||||||||||||||||||||||||||||||||||||||||||||||
9 | Retro actions | Onboarding →
Hack day →
Review attendance →
(new) Workshop for Jira →
(new) Fiaz liaison →
| ||||||||||||||||||||||||||||||||||||||||||||||||
10 | Roadmap review | Can we just sense check? TIS Admin product roadmap.pptx Explode-out revalidation to produce a Revalidation Roadmap | ||||||||||||||||||||||||||||||||||||||||||||||||