PM FPX 4030 Assessment 1 Project Management Plan

Name

Capella University

PM-FPX 4030 Scheduling, Cost, and Quality Management

Prof. Name

Date

PM FPX 4030 Assessment 1 Project Management Plan

Executive Summary

Implementing an electronic medical record (EMR) system can help healthcare organizations improve patient safety, streamline clinical workflows, and make patient information more accessible across multiple locations. For Preventative Care Healthcare Organization (PCHO), an EMR system is a strategic investment designed to replace paper-based processes, support physician satisfaction, strengthen care coordination, and accommodate continued organizational growth.

Over the past five years, PCHO has expanded from one location to five facilities in Peoria, Illinois. Its existing manual recordkeeping processes no longer adequately support the needs of its physicians, Health Information Management (HIM) staff, patients, shareholders, and community. As competing healthcare organizations adopt digital systems, implementing an EMR solution is increasingly important for maintaining operational efficiency and a competitive position.

The proposed EMR project will centralize patient information, improve access to clinical records, reduce documentation-related errors, and support more efficient communication among physicians, laboratories, pharmacies, clinics, and affiliated hospitals. Other anticipated benefits include simplified reporting, improved data analysis, and support for applicable healthcare quality and regulatory requirements (Athenahealth, Inc., 2018).

PM FPX 4030 Assessment 1 Project Management Plan

PCHO’s third-party accounting firm projects that the organization could achieve a 25% increase in profits within the first two years, followed by annual growth of approximately 10% to 15%. These figures are projections rather than guaranteed outcomes and should be evaluated against actual implementation costs, operational savings, and financial performance.

The proposed project has a maximum approved budget of $250,000, with vendor selection subject to physician approval. The project team will evaluate qualified vendors based on technical capabilities, cost, implementation timelines, security requirements, and the ability to support all five locations. A Project Change Control Committee will oversee proposed changes to the project scope, budget, schedule, and quality requirements. A dedicated risk management team will identify potential obstacles and develop appropriate mitigation strategies.

Physicians and HIM personnel will access the system through authorized desktop computers, laptops, tablets, and mobile devices, subject to the organization’s security and access policies. Successful implementation will require adequate staff training, testing, stakeholder communication, and coordination to avoid unnecessary disruption to patient care.

Statement of Work

The statement of work defines the principal activities required to deliver the EMR project. These activities include project approval, vendor evaluation and selection, development of the project charter and scope statement, application installation, system testing, staff training, and implementation across all five PCHO locations.

Budget approval is required for the next quarter to support timely procurement and implementation while maintaining existing healthcare operations and avoiding conflicts with other organizational projects.

Project Scope Management Plan

Project Information

Project name: Preventative Care – Electronic Medical Record (EMR)

Prepared by: Angelo Riccio

Original preparation date: April 15, 2018

Project Overview

Preventative Care is a healthcare organization operating five locations in Peoria, Illinois. Following substantial organizational growth, PCHO plans to replace its manual recordkeeping processes with an EMR system that can support centralized information management and coordinated clinical operations.

The organization will solicit proposals from established EMR vendors and qualified companies developing solutions that meet its requirements. Vendor proposals must demonstrate the ability to deliver a reliable, secure, and scalable system within the approved project constraints.

Business Objectives

The EMR implementation is intended to achieve several operational objectives. First, authorized personnel should be able to retrieve patient records across all five locations. Second, the selected solution should provide browser-based access with minimal technical requirements. Third, centralized physician scheduling should improve appointment coordination and resource utilization. Finally, consolidating application servers at a designated location should simplify system administration and maintenance where technically appropriate.

These objectives should be supported by appropriate safeguards for patient privacy, information security, system availability, and continuity of care.

Required EMR Features

The selected system must support the following core functions:

• Patient demographic and medical information.

• Patient insurance information and billing.

• Patient visits and clinical documentation.

• Physician profiles, appointments, and scheduling.

• Patient allergies and diagnoses.

• Vaccination records.

• Medication orders and electronic prescriptions.

• Laboratory orders and test results.

The vendor must also demonstrate how the system will support reliable data access, appropriate user permissions, and secure information exchange among authorized healthcare personnel.

Project Scope Definition

Work Included in the Project

The approved project scope includes a maximum budget of $250,000, implementation across all five PCHO locations, and an initial target delivery period of 12 months. The vendor must establish connectivity among the facilities and provide the documentation needed to plan, execute, monitor, and control the project.

