compare two project

Bluer-Aya
ProjectConceptDocument-template.docx

Project Concept Document 9/9

Project Concept Document (PCD)

<Project Title>

Contents

1 Purpose of Project Concept Document (PCD) 3

2 Document and Concept Summary 3

3 Project Concept Statement 4

4 Project Sponsorship, Team and Key Stakeholders Analysis 4

5 Project Value Measurement Framework 5

6 Project Description 7

Project Purpose, High-Level Scope, Time Estimate and Costs 7

Background and Circumstances 7

Estimated Business Benefits 7

Proposed Solution(s) Approach 7

7 Estimated Resource Requirements 7

8 Potential Project Risks / Constraints 8

9 Project Sponsor’s (Governance) Authorization to Proceed 9

Purpose of Project Concept Document (PCD)

The PCD document serves several purposes:

· Project initiation document – provides initial assessment for project governance decision to Approve/Reject/Put-on-Hold proposed project,

· Clearly states the business problem that needs to be solved,

· Defines the projects strategic objectives

· Suggests an initial approach to solve the business problem,

· Defines high-level project success criterion of Customers / Sponsor,

· Communicates the perceived priority and strategic alignment of the project to Lahey Health Governance.

· Serves as sponsor’s and PPM Governance authorization to proceed (Decision Gate #1) to project Concept and Definition phases.

Document and Concept Summary

Functional Area Priority Score

# (x) Project For FY13/14, Score ____ Priority : H - M - L

Date Submitted

dd/mmm/yyyy

Project/Program Name

Project Sponsor(s)

Business Case Author(s)

Department/Business Unit

Project Portfolio Category

Estimated Project Size

S – M – L

Date Governance Approved/Rejected/On-Hold

Project Concept Statement

What are the overall Lahey Health objectives that this project will satisfy?

Example:

To be the healthcare industry leader in our ability to provide real-time billing information to our patients.”

Note: The concept statement is more strategic in nature than a POS (Project Objective Statement), which specifically addresses project scope, schedule and resource goals. The POS is typically created in the PDW (Project Initiation/Definition Workshops).

Project Sponsorship, Team and Key Stakeholders Analysis

Name

Project Role

Contact Information

Impacted How?

Business Line Executive Project Sponsor (VP and above)

Proposed Business Lead

Proposed Project Manager/Lead

Proposed Technical Manager/Lead

Key Project Stakeholders (Physicians, Clinics, Facilities)

Clinical/Business/IT/SMEs, Etc.

[Identify the Project Sponsor, proposed team members, and key stakeholders. Identify their project role, how they will be impacted by the project and contact information.]

Project Value Measurement Framework

The goal of all Lahey Health projects is to provide value to our established strategic goals. Please fill out the following value measurement matrix. 1. Provide a self-reported ranking for each strategic goal category using the scoring rubric for each category, 2. Provide a brief explanation or reference for your self-reported score. Note: The final score will assist project governance to determine relative ranking for each project.

Proposed Project Value Scoring Criterion & Ranking

Scoring Guidelines:

Yes

No

Regulatory / Compliance

Is the project “Mandated” by a regulatory body?

Justification: [Please provide reference or justification for this decision]

Scoring Guidelines:

Requestor Rank 0-5

Governance Weighting (%)

Category Score

Patient Safety / Assessed Risk to Lahey Health

Will the project improve the quality of care for our patients and improve patient satisfaction?

5 = Yes, significantly improves patient safety or reduces risk to Lahey Health (quantifiable evidence exists)

3 = Yes, medium impact (some quantifiable improvement)

1 = Yes, minor impact (hard to quantify)

0 = No impact

Justification: [Please provide reference or justification for this ranking]

Superior Patient Experience / Satisfaction

Does this project improve our patients’ care experience at Lahey Health?

5 = Yes, significantly improves care experience (quantifiable evidence exists)

3 = Yes, medium impact (some quantifiable improvement)

1 = Yes, minor impact (hard to quantify)

0 = No impact

Justification: [Please provide reference or justification for this ranking]

Margin Enhancement / Operational Efficiency / Cost Effectiveness

Will the project reduce expenses or enhance revenue and improve efficiency for how we care for our patients?

5 = Yes, significantly improves operational efficiency

(quantifiable evidence exists)

3 = Yes, medium impact (some quantifiable improvement)

1 = Yes, minor impact (hard to quantify)

0 = No impact

Justification: [Please provide reference or justification for this ranking]

Lahey Health “System-wide Integration”

Will the project help grow our business or create new facilities and / or services?)

