Project Start Date:
Project Finish Date:
|
Name |
Notes |
|---|---|
|
Introduction to SCI Applications |
|
|
Interest in one or more of the SCI
Applications |
Initial contact may be web site, word of mouth, ECCI or just desperation! |
|
Register interest with Sema
Helpdesk |
Interest should be formally registered through Sema helpdesk - this will initiate contact from the SCI Implementation managers. |
|
SCI PROJECT ORGANISATION |
|
|
Liaise with SCI Team |
Meet and discuss requirements, possibilities more in-depth information and possibly a broad view of timescales. Demonstrations to be arranged if relevant. |
|
Establish strong Project
Board |
Include clinicians (both Primary and Secondary care where appropriate for the application to be implemented), finance and IT champions and powerbrokers, should ideally include SCI Implementation manager. Critical that there is a clinical champion. |
|
Identify key roles and responsibilities
within Project Board |
Chair etc |
|
Meet with SCI Team |
Help focus discussions on way forward.... |
|
Agree how project will be
resourced |
Both financially and from the human resource aspect taking into account the commitment required from participating areas eg clinical input for testing, impact on department from process redesign, impact from training etc |
|
Appoint a dedicated Project
Manager |
Essential to success of the project that the PM has only one hat! |
|
Identify key stakeholders and
issues |
Probably requires some 'advertising' and info distribution |
|
Determine
communication/consultation/promotion plan |
How to let the wider Trust(s) know about the plan and obtain buy-in. |
|
Establish project teams/planning
groups |
Including representation from all stakeholders where possible |
|
Nominate/Appoint other resources |
May be dedicated resource or part allocated resource. Clear role responsibility key factor.... |
|
Align with other initiatives (ECCI
etc) |
ECCI, other procurements etc. |
|
PREPARATION |
|
|
Project planning group(s)/Project
Teams |
May be same people! |
|
Identify roles and
responsibilities |
Setting agreed lines of communication could greatly enhance efficiency here. |
|
Meet SCI Implementation team |
Discuss detailed plans and possible timescales |
|
Adopt and adapt generic plan(s) to meet
local need |
Detailed - not high level |
|
Identify roll-out strategy |
To be agreed by Project Board |
|
Produce detailed roll-out plan |
To be agreed by Project Board. To include identified resources. |
|
Identify training resource - facility
and person(s) |
The scope and the scale of the plans and therefore the training implications should be fully considered. This to include basic Windows training as well as the SCI Application training. |
|
Produce detailed training plan |
Discussion with the SCI Training team is recommended prior to planning detail. |
|
Define support requirements |
|
|
Produce detailed support plan |
May include adopting the existing attached SLA if relevant to SCI Applications being implemented. |
|
MILESTONE 1 |
|
|
Meet SCI Implementation team - agree start
date |
When the above is complete, or has a tangible completion date; discuss strategy and agree timescales for implementation. |