Required vendor documentation includes the project charter, scope statement, project schedule, cost estimates, risk register, technical requirements, labor requirements, and communication plan.

Work Excluded From the Project

The following items are excluded from the initial project scope:

• Proposals that exceed the approved $250,000 budget without formal authorization for a revised budget.

• Remote physician access as defined in the original scope.

• Engagement of third-party vendors without PCHO’s permission.

Any proposed change to these exclusions must be reviewed through the formal change control process. Remote access and third-party integrations should also be reconsidered if required for security, interoperability, or operational needs.

External Dependencies

No external dependencies were identified in the initial project plan. Nevertheless, the project team should monitor potential dependencies involving hardware availability, internet connectivity, data migration, laboratory interfaces, pharmacy connections, and vendor support because these factors may affect implementation.

Project Assumptions

The project plan assumes that vendors will submit bids by the specified deadlines, comply with the approved budget, and provide realistic implementation schedules. It also assumes that physicians will participate in the vendor evaluation and approve the final selection.

These assumptions should be reviewed during project planning and updated whenever new information becomes available.

Project Constraints

The project must remain within the approved $250,000 budget unless an authorized change is approved. The original plan also requires the vendor to be based in the United States to help control travel expenses. Additional constraints include staff availability, operational demands, implementation deadlines, system compatibility, and the need to maintain patient care throughout the transition.

Project Milestones

The original project schedule identifies the following milestones:

Milestone	Target date
Vendor selection	June 1, 2018
Vendor approval	June 8, 2018
Project start	July 15, 2018
Project completion	December 15, 2018

These dates reflect the original planning document. The project plan also identifies a 12-month implementation period, so the stated milestones should be reconciled before the schedule is approved. A December 15, 2018 completion date would provide substantially less than 12 months from the proposed July 15, 2018 start date.

Primary Project Management Plans

The project will be guided by four primary management plans: scope management, time management, cost management, and quality management. Together, these plans will establish the approved work, schedule, financial limits, performance expectations, and quality controls.

Project Authorization

Formal approval of the project scope statement is required before significant resources are committed. The authorization process should confirm that PCHO leadership, the project manager, physicians, and other designated stakeholders agree on the project objectives, deliverables, exclusions, constraints, and acceptance criteria.

Project Time Management Plan

Introduction

The project time management plan establishes how implementation activities will be scheduled, monitored, and controlled. The original project documentation refers to a Work Breakdown Structure (WBS) that identifies tasks, durations, and dependencies. Vendors must use the approved WBS as the basis for developing a realistic project schedule.

Project Schedule and Gantt Chart

A Gantt chart will present the project schedule visually, showing activities, start and completion dates, dependencies, milestones, and deliverables. The approved schedule baseline will serve as the reference point for evaluating progress and identifying deviations from the plan.

Changes to the approved schedule baseline must be submitted to the Project Change Control Committee for review and authorization. This process helps prevent unapproved changes from affecting the project’s cost, scope, or delivery commitments (Project-Management.com, 2018).

The project manager should review schedule progress regularly and communicate delays promptly. If an activity falls behind schedule, the team should determine whether the delay affects dependent tasks, critical milestones, or the overall implementation date.

Critical Path Analysis

Critical path analysis identifies the sequence of dependent activities that determines the shortest possible project completion time. Tasks on the critical path generally have no scheduling flexibility without affecting the overall delivery date.

For PCHO, the project manager should identify critical activities such as vendor approval, system configuration, data migration, interface development, testing, staff training, and deployment. Delays in these activities may postpone implementation across the five facilities.

Regular critical path reviews will help the project team prioritize resources, address bottlenecks, and make informed decisions about schedule recovery (Schwalbe, 2016).

Project Cost Management Plan

Introduction and Budget

PCHO requires a cost management plan to control the financial resources needed to implement its EMR system. The original approved budget is $250,000, and the project team must evaluate vendor proposals against both cost and the ability to satisfy technical and operational requirements.

The project plan identifies labor and implementation effort over a 12-month period, equivalent to approximately 261 business days under the original estimate. Actual working days will depend on holidays, staffing arrangements, and the final implementation calendar.

Vendor Cost Comparison

Three vendor proposals were identified in the original project plan.

Vendor	Proposed cost	Proposed duration
Vendor A	$225,000	11 months
Vendor B	$225,000	11 months
Vendor C	$250,000	12 months

