Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
toc
Table of Contents
Info

What is the purpose of planning?

  1. Identify goal(s) and what needs to be done and ID specific stories against the goal(s)

  2. Planning tickets to bring into Ready for Dev to work on (most of which to complete) in next iteration.

  3. Ditto above, plus check the capacity of the team in the next two weeks (availability etc)

  4. Resolve prioritisation / sequencing

  5. Assessing work in progress on the board against refreshed goals

  6. 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

    •  

 

Team availability (e.g., Leave & Events):

Full capacity

Non-Kanban work (this iteration):

 

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

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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

17

Data work

From last iteration:

11

Retro actions

 

 

LTFT discovery

Cross-team effort, involving Ade B and Ade A .

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-5118
Discuss moving time for Y&H as it clashes with the Admin Review

Ade Babalola: LTFT Discovery Plan.xlsx

 

 

12

Roadmap review

TIS Admin product roadmap.pptx

https://healtheducationengland.sharepoint.com/:x:/r/sites/TISys/_layouts/15/Doc.aspx?sourcedoc=%7B957EBA4D-DEBB-4759-8F3B-7088E94B4519%7D&file=Connection%20iteration.xlsx&action=default&mobileredirect=true&DefaultItemOpen=1&login_hint=Catherine.Odukale%40hee.nhs.uk&ct=1683705063535&wdOrigin=OFFICECOM-WEB.START.EDGEWORTH&cid=ac8ac64f-f6af-4c96-90d1-16e09d23d0b9&wdPreviousSessionSrc=HarmonyWeb&wdPreviousSession=62cd44b3-80ab-49b4-ad29-a21c9e003360

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

 

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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4985

If there is capacity/willingness to refine:

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4985

17

Data work

From last iteration:

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4620
Further team discussion when Stan returns from A/L

11

Retro actions

LTFT discovery

Cross-team effort, involving Ade B and Ade A .

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-5118
Discuss moving time for Y&H as it clashes with the Admin Review

Ade Babalola: LTFT Discovery Plan.xlsx

 

12

Roadmap review

TIS Admin product roadmap.pptx

https://healtheducationengland.sharepoint.com/:x:/r/sites/TISys/_layouts/15/Doc.aspx?sourcedoc=%7B957EBA4D-DEBB-4759-8F3B-7088E94B4519%7D&file=Connection%20iteration.xlsx&action=default&mobileredirect=true&DefaultItemOpen=1&login_hint=Catherine.Odukale%40hee.nhs.uk&ct=1683705063535&wdOrigin=OFFICECOM-WEB.START.EDGEWORTH&cid=ac8ac64f-f6af-4c96-90d1-16e09d23d0b9&wdPreviousSessionSrc=HarmonyWeb&wdPreviousSession=62cd44b3-80ab-49b4-ad29-a21c9e003360

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.

TBD:

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4876
HLE session held.

 

Work lined up for the iteration

0

Live Defect

From last iteration:

Linked to - https://hee-tis.atlassian.net/l/cp/KC01PH24

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4689

Linked to - https://hee-tis.atlassian.net/l/cp/4kLjYF8T status?

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4864
-(AdHoc)

 1

Connections MVP dependent

In for development

Review sync issues in Revalidation

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4956
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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4154
Dev plan to finish this ticket in the next one /two days ready to be presented at Review.

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-5060

4

Other Tech improvement

In flight - does this involve us?

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-1209

In for development - does these involve us? Is it a Pepe one?

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3162

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-5061

6

Post funding

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-95

Next

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3785

What is next to keep this work progressing?

8

BUGS

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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.

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-5007

9

ESR

In flight

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-213
(Tech Improvement) Ongoing work

Lining up ---

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4985

10

Data work

In flight

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4838

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-5019

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4620
-AdHoc Huddle

 

11

Retro actions

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4988

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4955

12 

LTFT discovery

LTFT Discovery Plan.xlsx

 

 

13

Roadmap review

TIS Admin product roadmap.pptx

