Professional Documents
Culture Documents
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>
1 PROJECT DESCRIPTION
Project Name:
Project ID (if
applicable):
Project Objective: Provide a simple, broad statement of what is to be accomplished by the project.
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 Provide a general, high-level description of the benefits that the business or
Business / Customers customers will realize. Identify which departments will realize benefits.
IF NOT DONE - Impact to Describe the impact to the business or customers if this project is not
Business / Customers 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.
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.
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.
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
Resource
Notes:
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)