Vendors A and B offer a proposed cost $25,000 below the budget ceiling and a shorter implementation period. Vendor C uses the entire approved budget and proposes a 12-month schedule. However, the lowest price or shortest timeline should not determine selection by itself. PCHO must also evaluate system functionality, cybersecurity, data migration, interoperability, training, ongoing maintenance, vendor reliability, and total cost of ownership.

Cost Control Thresholds

The original plan identifies a $250,000 approved budget and a potential variance threshold of plus or minus 10%. A 10% variance would equal $25,000, but this monitoring threshold should not be interpreted as permission to spend beyond the approved budget. Any increase that exceeds formal spending authorization must receive appropriate approval before commitments are made.

Microsoft Project or another suitable project management tool can be used to compare planned and actual costs, track commitments, and identify emerging budget risks (Biafore, 2007).

Performance Measurement

Earned Value Management (EVM) will be used at major project milestones to compare completed work with planned progress and actual expenditures. This approach provides a structured way to assess whether the project is progressing efficiently and whether corrective action is required.

Vendors should report the percentage of work completed, costs incurred, upcoming milestones, schedule risks, and anticipated completion dates. These reports will help the project manager evaluate performance and communicate the project’s status to stakeholders (O’Reilly, 2017).

Project Documentation

The project team will maintain a central set of records, including the business case, project charter, scope statement, WBS, project schedule, risk register, communication plan, budget reports, change requests, and lessons-learned documentation. Maintaining accurate records will improve accountability and support future project planning.

Reporting Requirements

Weekly status reports will be distributed to key stakeholders, while executives will receive monthly progress updates. Additional risk reports will be prepared when significant issues arise. Reports should summarize schedule performance, spending, completed deliverables, unresolved risks, and decisions requiring management approval.

Project Quality Management Plan

Introduction

Quality management ensures that the EMR system meets PCHO’s functional requirements and supports safe, reliable clinical operations. Quality should be evaluated throughout planning, configuration, testing, training, and deployment rather than only at the end of the project.

Key quality measures include system availability, testing pass rates, defect frequency, data accuracy, user satisfaction, and the successful completion of required workflows. Security controls and the integrity of patient information should also be assessed before the system is placed into routine use (Schwalbe, 2016).

Quality Planning Tools

Two tools identified in the original project plan are the fishbone diagram and the control chart. These tools support different aspects of quality management. A fishbone diagram helps the project team investigate possible causes of a problem, while a control chart helps determine whether process variation remains within expected limits.

Fishbone Diagram

A fishbone diagram, also known as a cause-and-effect diagram, organizes potential causes of a problem into categories. For example, if EMR testing reveals frequent medication-record errors, the team can investigate whether the issue relates to data migration, system configuration, user training, interface failures, or unclear procedures.

The process begins by defining the problem, identifying relevant cause categories, brainstorming contributing factors, and examining the most plausible root causes. Corrective actions should address verified causes rather than merely treating visible symptoms.

Control Chart

A control chart tracks process measurements over time and compares them with a center line and statistically determined control limits. It can help the project team distinguish routine process variation from unusual patterns that may indicate a problem (American Society for Quality [ASQ], 2018).

For example, the team could monitor software defects identified during testing or the percentage of successful data migration records. Unusual variation should prompt investigation before the issue affects implementation quality or patient care.

Quality Metrics and Out-of-Control Signals

Control charts must be reviewed for out-of-control signals, such as points outside established control limits or nonrandom patterns that suggest a process may have changed. When a potential signal appears, the project team should document the observation, investigate its cause, record the findings, and implement corrective action when necessary.

Earned Value Management will complement these quality activities by providing information about project cost and schedule performance. Although EVM does not directly measure clinical quality, it helps determine whether completed work aligns with the project’s approved financial and scheduling baselines (Deshpande, 2014).

Earned Value Management Metrics

The following metrics will be used to monitor the EMR project’s performance:

• Planned Value (PV): The budgeted value of work scheduled to be completed by a specific date.

• Actual Cost (AC): The actual expenditure incurred for work performed by that date.

• Earned Value (EV): The budgeted value of work actually completed.

• Schedule Variance (SV): The difference between earned value and planned value.

• Schedule Performance Index (SPI): Earned value divided by planned value.

• Cost Variance (CV): The difference between earned value and actual cost.

• Cost Performance Index (CPI): Earned value divided by actual cost.

• Estimate at Completion (EAC): The projected total cost of the project at completion.

These measures provide complementary information. Negative schedule variance and an SPI below 1 indicate that less work has been completed than planned. Positive cost variance and a CPI above 1 indicate that the value of completed work exceeds the actual expenditure.

Earned Value Management Example

