Reference no: EM132402356

Final Project

Scenario – Background :

Good Medicine: Healing a Hospital’s Struggling ED

A 205-bed general medical and surgical hospital in a medically underserved community in Chicago was struggling with an underperforming emergency department (ED). Higher-than normal volume left patients waiting more than two hours to be seen by a doctor and almost eight hours to be admitted. Nearly 8 percent left without being treated at all. The poor experience resulted in patient satisfaction scores in the 4th percentile, and dragged down overall hospital performance.

The parent network had recently revamped operations at another hospital’s ED and decided to try a similar approach at the hospital in question. They brought in Integrated Project Management, Inc. (IPM) to organize and orchestrate an ED optimization program. IPM met with the ED medical director and hospital chief nursing executive to assess the current situation. The goal was to reduce delays in key performance areas, including the ED’s “left without treatment” (LWOT) numbers and increase patient satisfaction levels.

Using a two-phased approach and close collaboration with the hospital team, IPM first led a short engagement to determine the scope of the initiative, identify and prioritize projects within the program, estimate their size, and confirm team members. The second phase involved leading the project teams to prepare the detailed plans and implement them and ultimately, help get the stressed ED on track.

The process resulted in a complete redesign of the ED structure, from adding an RN and care provider to the triage area, to expanding the floor design with an additional nurses’ station. Instead of assigning individual nurses to a block of rooms, the new structure created teams of doctors, nurses, and techs (named the “blue” and “red” teams) who would provide care for a designated area. The team model focuses on patient safety and allowed for proper staffing ratios throughout the ED. Other changes included modifying workflow (e.g., establishing the “fast track” rooms next to triage), improving the organization and location of supplies, and changing metric tracking and communication

Project report detail :

The final project management report that you must prepare for this course would deliver the following, please use the case study for providing a context (your capstone project will be the best scenario that you can refer to for this project).

1. A project report that should not be more than 22 pages (appendix not included in the page limit) and should contain the rationale related to the given scenario, there are two parts for the final project

2. PART 1- refers to the sections in a project charter 2 (not more than 11 pages),

a. Project Overview

i. Executive summary

ii. Introduction

iii. Background

iv. Purpose

v. Description

vi. Pre-Project Documentation

b. Project Team and Stakeholders

i. Project Team.

ii. Stakeholder Groups.

c. Project Scope

i. In Scope

ii. Out of Scope

iii. Project Deliverables Planned

iv. Product Deliverables Planned

d. Project Estimates (Schedule & Cost)

i. Summary Level Schedule

ii. Detailed Schedule

iii. Managing Schedule Estimates

e. Project Budget

i. Managing Cost Estimates

f. Project Assumptions

g. Project Risks

h. Project Decision-Making

i. Project Approvals

3. PART 2- refers to the sections in a Project management report 3 (not more than 11 pages)

a. Purpose/background/approach

b. Goals/objectives

c. Scope

d. Deliverables

e. Constraints/assumptions

f. Related projects/critical dependencies

g. Schedule and milestones

h. Budget/cost-benefit assessment

i. Risk assessment

j. WBS

k. Quality management approach

l. Tools and techniques to be used

m. Resource estimates

n. Standards

o. Change and control procedures

p. Roles/responsibilities (include a separate section for project manager role)

q. Work plan

r. Update report when the project is half-completed (50%) hypothetically

s. Team contact directory

t. Approval sign-off form

4. Include project plan with task/activity dependencies, network diagram, and other visual representations/tables as appendices

5. Submit the charter and report as a single word file (include the project plan in the word file, no other file format will be accepted) to the Turnitin (or any other plagiarizing detection tool)

6. The presentation will be made to the class on the last week live session on the final project (not more than 8~10 slides), submit to a separate link, the final project slides

7. Bonus marks will be given to the thoroughness and for detail

Project Presentation :

Each student must present the project report during the week 8 live session (not more than 10 minutes, 2~ 3 minutes for questions) and submit the PowerPoint slides to the link in the Canvas. Minimum 8~10 slides plus cover slide and reference slide.