5 = Yes, significantly facilitates system wide integration (quantifiable evidence exists)

3 = Yes, medium impact (some quantifiable improvement)

1 = Yes, minor impact (hard to quantify)

0 = No impact

Justification: [Please provide reference or justification for this ranking]

Lahey Health System Strategic Growth

Will the project support the strategic goals of Lahey Health?

5 = Yes, significantly improves strategic growth (quantifiable evidence exists)

3 = Yes, medium impact (some quantifiable improvement)

1 = Yes, minor impact (hard to quantify)

0 = No impact

Justification: [Please provide reference or justification for this ranking]

Project Description

Project Purpose, High-Level Scope, Time Estimate and Costs

Provide a high-level summary of business/clinical problem being solved or opportunity begin pursued by this project.

Briefly describe the proposed project/initiative and its purpose.

Provide a high level overview of expected project deliverables (Scope),estimated or desired delivery time-frames (e.g. 2-4 months) and high-level cost estimates [Note: These are only high-level – the detailed scope, schedule and cost will be developed in the Project Definition Phase.]

Background and Circumstances

Provide a description of the environment and/or circumstances that have given rise to the project. Examples may include issues of quality, efficiency, cost, customer service, competition, business integration, regulatory requirement etc. What has given rise or triggered the need for this project?

Estimated Business Benefits

Summary of expected business benefits for Lahey Health to do this project.

Think in terms of meeting the customers’ [clinicians’ or patients’] needs, generating new revenues, increasing operational efficiencies, reducing manpower, etc. Estimated business benefits will form the basis for identifying critical success factors for the project.

Proposed Solution(s) Approach

Provide high-level alternative solutions or options for project evaluation, including, if available, a preferred choice with reasons. [E.g. - Could be in-house (organic) application development, purchase of 3rd party application to implement, 3rd part vendor, upgrade/enhancement to existing operational system, in-house team analysis to provide recommendations to Lahey’s senior management/Governance for approval.]

Estimated Resource Requirements

Please identify estimated resources (First by area, then by roles (if known) – not specific names at this point) required to help complete the assessment or Project Concept Document (PCD) and later help define and execute the project.

Note: One individual may represent multiple areas and play multiple roles. Be sure to include any external resources that you may need.

IT /IS Functional Areas:

Ambulatory (AllScripts)

Reporting

Interfaces

Legacy Apps

Database

Mgt

ECMS

IT Infrastructure

Web Svcs /

PeopleSoft

Telecomm.

Role

Role

Role

Role

Role

Role

Role

Role

FTE(s)

FTE(s)

FTE(s)

FTE(s)

FTE(s)

FTE(s)

FTE(s)

FTE(s)

IT PMO

IT Desktop

Other

Role

Role

Role

FTE(s)

FTE(s)

FTE(s)

List of IT /IS Roles:

App. Analyst

App. Designer

App. Developer

App. Tester

Business Analyst

IT Business Sponsor

Syst. Admin.

Technical Lead

Infrastructure Lead

System Architect

IT Project Manager

Database Admin.

Potential Project Risks / Constraints

List potential ‘known’ risks to the project at this time. Provide risk category, estimate probability of occurrence, impact to project and risk priority. Strive to assess any risk mitigation strategies. Reminder: Risks will evolve over the project’s life-cycle. See example below.

Risk Name

Risk Category

Probability of Occurrence

Potential Impact

Risk Priority

Potential Responses

Can’t meet mandatory compliance date (end of year)

Industry Compliance

Medium (3)

High (5)

High (15) - #1 Risk

Have dedicated resources prioritized to this project to ensure we meet mandatory dates for compliance.

Project Sponsor’s (Governance) Authorization to Proceed

<Name>, Project Sponsor, with guidance from project governance, authorizes the following actions to further address the business needs stated in this Project Concept Document [Examples]:

1. Project is Approved/Rejected/On-Hold

2. Perform a Project Definition Workshop (PDW) to define project requirements.

3. Form evaluation team to consider alternatives and report progress to Governance.

4. Project authorized to proceed to project definition with XX resources and IT priority YY.

5.

6.

AGREED:

Date: __________________

Executive Sponsor: PM: ____________________________

Name: Name:

Title: Title:

PMO Review:

Director, PMO: ____________________________

Name: _______________

Date Reviewed: ___________________________

lc_1c+k