Assume that the EMR project has an approved budget of $250,000 and has reached the six-month reporting point. For this example, the project team estimates that the planned value of scheduled work is $130,000, the actual cost is $115,000, and the earned value of completed work is $125,000.

The results are as follows:

Metric	Calculation	Result	Interpretation
Planned Value (PV)	Given	$130,000	Budgeted value of scheduled work
Actual Cost (AC)	Given	$115,000	Expenditure incurred
Earned Value (EV)	Given	$125,000	Budgeted value of completed work
Schedule Variance (SV)	EV − PV	−$5,000	Behind schedule
Schedule Performance Index (SPI)	EV ÷ PV	0.96	Approximately 96% schedule efficiency
Cost Variance (CV)	EV − AC	$10,000	Under budget relative to completed work
Cost Performance Index (CPI)	EV ÷ AC	1.09	Approximately 109% cost efficiency
Estimate at Completion (EAC)	Budget ÷ CPI	Approximately $230,000	Forecast final cost if current cost efficiency continues

The figures above use rounded results. The SPI is approximately 0.96, while the CPI is approximately 1.09 when calculated from the stated inputs.

Interpretation of Project Performance

The negative schedule variance indicates that the project has completed less work than planned by the reporting date. An SPI of approximately 0.96 confirms that progress is behind the baseline, so the project manager should investigate delayed activities and determine whether additional resources, revised sequencing, or other recovery measures are appropriate.

The positive cost variance and CPI above 1 suggest that the completed work has cost less than its budgeted value. The projected final cost of approximately $230,000 assumes that current cost efficiency continues. It is an estimate, not a guarantee, and should be updated as new cost and performance information becomes available.

The project team should avoid accelerating work in ways that compromise software testing, data integrity, staff readiness, or patient safety. Schedule recovery should be based on documented dependencies, realistic resource availability, and verified quality requirements.

Evaluation of Additional Project Quality Tools

Pareto Chart

A Pareto chart ranks categories of defects or problems by frequency, usually from highest to lowest. It helps the team identify the categories contributing the largest share of reported issues and prioritize improvement efforts (ASQ, 2018).

One advantage is that it provides a clear visual comparison and helps focus limited resources on common problems. It can also help the team compare defect patterns before and after corrective action. However, the chart does not establish the root cause of a problem, and frequency alone does not measure severity. A rare but serious medication-related defect may require more urgent attention than a frequent minor formatting issue (Wilhite, 2017).

Histogram

A histogram displays the distribution of numerical data by grouping values into intervals and showing their frequencies. During the EMR project, histograms could help the team examine testing durations, response times, or the distribution of defect-resolution times (Schwalbe, 2016).

Histograms are useful for recognizing patterns, spread, and potential outliers in larger data sets. However, they may not show exact individual values, and comparing multiple groups can become difficult when the distributions are presented separately (Acampora, 2013).

Scatter Diagram

A scatter diagram plots paired numerical observations to explore whether two variables are associated. For example, the project team could examine whether longer training sessions are associated with fewer user errors during system testing (Schwalbe, 2016).

This tool helps identify positive, negative, nonlinear, or apparently absent relationships. However, a scatter diagram does not establish causation, and the visual pattern alone may not quantify the strength or statistical significance of an association.

Flowchart

A flowchart illustrates the steps and decision points in a process. For PCHO, it could document patient registration, appointment scheduling, medication ordering, laboratory processing, or the escalation of system issues during implementation.

Flowcharts help stakeholders understand workflows, identify unnecessary steps, and communicate process changes. Their limitations include the need for updates when procedures change and the possibility that complex processes may become difficult to represent clearly (Westland, 2018).

Project Lessons Learned and Reflection

Lessons Learned

The original project planning experience highlighted several areas that require improvement in future implementations.

Vendor selection: The initial six-month period was considered insufficient for fully evaluating vendor capabilities. An additional two months could provide more time for demonstrations, reference checks, security assessments, cost comparisons, and physician feedback. The schedule should account for this evaluation period before vendor commitments are made.

Budget planning: The original $250,000 budget was considered inadequate, and an additional $50,000 was identified as potentially necessary. This finding highlights the importance of estimating data migration, integration, training, maintenance, contingency reserves, and other implementation expenses before finalizing the budget. Any increase must be supported by a revised business case and formal authorization.

Physician training: Training required more time than initially anticipated because physician participation was lower than expected. Future plans should include early engagement, flexible training sessions, role-specific instruction, and assessments of user readiness.