https://healtheducationengland.sharepoint.com/:x:/r/sites/TISys/_layouts/15/Doc.aspx?sourcedoc=%7B957EBA4D-DEBB-4759-8F3B-7088E94B4519%7D&file=Connection%20iteration.xlsx&action=default&mobileredirect=true&DefaultItemOpen=1&login_hint=Catherine.Odukale%40hee.nhs.uk&ct=1683705063535&wdOrigin=OFFICECOM-WEB.START.EDGEWORTH&cid=ac8ac64f-f6af-4c96-90d1-16e09d23d0b9&wdPreviousSessionSrc=HarmonyWeb&wdPreviousSession=62cd44b3-80ab-49b4-ad29-a21c9e003360

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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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)

Work lined up for the iteration

0

Live Defect

From last iteration:

Linked to - https://hee-tis.atlassian.net/l/cp/KC01PH24

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4689

Linked to - https://hee-tis.atlassian.net/l/cp/4kLjYF8T status?

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4864
-(AdHoc)

Support

Carried over…

Review sync issues in Revalidation - next step = High Level Estimation

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4956

Waiting

 1

Revalidation - Connections

From last iteration:

Private Beta in flight

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4154

Private Beta waiting

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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.

2

Other Tech improvement

Liaise with Andy Dingley re: https://hee-tis.atlassian.net/browse/TIS21-1209

3

Post funding

Waiting

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-95

To be refined

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4875

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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3785

5

TIS assessment

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4958

6

ESR

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-213
(Tech Improvement)

If there is capacity/willingness to refine:

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4985

17

Data work

From last iteration:

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4838

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4620
-AdHoc Huddle

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4612

11

Retro actions

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4988

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4955

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

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4417

Ade Babalola: LTFT Discovery Plan.xlsx

 

12

Roadmap review

TIS Admin product roadmap.pptx

https://healtheducationengland.sharepoint.com/:x:/r/sites/TISys/_layouts/15/Doc.aspx?sourcedoc=%7B957EBA4D-DEBB-4759-8F3B-7088E94B4519%7D&file=Connection%20iteration.xlsx&action=default&mobileredirect=true&DefaultItemOpen=1&login_hint=Catherine.Odukale%40hee.nhs.uk&ct=1683705063535&wdOrigin=OFFICECOM-WEB.START.EDGEWORTH&cid=ac8ac64f-f6af-4c96-90d1-16e09d23d0b9&wdPreviousSessionSrc=HarmonyWeb&wdPreviousSession=62cd44b3-80ab-49b4-ad29-a21c9e003360

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

Work lined up for the iteration

0

Live Defect

From last iteration:

Linked to - https://hee-tis.atlassian.net/l/cp/KC01PH24

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4687
(AdHoc)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4689

Linked to - https://hee-tis.atlassian.net/l/cp/4kLjYF8T status?

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4864
-(AdHoc)

Support

Carried over…

Review sync issues in Revalidation - next step = High Level Estimation

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4956

Waiting

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4952

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4928
(linked to MVP)

 1

Revalidation - Connections

From last iteration:

Private Beta in flight

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4154

Private Beta waiting

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4690

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

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4954
(preventative) AdHoc

Continuing:

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4862
(Cross-team)

3

Post funding

Waiting

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-95

To be refined

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4875

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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3273
- we queried the scope around delivery plan. Further conversation to fletch some things.

4

Programme Membership

In flight

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3785

TIS Assessment

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4958

 5

Email Change

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4876

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

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-213
(Tech Improvement)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4775
Blocked! There’s a blocker with built server - Raising ?a ticket??? cross-team???Not clear on the blocker-outside this planning.

17

Data work

From last iteration:

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4838

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4612

11

Retro actions

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4955

LTFT discovery

Watching brief. Cross-team effort, involving Ade B in the first instance.

12

Roadmap review

TIS Admin product roadmap.pptx

