EPLC_Project_Charter_v . .doc

<Project Name> Project Charter

Version: <1.0> Error! Unknown document property name.

Food and Drug Administration

<Project Name and Version number #> Enterprise Performance Life Cycle project charter

Document Version: <1.0> Document Version Date:<mm/dd/yyyy> Notes to the Author

[This document is a template of a Project Charter document for a project. The template includes instructions to the author, boilerplate text, and fields that should be replaced with the values specific to the project.

· Blue italicized text enclosed in square brackets ([text]) provides instructions to the document author, or describes the intent, assumptions and context for content included in this document.

· Blue italicized text enclosed in angle brackets (<text>) indicates a field that should be replaced with information specific to a particular project.

· Text and tables in black are provided as boilerplate examples of wording and formats that may be used or modified as appropriate to a specific project. These are offered only as suggestions to assist in developing project documents; they are not mandatory formats.

When using this template for your project document, it is recommended that you follow these steps:

1. Replace all text enclosed in angle brackets (i.e., <Project Name>) with the correct field values. These angle brackets appear in both the body of the document and in headers and footers. To customize fields in Microsoft Word (which display a gray background when selected):

a. Select File>Properties>Summary and fill in the Title field with the Document Name and the Subject field with the Project Name.

b. Select File>Properties>Custom and fill in the Last Modified, Status, and Version fields with the appropriate information for this document.

c. After you click OK to close the dialog box, update the fields throughout the document with these values by selecting Edit>Select All (or Ctrl-A) and pressing F9. Or you can update an individual field by clicking on it and pressing F9. This must be done separately for Headers and Footers.

2. Modify boilerplate text as appropriate to the specific project.

3. To add any new sections to the document, ensure that the appropriate header and body text styles are maintained. Styles used for the Section Headings are Heading 1, Heading 2 and Heading 3. Style used for boilerplate text is Body Text.

4. To update the Table of Contents, right-click and select “Update field” and choose the option- “Update entire table”

5. Before submission of the first draft of this document, delete this “Notes to the Author” page and all instructions to the author, which appear throughout the document as blue italicized text enclosed in square brackets.]

VERSION HISTORY

[Provide information on how the development and distribution of the Project Charter up to the final point of approval was controlled and tracked. Use the table below to provide the version number, the author implementing the version, the date of the version, the name of the person approving the version, the date that particular version was approved, and a brief description of the reason for creating the revised version.]

By Revision

Date Approved

By Approval

Date Description and Reason for Change

Table of Contents 51.0

INTRODUCTION

51.1

PURPOSE OF PROJECT CHARTER

52.0

PROJECT AND PRODUCT OVERVIEW

53.0

JUSTIFICATION

53.1

BUSINESS NEED

53.2

BUSINESS IMPACT

53.3

STRATEGIC ALIGNMENT

64.0

SCOPE

64.1

OBJECTIVES

64.2

HIGH-LEVEL REQUIREMENTS

64.3

EXPECTED OUTCOME

64.4

BOUNDARIES

75.0

PROJECT ORGANIZATION

75.1

ROLES AND RESPONSIBILITIES

95.2 Stakeholders (Internal and External)

96.0 Duration

96.1 Timeline

96.2 Milestones

97.0 budget Estimate

97.1 Funding Source

107.2

ESTIMATE

118.0 Assumptions, Constraints And Risks

118.1 Assumptions

118.2 Constraints

118.3 Risks

129.0 project Charter approval

13APPENDIX A: REFERENCES

14APPENDIX B: KEY TERMS

1.0 INTRODUCTION

1.1 PURPOSE OF PROJECT CHARTER

The <Project Name> project charter formally authorizes a project, describes the business need for the project and the product to be created by the project. It provides the project manager with the authority to apply up to a certain level of organizational resources to project activities. It is created during the Concept Development Phase of the project.

The intended audience of the <Project Name> project charter is the Business Sponsor and Critical Partners.

2.0 PROJECT AND PRODUCT OVERVIEW

[Typically, the description should answer who, what, when and where, in a concise manner. It should also state the estimated project duration (e.g., 18 months) and the estimated project budget (e.g., $1.5M).]

3.0 JUSTIFICATION

3.1 BUSINESS NEED

[This section of the Project Charter explains why the customers need this project to be completed. It identifies the customers who are to receive and benefit from the product(s) to be developed under this project. It identifies the need, the problem to be solved and/or the opportunity to exploit.]

3.2 BUSINESS IMPACT

[In this section you should list the benefits the business and/or customers will receive as a result of this project. Describe the observable and measurable outcomes that will result directly from the project’s performance. Please note that performance measures will be crafted in future deliverables related to these targeted outcomes.]

3.3 STRATEGIC ALIGNMENT

Scale: H – High, M- Medium, L – Low, N/A – Not Applicable

Organization Strategic Goals:

[Enter Program or division goals]

OPDIV/STAFFDIV Strategic Goals:

[Enter OPDIV/STAFFDIV goals]

Department of Health and Human Services (DHHS) Strategic Goals:

[Enter Health and Human Services Goals]

DHHS IT Goals:

[Enter Health and Human Services IRM Goals]

President’s Management Agenda (PMA) Strategic Goals:

[Enter PMA Strategic Goals]

4.0 SCOPE

4.1 OBJECTIVES

The objectives of the <Project Name> are as follows:

· [Insert Objective 1]

· [Insert Objective 2]

· [Add additional bullets as necessary]

4.2 HIGH-LEVEL REQUIREMENTS

The following table presents the requirements that the project’s product, service or result must meet in order for the project objectives to be satisfied.

4.3 EXPECTED OUTCOME

The following table presents the expected outcomes that the project’s product, service or result must meet in order for the project objectives to be satisfied.

4.4 BOUNDARIES

[Describe the inclusive and exclusive boundaries of the project. Specifically address items that are out of scope.]

5.0 PROJECT ORGANIZATION

5.1 ROLES AND RESPONSIBILITIES

[Depending on your project organization, you may modify the roles and responsibilities listed in the table below.]

This section describes the key roles supporting the project.

<Name>

<Org>

<Name>

<Org>

<Name>

<Org>

<Name>

<Org>

<Name>

<Org>

<Name>

<Org>

<Name>

<Org>

<Name>

<Org>

<Name>

<Org>

<Name>

<Org>

<Name>

<Org>

<Name>

<Org>

<Name>

<Org>

<Name>

<Org>

5.2 Stakeholders (Internal and External)

[A stakeholder is a person or organization that is actively involved in the project, or whose interests may be positively or negatively affected by execution or completion of the project. A stakeholder may also exert influence over the project and its deliverables.]

6.0 Duration

6.1 Timeline

[An example of a high-level timeline is provided below.]

6.2 Milestones

[Example: For projects associated with a major/tactical investment as defined by FDA OCIO]

The table below lists the high-level Executive Milestones of the project and their estimated completion timeframe.

[Add additional rows as necessary]

7.0 budget Estimate

7.1 Funding Source

[Example: grant, terrorism budget, or operational budget.]

7.2 ESTIMATE

This section provides a summary of estimated spending to meet the objectives of the <Project Name> project as described in this project charter. This summary of spending is preliminary, and should reflect costs for the entire investment lifecycle. It is intended to present probable funding requirements and to assist in obtaining budgeting support.

[For projects associated with a major/tactical investment as defined by FDA OCIO there should be a line of sight between the budget presented here and the investment’s Exhibit 300. Double click on the Microsoft Excel Object table below to input values.]

* PY = Past Year, CY = Current Year, BY = Budget Year

8.0 Assumptions, Constraints And Risks

8.1 Assumptions

This section identifies the statements believed to be true and from which a conclusion was drawn to define this project charter.

· [Insert description of the first assumption.]

· [Insert description of the second assumption.

· [Add additional bullets as necessary]

8.2 Constraints

This section identifies any limitation that must be taken into consideration prior to the initiation of the project.

· [Insert description of the first constraint.]

· [Insert description of the second constraint.]

· [Add additional bullets as necessary]

8.3 Risks

[List the risks that the Business Sponsor should be aware of before making a decision on funding the project, including risks of not funding the project.]

The table below presents the known risk which could have a major impact on the outcome of the project and associated mitigation strategy that the business sponsor/project team will take to manage them.

9.0 project Charter approval

The undersigned acknowledge they have reviewed the project charter and authorize and fund the <Project Name> project. The undersigned herby give the project manager the authority to apply the approved level of organizational resources to project activities. Changes to this project charter will be coordinated with and approved by the undersigned or their designated representatives.

Signature:

Date:

Print Name:

Title:

Signature:

Date:

Print Name:

Title:

APPENDIX A: REFERENCES

[Insert the name, version number, description, and physical location of any documents referenced in this document. Add rows to the table as necessary.]

The following table summarizes the documents referenced in this document.

APPENDIX B: KEY TERMS

[Insert terms and definitions used in this document. Add rows to the table as necessary. Follow the link below to for definitions of project management terms and acronyms used in this and other documents.]

The following table provides definitions for terms relevant to this document.

Requirements Analysis

Developed Prototype

Completed

System Development

05/06

02/06

12/05

10/05

Completed

Project Plan Completed

� EMBED Excel.Sheet.8 ���

Template Version 2.1 (Last Modified on Aug. 7, 2009)

PAGE

Revision Date: Error! Unknown document property name.

N EPLC_Project_Charter_Template.doc

_1296907002.xls Sheet1

PY* CY BY BY+1 BY+2 BY+3 BY+4 & Beyond Total

Planning 0

Acquisition 0

Maintenance 0

Sub Total 0 0 0 0 0 0 0 0

# of Govt. FTE

Govt. FTE Costs 0

Total Costs 0 0 0 0 0 0 0 0