Project Brief Template V2.0

Project Brief Template V2.0

SMS/Texting

Project Brief

Version No:0v1 20110911

Issue Date:

Purpose of this Document

version history

Version / Date Issued / Brief Summary of Change / Owner’s Name
For more information on the status of this document, please contact:
Date of Issue

Contents

1.BACKGROUND

2.PROJECT DEFINITION

a) PROJECT Description

b)PROJECT Scope

c)OUTLINE PROJECT DELIVERABLES (AND/OR DESIRED OUTCOMES)

d)Objectives

e)CONSTRAINTS

f)INTERFACES

3. OUTLINE BUSINESS CASE

4.iNITIAL Project Budget

5.PROPOSED PROJECT TIMEFRAME

6.RISKS

7.OTHER RELATED DOCUMENTS

APPENDICES

The purpose of the document is to provide a full and firm foundation for the initiation of the project, the contents are extended and refined into the Project Initiation Document (PID). The Project Brief is a key document in its own right. It is the basis of the PID which gives the direction and scope of the project and forms the ‘contract’ between the Project Management Team and corporate or programme management

Derivation – developed from the Project Mandate supplied at the beginning of the project. If the project is part of a Programme the Programme should provide the Project Brief. In such circumstances it will not have to be derived from a Project Mandate.

If no Project Mandate is provide, the Project Manager has to develop the Project Brief from scratch in discussions with the Customers and Users.

Quality Criteria –

Does it accurately reflect the Project Mandate?

Does it form a firm basis on which to initiate the Project?

Does it indicate how the Customer will assess the acceptability of the finished product(s)?

1.BACKGROUND

Liverpool Community Health hope to trail and to gather evidence to see if text message reminders will have an impact on patient ‘did not attend’ (DNA) rates and to gather valuable patient experience information.

Pockets of work have already been undertaken. RK and KR piloted SMS/Texting with Podiatry and Dietetics. Podiatry showed a small improvement, dietetics didn’t, on the analysis it would seem that that the DNA rate increased.

SC, ML and D W held a conference call with a company called Good4Health on Patient Experience texting in August 2011. LCH has not progressed any further since the initial call took place.

PCMS – LB has also had contact with a company called Healthcare Communications with a view to rolling out SMS appointment reminders for PCMS Practices. This has no progressed any further due to the retendering process.

Explain briefly the context of the project and how the current position of requiring the project has been arrived at.

2.PROJECT DEFINITION

We are hoping to provide an initial months trail from various suppliers in order to analyse the product and any benefits that it might bring. Following this the results from the preferred supplier with be presented to the board for a decision to be made about procuring the product for LCH.

Key Benefits

  • Potential for reduction in DNA rate
  • Potentially enable better use of staff resource
  • Exploit ‘free’ technology to enable cost savings
  • Improve patient experience
  • Provide an additional way for our services to contact patients
  • Provide a feasibility study for future role outs to other services using a managed system

a)PROJECT Description

Explain what the project needs to achieve and express wherever possible in measurable terms.

b)PROJECT Scope

  • Appointment reminders:
  • Changing of Appointments,
  • Patient Experience/ Feedback
  1. Clear outline of where all texting projects are up to?
  2. Support and PM the implementation.
  3. 2/3 types of texting to be tested.
  4. Analysis/Benefits.

c)OUTLINE PROJECT DELIVERABLES (AND/OR DESIRED OUTCOMES)

  • Evidence relating to the effect text message reminders have on patient DNA rates.
  • Evidence relating to the effect text message reminders have on the number

of cancelled appointments that would otherwise have resulted in a DNA.

  • Gathering of patient experience information relating to wider rollout of this service
  • Testing of technological interface with Community PAS systems

d)Objectives

State the expected main project deliverables with sufficient content to enable further detail to be developed during project initiation.State what will be excluded from the scope of the project.

e)CONSTRAINTS

Current figures show 29,818 unique mobile telephone numbers held on IPM. This is just 8.1% of patients. A data capture process with all identified teams will need to be undertaken before implementation of any trial.

f)INTERFACES

Identify interfaces with other projects or systems

3. OUTLINE BUSINESS CASE

Explain why the project is being undertaken and how it supports the corporate strategy or overall Programme needs. The Business Case must be created here, if it is not the subject of a separate document. The success of the project will be measured against this.

Identify plans and state Customer quality expectations.

4.iNITIAL Project Budget

?? Free

5.PROPOSED PROJECT TIMEFRAME

Trails to start Nov/Dec?

6.RISKS

Briefly describe key risks identified and recorded (refer to the Project Risk Log which should be created)

7.OTHER RELATED DOCUMENTS

APPENDICES

Identify any other documents relating to the project.

Version No: Project Brief Template.docDate: 1 Author: Project Brief Template.doc

Top View