https://healtheducationengland.sharepoint.com/:x:/r/sites/TISys/_layouts/15/Doc.aspx?sourcedoc=%7B957EBA4D-DEBB-4759-8F3B-7088E94B4519%7D&file=Connection%20iteration.xlsx&action=default&mobileredirect=true&DefaultItemOpen=1&login_hint=Catherine.Odukale%40hee.nhs.uk&ct=1683705063535&wdOrigin=OFFICECOM-WEB.START.EDGEWORTH&cid=ac8ac64f-f6af-4c96-90d1-16e09d23d0b9&wdPreviousSessionSrc=HarmonyWeb&wdPreviousSession=62cd44b3-80ab-49b4-ad29-a21c9e003360

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?

 

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

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4687

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4689


Linked to - https://hee-tis.atlassian.net/l/cp/4kLjYF8T status?

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4864
-

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.


https://healtheducationengland.sharepoint.com/:x:/r/sites/TISys/Shared%20Documents/Admin%20Product%20Team/Revalidation/General%20information/Revalidation%20sync%20issues.xlsx?d=w4fc720a27fa54f30a46409eccbb677bf&csf=1&web=1&e=6YlOWY

 1

Revalidation - Connections

From last iteration:

Private Beta in flight

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4154
Huddle to help progress this ticket ? Today

Private Beta waiting

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4690

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?
@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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4862
(Cross-team)

Continuing:

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4739

Post funding

From last iteration:

In flight

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4802

Waiting

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-95

To be refined

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3273

4

Programme Membership

Waiting

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4876
Friday HLE to scope out this work. P1

6

ESR

  • MongoDB contract renewal for ESR: We need a ticket.

    Jira Legacy
    serverSystem JIRA
    serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
    keyTIS21-4884

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-213
(Tech Improvement)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4775

17

Data work

From last iteration:

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4838

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4612

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4688

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4620
- To be 3 Amigo’d on the completion of the 4838

11

Retro actions

From last iteration:

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4781

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4882

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4883

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

https://healtheducationengland.sharepoint.com/:x:/r/sites/TISys/_layouts/15/Doc.aspx?sourcedoc=%7B957EBA4D-DEBB-4759-8F3B-7088E94B4519%7D&file=Connection%20iteration.xlsx&action=default&mobileredirect=true&DefaultItemOpen=1&login_hint=Catherine.Odukale%40hee.nhs.uk&ct=1683705063535&wdOrigin=OFFICECOM-WEB.START.EDGEWORTH&cid=ac8ac64f-f6af-4c96-90d1-16e09d23d0b9&wdPreviousSessionSrc=HarmonyWeb&wdPreviousSession=62cd44b3-80ab-49b4-ad29-a21c9e003360

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).

 

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

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4687

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4689

Live Defect: 19.7.23 ticket to be created.

 1

Revalidation - Connections

In flight

 

 MVP improvements ready

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4690

 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

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4739

Post funding

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4802

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-95
get refined and lined-up (ADHoc? Today or tomorrow)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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?

17

Data work

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4612

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4688

11

Retro actions

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4781

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4828

12

Roadmap review

TIS Admin product roadmap.pptx

https://healtheducationengland.sharepoint.com/:x:/r/sites/TISys/_layouts/15/Doc.aspx?sourcedoc=%7B957EBA4D-DEBB-4759-8F3B-7088E94B4519%7D&file=Connection%20iteration.xlsx&action=default&mobileredirect=true&DefaultItemOpen=1&login_hint=Catherine.Odukale%40hee.nhs.uk&ct=1683705063535&wdOrigin=OFFICECOM-WEB.START.EDGEWORTH&cid=ac8ac64f-f6af-4c96-90d1-16e09d23d0b9&wdPreviousSessionSrc=HarmonyWeb&wdPreviousSession=62cd44b3-80ab-49b4-ad29-a21c9e003360

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).

    • Develop a delivery plan for the final push to get Connections in a state for adoption - current changes based on the UR. What stories do we have?

    • Demonstrate the MVP is being refined and improved.

 

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):

  1. Pen Test planning in light of Connections release? Not required.

  2. 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

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4687

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4689

 1

