Versions Compared

Old Version 95

changes.mady.by.user Reuben Roberts

Saved on

compared with

New Version 96

changes.mady.by.user Doris.Wong

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
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. Review metrics dashboards for potential insights to work on in the coming Iteration

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

  5. Resolve prioritisation / sequencing

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

  7. Planning is not a refinement session - this is what the Refinement session 2 days before is about

22th July 2024 

Kanban board review:

Team capacity:

  1. Naz - 1 day (to be confirmed)
    - half day event on 24/7

  2. Ed - 4 days

  3. Andy - 1 day (to be confirmed)

  4. Reuben - 4 days

Goals for the next two weeks:

Primary Goal

  • Send out Day one notifications

Secondary Goals

  • Action DB data to Tableau report

Research Goal

  • Public Health Works - Understand London’s take on FormR process for public health trainees and speak to LO to agree with the date to bring on board (Nazia AKHTAR )

  • Form R -improvements - Lyn Bradley will co-ordinate LO session to understand FormR info filled in by trainees (Nazia AKHTAR )

  • LTFT - a session for team feedback (team)

  • LO feedback of new starter Pilot - test run for the survey question (Ele Linardou & Kavitha.Shankar )

Other Work

  • Course Manager discovery - the team to look at the recommendation docs and discussions (Ade.Olaiya & Nazia AKHTAR)

  • Leave Manager discovery - Communicating with sub-contractor (Ade.Olaiya )

  • Study leave - discovery to start in Aug, once the discovery is on the way, we can renew the end day (Ade.Olaiya & Nazia AKHTAR )

  • Set up Support session with LOs - common issues that are reported to TSS support desk. Refocus on this in next iteration, once current support email issues are resolved. (Anita Cheng )

  • Tracker for onboarding process - meeting for onboarding process on 23/7 to look at user journey before refining the investigation ticket (team)

Dashboard review

  • Look at the tickets to improve Chatbot in a few iterations

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

  • Touch based with Nick Summerfield and Anita Cheng for support queries (Nazia AKHTAR )

Road Map

  • Programme pilot: look at conclusion and enhancement (Nazia AKHTAR )

  • Connection module: investigation works (Nazia AKHTAR )

  • Add ticket for investigation works on GMC (Nazia AKHTAR )

  • CCT calculator: look at comments and summarise them (Ele Linardou )

Who is leading the meetings in next iteration (link to the wheel)

8th July 2024 

Kanban board review:

...