project management

Implementation of Electronic Medical Record. This has to be completed in MS Project.

 

Due Week 4: Work Breakdown Structure and Network Diagram

 

According to the PMBOK, “the WBS is a deliverable-oriented hierarchical decomposition of the work to be executed by the project team, to accomplish the project objectives and create the required deliverables.” In other words, it lists the tasks, the sub-tasks, the sub-sub-tasks, etc., for the project.

 

For this phase, you will create a Work Breakdown Structure (WBS) for the project you selected during Phase One. Remember that the WBS starts with your major deliverables (that you stated in your Scope Management Plan) at the highest level. The lower levels have the tasks required to complete those deliverables. You should have at least three tasks under each deliverable, but you may have as many tasks as needed to ensure that the deliverables are complete. Review the textbook (and the PMBOK, if you have it) for some suggestions on how best to create a WBS. From your work breakdown structure, develop a project task list with dependencies. Add durations. Then submit a network diagram (using MS Project) and a project schedule.

 

Develop the Work Breakdown Structure

 

Your WBS should have a minimum of 25-30 tasks and be three subtasks deep.

Make sure to use verb/object task names (for example, “Develop software”).

Enter tasks in MS Project.

Create the predecessor relationships to create a network diagram.

DO NOT LINK SUMMARY TASKS!

In the Gantt Chart Tools tab, check the box marked “Outline Number” in the Show/Hide group.

Deliverables:

 

In MS Project, print the following:

Gantt Chart Entry Table on no more than three pages [View > Tables > Entry]

Include Task Name, Duration, Start, Finish, and Predecessor columns with Gantt Chart.

Schedule Table on one page [View > Tables > Schedule]

Include only the default columns (Task Mode, Task Name, Start, Finish, Late Start, Late Finish, Free Slack, Total Slack) and do not include the Gantt Chart. Make sure that all columns are wide enough to read completely.

Network Diagram on one page [Task tab > View group > Network Diagram]

Highlight Critical Path and Circle Milestones.

Justify why you chose your milestones. (Hint: use milestones from the scope statement or look for key merge or burst activities.)

Also print out the network diagram on two to three pages so that task information can be read.

Using the Resource Sheet (View > Resource Sheet) develop and print a list of resources required for your project. Include Max.Units and Costs (Std. Rate, Ovt. Rate, Cost/Use).

If working in a group, include a statement of participation, describing how each person contributed to this project deliverable. Please have each person sign the statement.

DO NOT ASSIGN RESOURCES AT THIS TIME!

 

PROJECT OBJECTIVE

The objective of this project is to have installed a working version of the EHR in production and Test environments with in the next 6 months at cost not to exceed $250,000 with 10-15% recurring maintenance and support cost for useful life of the system.

DELIVERABLES

· Develop specific, measurable goals for EHR

· Assess training needs (computer skills, other)

· Evaluate hardware and networking needs

· Perform workflow analysis

· Evaluate interface and conversion needs

MILESTONES

· Hardware and software installation – Feb 1

· Customized software and configuration – March 8

· Testing of systems and interfaces – May 10

· Chart abstraction and data migration – June – 28

· Training of leadership team, providers, and all staff July – 15

· Mock “go-live” with testing of back-up plans – July – 29

· True GO-Live day Aug – 11

TECHNICAL REQUIREMENTS

· Detailed inventory of printers, faxes, workstations, etc

· New hardware needed and cost

· New network drops

· New Electrical outlets

· Wireless network

· EHR access method (ASP, in house, hosted)

LIMITS AND EXCLUSIONS

· CCHIT and meaningful use criteria are included in the HER

· EHR HIPAA Compliant

· Vendor is responsible for training of staff

· Recurring maintenance and support for useful life of the system

CUSTOMER REVIEW

Elizabeth Baker