Revalidation - Connections

In flight

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4548

MVP improvements ready

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4574

 

MVP improvements from feedback

Feedback from Teams → Connections Private Beta - TIS21 Confluence Space - Confluence (atlassian.net)

#13 >

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4662
(this is a fault/bug)(P1)

#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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4526
– To create a new ticket for a specific filter which is addressing programme owner(P2)

#9 > Dummy record removal

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4690

#8 > Bring in

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4154
Creating of Spike ticket

EDIT 14/07 to add that 4154 spike ticket =
Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4769

MVP outstanding --- these have gone back to the backlog. Are they necessary for MVP?

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4040

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-2403

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4651

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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

17

Data work

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4612

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4688

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4607

11

Retro actions

 

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4751

Plus to be added from yesterday’s session.

12

Roadmap review

TIS Admin product roadmap.pptx

https://healtheducationengland.sharepoint.com/:x:/r/sites/TISys/_layouts/15/Doc.aspx?sourcedoc=%7B957EBA4D-DEBB-4759-8F3B-7088E94B4519%7D&file=Connection%20iteration.xlsx&action=default&mobileredirect=true&DefaultItemOpen=1&login_hint=Catherine.Odukale%40hee.nhs.uk&ct=1683705063535&wdOrigin=OFFICECOM-WEB.START.EDGEWORTH&cid=ac8ac64f-f6af-4c96-90d1-16e09d23d0b9&wdPreviousSessionSrc=HarmonyWeb&wdPreviousSession=62cd44b3-80ab-49b4-ad29-a21c9e003360

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).

    • Socialise user feedback insights to team so that we can make judgements on improvements - which may need to be validated with users.

    • Identified MVP improvements prioritised on the fly.

    • Demonstrate the MVP is being refined and improved.

 

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):

  1. ESR meeting TBA (Rob leading on this)

  2. GMC meeting - cover-off London DB merger, the stage update and support for bulk connections.

  3. Pen Test planning in light of Connections release?

Work lined up for the iteration

Work lined up for the iteration

0

Live Defect

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4687

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4689

 1

Revalidation - Connections

In flight

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4548
Cai and Yafang meeting after planning.

MVP improvements ready

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4574

MVP outstanding (when are these necessary to be done)?

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4040

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4039

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

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4690

#7 > Bring in

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4526
– ? Is this dependent on further insights?

#8 > Bring in

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4154
Would need to be refined.

#13 >

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4662
(ADHOC refinement as a matter of urgency?)

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?

  • cost optimisation

  • database design

  • a major version upgrade

Book second day

4

Programme Membership

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-2403

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-2399
(should be mostly Reviews)

Bulk uploads

James would like us to consider these… They are dependent on 2403 (I think). Opinions?

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4651
→ is this a bug?

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4508

Are we in a position to bring these in? At least to get them refined so they can be lined up.

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3822

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3819

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3785
(Tickets to be put in refinement)

5

Post funding UR

Can we get some priority tickets developed so they can be lined up, please?

6

ESR

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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

KSS ESR issue(s) to be investigated.

17

Data work

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4612
Dependency on 4688

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4688

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4607

11

Retro actions

12

Roadmap review

TIS Admin product roadmap.pptx

https://healtheducationengland.sharepoint.com/:x:/r/sites/TISys/_layouts/15/Doc.aspx?sourcedoc=%7B957EBA4D-DEBB-4759-8F3B-7088E94B4519%7D&file=Connection%20iteration.xlsx&action=default&mobileredirect=true&DefaultItemOpen=1&login_hint=Catherine.Odukale%40hee.nhs.uk&ct=1683705063535&wdOrigin=OFFICECOM-WEB.START.EDGEWORTH&cid=ac8ac64f-f6af-4c96-90d1-16e09d23d0b9&wdPreviousSessionSrc=HarmonyWeb&wdPreviousSession=62cd44b3-80ab-49b4-ad29-a21c9e003360

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):

  1. 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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4548