Communication planning: Missed stakeholder meetings contributed to scheduling challenges. A stronger communication plan should establish meeting expectations, identify decision-makers, distribute agendas and status reports, and provide alternative ways for busy clinicians to contribute feedback.

Professional Reflection

This project provides an opportunity to apply project management principles to a healthcare technology initiative involving budget control, scheduling, quality assurance, and stakeholder coordination. Earned Value Management offers a practical method for comparing completed work with planned progress and actual expenditures, while tools such as Gantt charts, control charts, and fishbone diagrams support scheduling and quality improvement.

The experience also highlights the importance of realistic planning, timely communication, and continuous risk assessment. Developing confidence with Gantt charts and other project management tools requires practice, and instructional videos and practical exercises can help strengthen these skills.

Overall, the lessons from the PCHO EMR project can inform future healthcare technology implementations by emphasizing clear scope definition, evidence-based decision-making, staff engagement, and quality safeguards throughout the project lifecycle.

Frequently Asked Questions

What is the main purpose of the PCHO EMR project?

The primary purpose is to replace manual patient recordkeeping with an electronic medical record system that supports all five PCHO locations. The system is intended to improve access to clinical information, streamline workflows, strengthen coordination, and support patient safety.

What is the approved budget for the EMR implementation?

The original project budget is $250,000. Any proposed increase must undergo formal review and receive the appropriate authorization before additional spending is committed.

What is Earned Value Management in project management?

Earned Value Management is a project monitoring method that compares the budgeted value of completed work with planned work and actual costs. Metrics such as schedule variance, cost variance, SPI, and CPI help project managers identify performance problems and forecast likely outcomes.

What does an SPI below 1 mean?

A Schedule Performance Index below 1 indicates that the project has completed less work than planned for the reporting period. The project manager should investigate the causes and determine whether corrective action is needed.

What does a CPI above 1 indicate?

A Cost Performance Index above 1 indicates that the budgeted value of completed work exceeds the actual cost incurred. It suggests favorable cost efficiency, although it does not automatically mean that the project is on schedule or meeting all quality requirements.

Which quality tools can support EMR implementation?

Useful tools include fishbone diagrams, control charts, Pareto charts, histograms, scatter diagrams, and flowcharts. Each serves a different purpose, from investigating root causes to monitoring variation, prioritizing defects, analyzing data distributions, exploring relationships, and documenting workflows.

Why is physician training important during EMR implementation?

Physician training helps users understand system functions, follow standardized workflows, document clinical information accurately, and use the new technology safely. Adequate training can reduce user errors, improve adoption, and support continuity of patient care.

How can PCHO reduce EMR implementation risks?

PCHO can reduce risks by conducting thorough vendor assessments, maintaining a realistic budget and schedule, protecting patient information, testing interfaces and data migration, training staff, communicating regularly with stakeholders, and using formal change control procedures.

References

Acampora, J. (2013, May 20). Comparative distribution chart: Histogram or box plot alternative. Excel Campus. https://www.excelcampus.com/charts/comparativedistribution-chart-histogram-box-plot-alternative/

American Society for Quality. (2018). Control chart. https://asq.org/quality-resources/control-chart

American Society for Quality. (2018). Pareto chart. https://asq.org/quality-resources/pareto

American Society for Quality. (2018). Scatter diagram. https://asq.org/quality-resources/scatter-diagram

Athenahealth, Inc. (2018). Electronic health records and healthcare technology resources. https://www.athenahealth.com/

Biafore, B. (2007). Microsoft Project 2007: The missing manual. O’Reilly Media.

Deshpande, R. (2014). Earned value management: Concepts and applications. Project management reference cited in the original project plan.

PM FPX 4030 Assessment 1 Project Management Plan

O’Reilly. (2017, May 11). Earned value management and project performance. O’Reilly Media. https://www.oreilly.com/

Project-Management.com. (2018, January 25). Project schedule management and change control. https://project-management.com/

Schwalbe, K. (2016). Information technology project management (8th ed.). Cengage Learning.

Usmani, F. (2014). What is a scatter diagram? PM Study Circle. https://pmstudycircle.com/what-is-a-scatter-diagram-correlation-chart/

Wilhite, T. (2017, September 26). The disadvantages of Pareto analysis. Bizfluent. https://bizfluent.com/list-6831238-disadvantages-pareto-analysis.html

Westland, J. (2018, February 15). Sample project management flow chart. ProjectManager. https://www.projectmanager.com/blog/sample-project-management-flow-chart