Terms of Reference for the Insights Network 

 

1.     Organisation

 

1.1.    The Insights network is membership organisation that is managed by the Quality Observatory team.

1.2.    It is anticipated that the work programme and direction of the networks activities will be driven by the member organisations

1.2.1. Members are expected to actively participate in developing the work programme and make suggestions

 

1.3.    Members will be invited to regular update meetings

1.3.1. These meetings will be a mixture of face to face and webinars

1.3.2. We will try to use technologies as much as possible that reduce the expense (in time and money) required to travel to meetings

 

2.     Membership

2.1.    The activities of the network will be funded by an annual subscription

2.2.    The annual subscription fee may change if more organisations join the network

2.3.    It is assumed that most organisation will subscribe at a single “standard” membership level

2.4.    There is an option for different membership levels if there is sufficient demand

2.4.1. These membership levels will have access to fewer features

2.4.2. and no voting rights

2.4.3. no suggestion right

2.5.    Organisations can join part way through the year

2.5.1. Membership fees will be calculated pro-rata

2.5.2. Pro-rata refunds will be issued in year if the number of subscribing organisation triggers a fee change.

2.6.    Organisations can subscribe for more than 1 year if they wish

 

3.     Work Programme

 

3.1.    Members will have responsibility to put forward suggestions for the on-going work programme.

3.1.1. The QO team will assess / scope the suggestions as they are put forward against viability criteria including but not limited to the below:

3.1.1.1.              Assessments will take into account availability of data

3.1.1.2.              Difficulties regarding collation or access

3.1.1.3.              Processing that is required

3.1.1.4.              Technical viability and production / development resource required

3.1.1.5.              Similarity to other requests

3.1.1.5.1.  Where requests are the similar a scoping exercise will be undertaken to determine the viability of amalgamating the requests

Example:  more than one request to include information from provider surveys -> QO team will look at the provider surveys and see if data items are similar and assess the potential to merge into a single data set& work item

3.1.2. Network members are expected to review and discuss the suggestion put forward

 

3.2.   The volume and complexity of work requests will determine if voting / prioritisation processes will need to be applied.

Example: if there are only 2 or 3 straight forward work requests then they might get accepted automatically, if there are 15 work requests some of which could be resource intensive / complex then a prioritisation process may be needed.

 

3.3.    New features / functions or work items will be voted on at the beginning of each development cycle if necessary.

3.3.1. A cycle can have more than one work item

3.3.1.1.              The number of work items is dependent on the resources required

3.3.1.2.              The QO team Network manager will advise and agree the items to be delivered in the cycle

3.3.1.3.              There is no defined time limit to the cycle

3.3.1.3.1.                     It is anticipated that there will be at least 4 cycles in a year

3.3.1.3.2.                     The number of cycles will depend on the number of work items agreed and resource required to deliver them

 

3.4.    Suggestions and feature requests that are not successful can carry forward to the next development cycle.

 

3.5.    The work programme will follow the following pathway :

 

Feature request -> Membership approval -> develop -> test ->refine-> approve -> deploy

 

3.5.1.  And approved work item will need a Sponsor

3.5.1.1.              It is anticipated that the Sponsor would be the feature / work item requester

3.5.1.2.              The Sponsor will be the person responsible for testing, refining and approving the work item

3.5.1.3.              The Sponsor can involve other members in the development programme 

 

3.6.    New feature will be tested and approved on the development platform before being deployed on the Live platform

 

3.7.    Work items can include (but are not limited to) the following  :

3.7.1. New dashboards or Visualisations

3.7.2. Enhancements to existing views

3.7.3. Creation of Tools  or new features

3.7.4. One off analysis or reporting

3.7.5. Data Availability and Quality review

3.7.6. Mapping and Geographical Analysis

3.7.7. Deep Dive / Hot topic data packs

3.7.8. Development of e-learning tools / packs

3.7.9. Workshops / learning events

 

4.     Decision making

 

4.1.    Decisions on the work programme will be made at beginning of each development cycle

4.2.    Each full member gets 1 vote per cycle

4.3.    Work items can carry over from previous cycles

4.3.1. Votes do not carry over from previous cycles, each cycle is started “fresh”

4.3.1.1.              The exception to this may be when there are no new requests & no new members have joined the network in which case work items can be accepted in existing voted priority order – unless there is a desire from the network to vote.

4.4.    The work item(s) with the highest scores will be approved for inclusion in the work programme.

4.5.    At least 60% of the networks membership need to have voted for a work item to be approved 

4.6.    Organisations that have subscribed at a lower membership level have no voting rights

4.7.    Organisations that Join part way through the year will be able to vote from the next cycle after they join.