Bring in

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-2403

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-2399
(should be mostly Reviews)

Bulk uploads

James would like us to consider these… They are dependent on 2403 (I think). Opinions?

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3822

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3819

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-213
(Tech Improvement) conversation on how we achieve the goal of this ticket- no current blocker

17

Data work

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4567

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4457

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4612

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4607

11

Retro actions

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4625
Links in with (2)Connections user research

 

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4626

12

Roadmap review

TIS Admin product roadmap.pptx

https://healtheducationengland.sharepoint.com/:x:/r/sites/TISys/_layouts/15/Doc.aspx?sourcedoc=%7B957EBA4D-DEBB-4759-8F3B-7088E94B4519%7D&file=Connection%20iteration.xlsx&action=default&mobileredirect=true&DefaultItemOpen=1&login_hint=Catherine.Odukale%40hee.nhs.uk&ct=1683705063535&wdOrigin=OFFICECOM-WEB.START.EDGEWORTH&cid=ac8ac64f-f6af-4c96-90d1-16e09d23d0b9&wdPreviousSessionSrc=HarmonyWeb&wdPreviousSession=62cd44b3-80ab-49b4-ad29-a21c9e003360

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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4555

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4554

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4361

4

Programme Membership

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-2403

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-213
(Tech Improvement) conversation on how we achieve the goal of this ticket- no current blocker

17

Data work

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4567

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4457

11

Retro actions

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4453
? to be discussed with team then( To link this with Stan’s planned work around our Jira dashboard)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4570
: Ade B to guide on this on post funding.

12

Roadmap review

TIS Admin product roadmap.pptx

https://healtheducationengland.sharepoint.com/:x:/r/sites/TISys/_layouts/15/Doc.aspx?sourcedoc=%7B957EBA4D-DEBB-4759-8F3B-7088E94B4519%7D&file=Connection%20iteration.xlsx&action=default&mobileredirect=true&DefaultItemOpen=1&login_hint=Catherine.Odukale%40hee.nhs.uk&ct=1683705063535&wdOrigin=OFFICECOM-WEB.START.EDGEWORTH&cid=ac8ac64f-f6af-4c96-90d1-16e09d23d0b9&wdPreviousSessionSrc=HarmonyWeb&wdPreviousSession=62cd44b3-80ab-49b4-ad29-a21c9e003360

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 - What value can we deliver?

  • UR - Post funding Research Plan and user needs to start.

 

Team availability (e.g., Leave & Events):

  • Yafang15th -19th of May

Bank Holiday: 29th of May 2023

Non-Kanban work (this iteration):

  1. 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:

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3734

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4157

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4510

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4510

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4526
-Epic? Is this post MVP improvement work led by the UR and prob FE too.

https://healtheducationengland.sharepoint.com/:x:/r/sites/TISys/_layouts/15/Doc.aspx?sourcedoc=%7B957EBA4D-DEBB-4759-8F3B-7088E94B4519%7D&file=Connection%20iteration.xlsx&action=default&mobileredirect=true&DefaultItemOpen=1&login_hint=Catherine.Odukale%40hee.nhs.uk&ct=1683705063535&wdOrigin=OFFICECOM-WEB.START.EDGEWORTH&cid=ac8ac64f-f6af-4c96-90d1-16e09d23d0b9&wdPreviousSessionSrc=HarmonyWeb&wdPreviousSession=62cd44b3-80ab-49b4-ad29-a21c9e003360

 

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

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4453

 

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4529

11

Roadmap review

Can we just sense check? TIS Admin product roadmap.pptx

https://healtheducationengland.sharepoint.com/:x:/r/sites/TISys/_layouts/15/Doc.aspx?sourcedoc=%7B957EBA4D-DEBB-4759-8F3B-7088E94B4519%7D&file=Connection%20iteration.xlsx&action=default&mobileredirect=true&DefaultItemOpen=1&login_hint=Catherine.Odukale%40hee.nhs.uk&ct=1683705063535&wdOrigin=OFFICECOM-WEB.START.EDGEWORTH&cid=ac8ac64f-f6af-4c96-90d1-16e09d23d0b9&wdPreviousSessionSrc=HarmonyWeb&wdPreviousSession=62cd44b3-80ab-49b4-ad29-a21c9e003360

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 (A/L) 25-28th April

  • ? Rob (A/L) 5th May

