Current MVPs and likely next increment


This is a page designed to:

  • confirm what we’re currently working on as a team

  • confirm what the MVPs (and likely next increments) are for those things we’re working on - in bulleted prose (for communication with the wider business, not as a checklist of development for ourselves)

  • track changes to these things over time, such that we always have clarity on MVP of work (or the next increment, once we’ve delivered the MVP) as an ‘elevator pitch’ when communicating with stakeholders

  • provide a high level estimate of # of iterations to complete listed work
    [Note to TIS Team: please try to provide an estimate range that gives an indication of both:
    - an optimistic best estimate (whole team effort, with the team free from distractions); and
    - a pessimistic worst estimate (including factors like: team needing to work on other things; upcoming leave; expected LiveDefects (avg from previous iterations); new starters/leavers; maintenance requests on other services…)]

Status

Work area

Date

Description

Status

Work area

Date

Description

Estimated

Reval Connections MVP

8-20 Iterations

Oct 14, 2022

type key summary assignee reporter priority status resolution created updated due
Loading...
Refresh

https://coggle.it/diagram/YzbDMECwZkiUHAgt/t/connections-mvp/4c9f0eed567e1fd297104b3c1f685cf7bd63a786685cf8e98958145f4282def6

 

Done

TIS Self-Service MVP

1 Iteration left
(4.5/5 confidence)

Mar 17, 2021

First cohort of Trainees (c.50, from across LOs, all of whom will be at the point of needing to fill in their Form Rs imminently):

  • have a login to TISSS and know what to use it for and can reset their passwords

  • can access their personal details held on TIS

  • can see their current and future Programme and curriculum membership they are training on

  • can ensure placement details are accurate and have a way of knowing where they are going to be training next

  • have visibility of their assessments including upcoming ones

  • need, and are able, to complete their Form R Parts A and B electronically

  • are able to receive support when they have queries regarding using Trainee Self Service or Submitting specific forms

HEE Admin:

  • are able to access submitted Form R's and unlock/un-submit them from within the TIS app

2021-04-14 - Outstanding estimate of a few days, before doing some live run throughs and quick fixes, before starting the Pilot.

2021-01-08 - Original estimation: 3-4 iterations (mid-Feb --> Mid-Mar)

2021-02-05 - Progress and revised estimation: (1st → 3rd week in March)

2021-02-12 - 4/5 confidence estimate still holds

2021-02-22 - Updated. Behind due to sync service speed issues, interruptions (live defects and other essential TIS/ESR Work) and holidays.

2021-03-05 - Updated. Resolved majority of performance issues. Back to a 1-2 Iterations remaining estimate.

2021-03-17 - Updated. Tidying up sync stuff, and address TISSS Feedback tickets in Backlog/Refinement

https://coggle.it/diagram/YB0lOsDXIkbeiedk/t/tis-ss-pilot/dfc47c8f5e17259a1439edadccfb86b116b4f90f1e1e32ec94dc34cd9557db6d

 

Done

NIMDTA TIS MVP

Aug 18, 2021

All requested Intrepid NIMDTA admins users onboarded on, and are administering Trainees within NI exclusively from the NIMDTA TIS app, the NIMDTA Intrepid app is read-only and can be switched off.

NIMDTA Admins' Administration of Trainees includes:

  • creating, reviewing and updating full Trainee records for Trainees on NIMDTA programmes, including placements, programme memberships, curricula, assessments and rotations

  • ability to see up-to-date basic information about HEE Trainees

  • can get Tableau reports on NIMDTA Trainees via NDW (initially via liaison with James Harris)

HEE Admins will also be able to:

  • see basic up-to-date information about NIMDTA Trainees from within TIS

(Note: for MVP, real-time data synchronisation between TIS and NIMDTA TIS is not yet in place)

Data sync of person details

https://coggle.it/diagram/YAFm97yzjo6hrJj0/t/ni-sync/5dec86da94f7b30c52a5ebdf786558827000613d3885662c38c4306a7d5a8113

Split into smaller MVPs

Reval MVP

Aug 18, 2021

Operations & Access

  • All requested HEE Reval Admins are onboarded and administering the Revalidation process from the new Reval service (Reval, Concerns and Connections)

  • HEE Reval Admins do not need to access GMC Connect to carry out any Revalidation functions.
    (Note: for MVP, reporting on Reval via NDW is not yet in place)

  • Support and future development to be prioritised alongside

 

Application

  • Connections: admins will be able to

    • Add a new connection via the Add Connection filter

    • Remove an existing connection via the Remove Connection filter

    • Review connections discrepancies via the Exceptions filter

    • Ignore connections discrepancies that do not require any action via the Hidden filter

    • These actions will be limited per local office permission set, and only to particular roles

  • Recommendations: Admins will be able to

    • Draft and Review a new Recommendation, depending on their role and local office

    • Submit a Recommendation, depending on their role and local office

    • Review previously drafted and submitted Recommendations

  • Concerns: Admins will be able to

    • Review and update previously entered Concerns per Trainee

    • Add a new Concern to a Trainee’s record

 

2021-04-16 - Updated estimate range (optimistic → pessimistic) of what has been requested 13-23 Iterations (6-12 months).
So we have included the start of a narrative around what the known complexities are, where there is significant uncertainty and what assumptions are being made.
Underlying all of this is the grave concern that we are increasingly expected to develop out a full solution, covering every permutation, rather than the approach we desperately want to take, of focusing on the happy paths of basic functions, and an iterative development approach within a Production environment. The layering of levels of complexity in advance of getting basic functionality released to a testable state will result in more and more pressure for more and more levels of sign off before releasing (precisely because there is increasing uncertainty that we have developed the right thing in the right way). The antidote to this is to put the basic functions out there for people to actually try to use, find issues, decide on priority next steps, and iterate fortnightly.

https://coggle.it/diagram/YHBYbz4M8NIRAgZ1/t/reval-what-is-left-on-reval-mvp-on-the-rhs/475b091dbd7b0031b392bd86be8665428615c108f5651e04c2e39e556f4e8044