Scope Statement, Business Plan Example

Mission Statement

The mission of our organization is to provide technologically integrated services to provide quality care before, during and post care.  Our organization will blend in person admission and consultation with virtual and technological enhancements to bring the best service, support and care to our patients.

Project Objectives

• Create a dashboard tool for patient/medical team collaboration
• Provide a workflow process for patients during admissions
• Increase engagement and data collection by leveraging technology
• Provide communication venues for patients and families
• Provide instant feedback on status, schedule and updates to patients
• Enables line of sight to current medical staff in real time
• Support patient confidentiality while also providing patient records, medical status, medications and upcoming process steps such as treatments and tests
• Increases the patient’s knowledge base by providing educational services, communication to staff and other web-based applications to keep the patient connected with staff and family

Justification

Increasing the quality and quantity of information will provide the patient and the medical staff all of the necessary data to make informed decisions on the care that is provided as well as the care that is expected.  The information is also readily available as the medical staff enters the patient’s location.  This eliminates the potential need to return for records, retrieve lost information or confusing patient information.  There is one source of information that is accessible throughout the facility by those that need the information.

Having the right information and providing the information to the patient creates an environment where the patient is satisfied and the medical staff can make the best decisions necessary for the patient.  Inherently the hospital is in a discomforting and unnatural environment for the patient and providing the key information they need, providing immediate status on their care and enabling reliable communication with their medical staff and family increases the overall quality of the visit and improves the hospital stay.

The primary objective of creating a dashboard for the patient to interact with the medical staff provides a better understanding of their treatment and schedule.  This tool will enable a partnership between the family, patient and medical staff.  Working in a collaborative environment will ensure an overall better experience by the patient.

Implementation Strategy

The implementation of this project will follow the waterfall project management methodology according to the Project Management Book of Knowledge (PMBOK).  The project itself will require implementation of both a technical solution as well as a business process implementation.  The technology implementation will include hardware and software implementation prior to the launch of the Second Life application to the patients and staff.  Concurrently with the hardware and software implementation the second half of the project will focus on the business processes implementation.

The hardware and software project will focus on the implementation of the equipment in the established data center.  The capital equipment will be ordered and the requirements are based upon the system requirements of the application as well as the potential growth and need for servers and infrastructure to support the dashboard applications.  Once the hardware is in place the requirements for software configuration will be reviewed by the business owners to ensure the outlined business processes are coordinated with the functionality of the application.

The business process changes will be outlined based upon the requirements outlined in the project plan documentation.  The project manager has the responsibility to conduct a gap analysis and provide the necessary solutions to meet the scope of the project.  The end users of the system will be trained on the system prior to launch of the application and training material will be provided for both patients and medical staff.

In order to mitigate the risk of launching the application enterprise wide, there will be a limited or pilot release in one area of the hospital that will last fifteen (15) calendar days.  During this time feedback will be obtained through bi-weekly (2 times per week) meetings with staff and surveys conducted by patients.  As feedback is received the necessary project management activities will be implemented prior to launching enterprise wide.  The project will then be rolled out to the entire medical operation for use by all staff and patients.

Project Resources

Completion Date

Schedule Start: September 2013

Completion: December 2013

Measures of Success

Success is ultimately achieved by fulfilling the customer’s needs and expectations.  The goals and objectives of this project have goals that are specific, measurable, achievable, relevant and time-bound.  Each objective will have a pass/fail criteria established with the stakeholders so that at the end of the project the criteria accepted at the beginning of the project will be the same criteria that is measured for project completion.

Success will be a dashboard implementation that meets the scope of the project.  If the scope is altered during the course of the project the acceptance criteria will be adjusted to meet the scope requirements. As will all projects if the scope changes the schedule and cost of the project are also subject to change.  It is up to the project manager to manage the change in scope and limit the ramifications scope creep has on the project.

Assumptions

• Wireless connectivity exists
• Basic understanding of tablet/notebook interfaces exist
• Data integration is seamless between legacy systems and the new dashboard
• Data in the system is relevant and includes the highest level of integrity
• All regulatory and policy requirements are met regarding patients and medical staff information
• Knowledge base provided to clients will be populated with the base level information and will continue to grow as the clients interact with the system

Constraints

• Limited immediate knowledge base
• Queuing process is not optimized during initial implementation
• Feedback is based upon voluntary information
• Benefits are in productivity not direct cost savings or profit