Bank Holiday: 1st of May and 8th of May

Non-Kanban work (this iteration):

  1. 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:

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3961

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3962

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3963

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4038

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3772

 

3

TIS (Infrastructure)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4354
Ongoing work with Pepe

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)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-213

There is some additional Tech Improvement that doesn’t directly involve services for the Connections MVP similar to

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3874
Tech team sharing

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 - 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):

  1. 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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4367
… Just RCA & Actions left?

 1

Revalidation - Connections

This Iteration:

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3961

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3962

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3963

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3874

Last Iteration:

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-213

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3874

Not refined but need to do (sorry from Joseph (Pepe) Kelly ):

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4370

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

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4368

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4369

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4319
this work to be linked with Stan’s Jira Dashboard

 

11

Roadmap review

Can we just sense check? TIS Admin product roadmap.pptx

Explode-out revalidation to produce a Revalidation Roadmap

https://app.featuremap.co/m/mahTIp/mvp-definitive-list-of-doctors-currently-connected-to-a-db-as-mirrored-on-gmc-connect-and-the-ab

 

 

Goal(s) for the next Iteration:

Statement:

Info

Focussing on

  • 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):

  1. 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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3774
- next work in line (for

refinement)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3874

Devs Team meeting to go through Logic tickets and ? re-prioritise as needed

2

Merger

Release Plan for NHS E Restructure GMC Changes

Revalidation Connections - Overview

Summary of work done and work to do - formation of a delivery plan
https://hee-tis.atlassian.net/l/cp/zd0imJxs

3

Certification

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4320

4

Programme Membership

Refinement Cross-Team for tickets in backlog TIS21-2399 &TIS21-2403.

?

5

Bulk Upload

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3949

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

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4318

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4319

 

11

Roadmap review

Can we just sense check? TIS Admin product roadmap.pptx

Explode-out revalidation to produce a Revalidation Roadmap

https://app.featuremap.co/m/mahTIp/mvp-definitive-list-of-doctors-currently-connected-to-a-db-as-mirrored-on-gmc-connect-and-the-ab

Goal(s) for the next Iteration:

Statement:

Info

Focussing on

  • 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):

  1. 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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3774
- next work in line (for refinement)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3874

2

Merger

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4290

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4289

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4293

Revalidation Connections - Overview

Summary of work done and work to do - formation of a delivery plan
https://hee-tis.atlassian.net/l/cp/zd0imJxs

3

ESR

Ready → File management →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-146

4

Programme Membership

Refinement Cross-Team for tickets in backlog TIS21-2399 &TIS21-2403.

?

5

Bulk Upload

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3949

6

Data work

7

Technical improvement

8

Revalidation reporting research / discovery

In progress → UR -

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4013

Resolve Alpha approach

9

Post funding UR

Research plan and user mapping

Start the research

10

Retro actions

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4318

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4319

 

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4217

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4282

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4283

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

  • 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):

  1. 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.

  2. 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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3774
- next work in line (for refinement)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3874

Look at

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4041
from infrastructure Epic (M effort)

Revalidation Connections - Overview

Epic summary

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3592
(2 done and 1 in BL -3734)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3594
(1 done and 2 BL - 3772 and 3769)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3595
(1 done and epic completed)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4013

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 →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-146

5

Programme Membership

Refinement Cross-Team for tickets in backlog TIS21-2399 &TIS21-2403.

6

Bulk Upload

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3949

7

Data work

ESR reporting →

8

Technical improvement

9

Retro actions

(new) Fiaz liaison →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4103

 

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4217

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4282

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4283

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

  • 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):

  1. Post funding. Planning to get a call in with James, Ade B, Ade A and Rob

  2. Collate ESR work, specifically list of issues. Planning to get a call in. Rob/?Pepe

  3. 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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3774
