nhsdigital / value-set Goto Github PK

In order to promote the survey
I will write some promotion material for the T&C Quarterly newsletter

DOD

• Agreed and approved Communications [Done]
• sent to T&C business admin by 8th August [Done]
• Published in the September newsletter 22 September [DONE]

Link
https://hscic365.sharepoint.com/:w:/r/sites/ValueSetPlatform/Shared%20Documents/General/Marketing%20and%20Comms/Value%20Sets-%20T%26C%20Newsletter-Aug2022.docx?d=wc85a7ebf007445fe986ef55618531eff&csf=1&web=1

Following on from interviews, choose a candidate and make an offer.

D.O.D.

• Offer of a contract made

Accenture may be our best option to advance the development of the VSM Tool this financial year. This is to agree wither we will take that option and the extent of the work to be done.

D.O.D.

• Agreement reached internally on whether we will use Accenture.
• Agreement reached internally and with Accenture regarding the initial scope of the work (if required)

Identify new candidates for the Interaction/Service Designer role and interview

D.O.D.

• Interviews were undertaken and a decision was made regarding suitability for the role.

Around a dozen high-level requirements to be created in order to help frame the high-level scope of the project and inform other work products, such as the Vision Statement.

D.O.D.

• Around a dozen high-level requirements created
• HLRs agreed with Pete Turnbull, Tracy Simmonite and Nicholas Oughtibridge as a minimum

This is a test card for demonstration purposes

D.O.D.

• Demo completed.

Choose short list of candidates for the Service/ Interaction Designer role and commence interviews

D.O.D.

• Interviews commenced

Develop the work products that will define the project scope

D.O.D. (Work products)

• Problem Statement
• Vision
• Initial Benefits Log
• Initial High-level Prioritised Requirements List

Distilling known problems from a collection of a variety of sources into a list that we believe we will be looking to mitigate/resolve through the development of the VSM tool.

Once distilled and agreed, then a more detailed mapping of the problems against the anticipated VSM tool capabilities.

The work should make it clear that the capabilities being delivered through the VSM tool will be targeting the known problems.

D.O.D.

• Questions agreed for care providers
• Questions agreed for suppliers
• Questions agreed for others (TBC)

Start process for recruiting a new UR

D.O.D.

• Approval obtained to recruit
• Interview completed
• Offer made

This is an example ticket

D.O.D.

• Demo'd the example ticket

DoD:

1. Prepare a set of interview questions for UR sessions
2. Some questions will differ for the two groups to be targeted (system suppliers/Mental health service providers)
3. Questions will be a combination of set generic questions and questions around key theme areas that we need to understand and base our emerging insights on
4. Question will need to be reviewed and approved by UR team

Describe the problem that we are trying to solve. (NB: this is subject to change as we discover user needs through UR)

D.O.D.

• Problem statement described clearly and concisely (target - no more than half a page of A4)

DoD:

• Interview discussion guides ready

• Consent forms/additional information ready

• Interview slots scheduled

Create an initial draft SoW for Accenture for the first Development work

D.O.D.

• Draft SoW to a quality to facilitate a discussion with Accenture

Prepare and finalise questions for Discovery interview discussion guide (Kobi, Pete, Peter, Emily)

D.O.D.

• Questions ready for interviews.

Identify new candidates for the Interaction / Service Design role and set up interviews.

D.O.D

• Interviews in the diary

Set up and start to populate spreadsheet for UR stakeholder and user group management

D.O.D.

• Spreadsheet created and all known stakeholders and user groups populated on it

Reach out to Bulletin and CCIO Network contacts for UR engagement

D.O.D.

• All contacts on list contacted

Reach out to individual contact list (provided by Tracy Simmonite)

D.O.D.

• All users on the list contacted.

Create an initial draft of the UCD Approach

D.O.D.

• Document structure to be in place
• Initial draft information in all sections, ready to be fleshed out.

Agree on the objectives for the Accenture SoW (if required - depends on the outcome of #44)

D.O.D.

• High-level objectives agreed - e.g. Architectural design and develop (what?) for Alpha / PoC

The MAD is to describe the approach to managing the project, for example, the Agile approach being taken and how this fits with the UCD Approach, who the key stakeholders are, what roles exist and who will fill them, project governance, key deliverables (work products), etc.

D.O.D.

• The MAD accurately describes the project approach and has been shared with appropriate team members.

Refine comms draft and create new comms for specific user groups

D.O.D.

• Comms wording agreed with Tracy Simmonite, Alan Payne, with input from other SMEs in SNOMED Implementation team.

Agree whether we will make use of the current call-off contract with Accenture in order to start to develop the Value Set Management tool.

D.O.D.

• Agreed between with Pete Turnbull and Paul Chapman that we will make use of this contract.

Create draft mapped problems and capabilities to feed into task #36

D.O.D.

• A draft set of problems and capabilities documented to reflect the current team understanding of each.

Agree on the problem statement with key stakeholders in order to create a defined baseline going into UR Discovery.

D.O.D.

• Problem statement agreed with Tracy Simmonite, Pete Turnbull, Ian Ramsey and Nicholas Oughtibridge (as a minimum)

DoD:

• Comms sent to System suppliers

• Comms sent to Mental Health Service Provider contacts

• Confirm receipt of Comms & follow up

Add additional user groups to be contacted for UR engagement

D.O.D.

• user groups added to contact list

DoD:
Complete the UR Approach document and issue for review
Baseline the UR Approach document once it has been formally reviewed and approved

... add a description...

D.O.D.

• ... add definition of done here...

Set up the first set of user interviews for commencement of the Discovery phase

D.O.D.

• First batch of interviews set up

Develop an initial vision, based on existing material, historic meetings etc. The vision should be business-focussed (not IT focussed) with clarity regarding its scope boundaries.

D.O.D.

• Vision to be good enough to act as a discussion document for use in finalising the vision later.
• Vision to be clear about its boundaries, e.g. are we just trying to support people building/ maintaining value sets or are we aiming to support people developing information standards?

Complete UR pre-discovery

D.O.D.

• Identify user groups who will be contacted during Discovery (NB: 4 groups identified during sprint 2, but need to expand due to lack of response)
• Confirm some named users to support the groups (sizable number of people to get Discovery underway)
• Define and agree approach for each group (1:1, questionnaire, group workshops etc.)
• Agree comms that will be issued to users
• Plan and prepare for first group of user interactions (interviews etc.), including agreeing to questions that we will ask/discussion areas.

Send the UR Survey to the agreed set of initial Terminology & Classification newsletter recipients.
D.o.D.

• Survey issued to Terminology & Classification newsletter recipients