<Insert Project Name>

Project Charter
Project Manager:
Program Name:
Executive Program Sponsor:
Author:
Creation Date:
Last Updated:
Version:

Revision History
<REVISION HISTORY SECTION IS REQUIRED AND MUST BE KEPT UP TO DATE. VERSION NUMBERS IN TABLE
BELOW, MUST MATCH VERSION FIELD ABOVE AND VERSION NUMBER IN FILE NAME. WHEN FINAL VERSION IS
APPROVED VIA PGR PROCESS, THE TABLE BELOW MUST INDICATE THE VERSION THAT WAS APPROVED AT
PGR>
Date

Version #

Description of Changes Made

Author

Approved By

TABLE OF CONTENTS
1

PROJECT DESCRIPTION...........................................................................................3
1.1
1.2

GOALS OF PROJECT........................................................................................................................ 3
BENEFITS........................................................................................................................................ 3

SCOPE, PHASES, RISKS, DEPENDENCIES AND ESTIMATES..............................4

2.1
2.2
2.3
2.4
2.5
2.6
2.7

SCOPE............................................................................................................................................ 4
DELIVERABLES................................................................................................................................ 5
KEY STAKEHOLDERS........................................................................................................................ 5
INTERNAL AND EXTERNAL RESOURCES/DEPENDENCIES.....................................................................6
ASSUMPTIONS / CONSTRAINTS......................................................................................................... 7
RISKS............................................................................................................................................. 7
LEVEL 0 ESTIMATE RESPONSE (IF APPLICABLE).................................................................................7

<ALL BLUE ITALICIZED TEXT INCLUDED IN THE DOCUMENT IS INSTRUCTIONAL ONLY. UPON COMPLETION OF THE
DOCUMENT ALL BLUE ITALICIZED TEXT SHOULD BE REMOVED .>

1 PROJECT DESCRIPTION
Project Name:
Project ID (if applicable):
Provide a simple, broad statement of what is to be accomplished by the project.
Project Objective:
Project Manager:

1.1

Estimated Start Date:

Estimated Delivery Date:

Goals of Project

Goals
Describe the overall goals of the project, by listing specific, actionable results that support the objective.

Measures of Success
List the objective, quantifiable metrics by which the successful accomplishment of each goal will be measured. If
quantifiable metrics cannot be established, list observable actions or outcomes that will demonstrate the
accomplishment of each goal.

1.2

Benefits

IF DONE Benefit to
Business / Customers

Provide a general, high-level description of the benefits that the business or

customers will realize. Identify which departments will realize benefits.

IF NOT DONE - Impact to

Business / Customers

Describe the impact to the business or customers if this project is not

completed. List the risks and costs incurred, and identify affected departments.

2 SCOPE, PHASES, RISKS, DEPENDENCIES AND ESTIMATES

2.1

Scope

Depending on the project size, details on additional scope types may be required. .
Scope of the Project
Define the boundaries which determine the scope and context of this project. Boundaries may be in product,
information, location, activity, business capability, technology, or organization.

Processes Impacted
List the business processes that will be directly or indirectly affected by this project. Briefly describe what the effect
will be.

Products and Services

List the products and services which are inputs and required in order to successfully complete the project. Briefly
describe the relationships between this project and the products and services listed.

End Users Impacted

List the users, by role or department, affected by a change in their interaction with the product, service, or system in
scope for this project. Briefly describe the nature of the change for each user role or department.

Out of Scope for the Project

Identify the products, information, locations, activities, business capabilities, technologies, or organizations which
are not in scope for this project, but which might otherwise be inferred to be in scope if not explicitly listed here.

2.2

Deliverables

List key deliverables in this project, by which progress toward on-time completion will be measured. Include the
Planning/Design Review, Deliverable Completeness Review, and Pre-Execution Review phases.
Phase / Deliverables
Target
Comments
Date

2.3

Key Stakeholders

List affected organizations, people, or external agencies. Stakeholders may include owners or sponsors of
dependent efforts as well as users.
Program Stakeholders
Executive Sponsor:

<name and title>

Team Leader:
Project Lead:
Project Managers:

<name and title>

<name and title>
<name and title>

Team Stakeholders

Enterprise Program Management Office Stakeholders

Enterprise Program
Leader:
Enterprise Program
Manager:
Enterprise Program
Liaison:

<name and title>

<name and title>
<name and title>

2.4

Internal and External Resources/Dependencies

Project Resource Estimate

Identify the roles required to support the project, possible individuals to be assigned and their responsibilities.
Include deliverables on which the project goals or measures of success depend.
LOB/Dept.

Resource
Notes:

Resource Name

Responsibilities

Internal/External Dependency
Deliverable

2.5

Assumptions / Constraints

List assumptions and critical success factors on which this project is based. Include assumptions that are the basis
of project goals or measures of success.
Assumptions 1.
and Critical
Success
Factors
1.

Management
and
Organizational
Constraints

2.6

Risks

List the risks for the project. Dependencies and Assumptions may have associated risks that should be included
here. Risk Category is classified as Business, Financial, Legal/Compliance, Operational Support, Scope,
Quality / Usability, Resource Commitment, Schedule/Plan Progress, Supplier/Vendor Management, Technical, or
Other.
Risk
Cause
Effect
Impact
Probability
Mitigation
Category
(As a result
(risk event may
(High,
(High,
Strategy
of)
occur)
Medium,
Medium,
Low)
Low)

2.7

Level 0 Estimate Response (if applicable)

Project Cost Estimate

Cost Category
Internal Labor
Cost:
Internal IT Cost
(Towards SLA)
Other SLA Costs
External (Hard $)
Costs Specify
______________
External (Hard $)
Costs Specify
______________
TOTAL
Notes on Cost
Estimates:

Most Likely Estimate

Cost Estimate Range (-25% to +75%)