- next work in line (for refinement)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3874

Look at

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4041
from infrastructure Epic (M effort)

Revalidation Connections - Overview

Epic summary

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3592
(2 done and 1 in BL -3734)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3594
(1 done and 2 BL - 3772 and 3769)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3595
(1 done and epic completed)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4013

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 →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-146

5

Programme Membership

Refinement Cross-Team for tickets in backlog TIS21-2399 &TIS21-2403.

6

Bulk Upload

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3949

7

Data work

ESR reporting →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3980
  Stan to create Bug ticket as a follow on work in the iteration.

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4221

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4004

8

Technical improvement

Trainee team ticket we need sight of →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-532

9

Retro actions

(new) Workshop for Jira →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4102

(new) Fiaz liaison →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4103

 

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4133

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4217

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

  • 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):

  1. Post funding. Planning to get a call in. y

  2. Collate ESR work, specifically list of issues. Planning to get a call in. y

  3. 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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4116
Will this unblock the rest of Connections. If so, what next? Investigation

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3774
- next work in line (for refinement)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3874

Look at

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4041
from infrastructure Epic (M effort)

Revalidation Connections - Overview

Epic summary

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3592
(2 done and 1 in BL -3734)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3594
(1 done and 2 BL - 3772 and 3769)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3595
(1 done and epic completed)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4013

Next step Alpha? This is primarily data work so assume no impact on developers (is this a correct assumption)-

4

ESR

Ready → File management →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-146

5

Programme Membership

Refinement Cross-Team for tickets in backlog TIS21-2399 &TIS21-2403.

6

Bulk Upload

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3949

7

Data work

ESR reporting →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3980
  Stan to create Bug ticket as a follow on work in the iteration.

8

Technical improvement

Trainee team ticket we need sight of →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-532

9

Retro actions

Review attendance →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4004

(new) Workshop for Jira →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4102

(new) Fiaz liaison →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4103

 

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4133

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

  • Revalidation connections - to deliver value

  • To define the MVP plan so it can be socialised

  • To start the UR work on reporting

Team availability (e.g., Leave & Events):

  • User Research Sessions - a number of the team

  • Everyone: Hack Day

Non-Kanban work (this iteration):

  1. Recruitment (Tracker) and update from Anita… https://hee-nhs-tis.slack.com/archives/C02EWCJR1MX/p1669895586096139

  2. Post funding. ?

  3. Collate ESR work, specifically list of issues. (Rob)

  4. NI investigation. Ongoing. (Rob)

  5. GMC show and tell - are there thoughts around this?

  6. Want to resurrect user satisfaction survey, but unsure of timings.

  7. Review survey to go out. Perhaps Stan can help with result analysis?

Work lined up for the iteration

1

Revalidation - Connections

Ready → Maven workflow →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3880

Agree to rapidly refine

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3774
and put at the top of Ready for Development so it is worked on first.

Then once 3774 is advanced work through what else is brought onto the Kanban.

Look at

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4041
from infrastructure Epic (M effort)

2

Revalidation Connections - Overview

Epic summary

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3592
(2 done and 1 in BL -3734)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3594
(1 done and 2 BL - 3772 and 3769)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3595
(1 done and epic completed)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-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

3

Revalidation-related

Ready → Testing →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3880

4

Revalidation reporting research / discovery

In porgress → UR -

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4013

5

ESR

Ready → File management →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-146

6

Programme Refactoring

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-2403
to be refined prob Yafang, James and Reuben

7

Data work

In progress

ESR reporting →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3946

ESR reporting →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3980

Revalidation and Metabase →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3979

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 →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4003

Hack day →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3986

Review attendance →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4004

(new) Workshop for Jira →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4102

(new) Fiaz liaison →

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4103

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4134

10

Roadmap review

Can we just sense check? TIS Admin product roadmap.pptx

Explode-out revalidation to produce a Revalidation Roadmap