Template - Charter EZ, V2.2

Template: Project Charter EZ
Change the template as appropriate for your project.
Project Name Project name

Project Manager Project manager name Organization Organization name
Sponsor Sponsor name Organization Organization name
Customer Customer name Organization Organization name
Document Version and Version number and date of this document.
Date
Project Scope
Business Need Provide a brief overview and background information about the project. Explain at a
high level what the project is to accomplish, who initiated the project and expected
benefits. Enter the information that will give a context to the project drawing on the
information in the Project Concept document as a source .
Project Goals Optional for EZ charter

Identify the key project goals. Any project goals identified in the Project Concept
document should serve as the basis for this section.
Product Description Describe the product or service that the project is to deliver.
In Scope/Out of The scope sets the boundaries of the project. Enter those key items that are a part of
Scope the project and those major items that will not be worked on as part of this project.
This is a high level description of what is in and what is out of the boundaries of the
project.
Critical Success Optional for EZ charter

Factors Identify the critical success factors for the project. Critical success factors are
outcomes that must be achieved in order for the project to be considered a success.
Project Assumptions Optional for EZ charter
List any assumptions made in defining the project. Assumptions can affect any area
of the project including scope, stakeholders, business objectives and functional
requirements.
Project Constraints Optional for EZ charter
Summarize the key constraints that will serve as limitations and boundaries for the
project team in their decision making.
Project Deliverables List the key deliverables of the project with a short description of each.
Template: Project Charter v2.2 Page 1 of 4

Requirements
Identify the functional requirements here. Functional requirements describe what characteristics the
proposed product or service must have and provides a list of the minimum features that must be in place
when the project is complete.
High-Level Milestones and Timeline
Milestones are deliverables or major events that may be readily identified as completed or not completed on
a specified date. Project Milestones are ‘how are we doing’ thresholds that indicate whether a project is on
track to finish as expected.
Enter the project’s key milestones with an estimated date for the completion of the milestone.
Enter the roles and project responsibility for each role required for the project. Enter the skills required of
the role. Enter the preliminary FTE estimates for resource commitment for the fiscal year. Enter a total of
the FTE for the fiscal year. Enter the planned or recommended source for acquiring the resource.
Example: Contractor or the name of the organization that might provide the resource.
High-Level Roles
Role Project Skills Required FTE Recommended
Responsibility FY yy-yy Source
Total
Enter the preliminary budget information needed to support the project. Include costs for labor, material
and other expense items. If the on-going maintenance and support costs are required by your project add
this information to the high-level budget. The preliminary budget can also be broken down by major
phases or key deliverables/milestones pf the project.
High-Level Budget
Cost Type FY yy-yy FY yy-yy Total
Total Budget
Communications Strategy
The communications strategy provides guidance in how to meet the ultimate end of project communication.
Develop a high-level statement of the general approach to communications for key items:
Project Communication Objectives

Key Communication Message
Key Audiences

Quality Management Strategy
The quality management strategy provides guidance in how to meet the quality objectives of the project.
Develop a high-level statement of the general approach to quality management issues for these key items:
Quality Objectives
Key Project Deliverables and Processes subject to quality review
Main Quality Standards to be used on the project
Issue Management Strategy

The purpose of issue management is to minimize the impact of unplanned for events during project
execution and control, and to ensure that issues that cannot be resolved by the project team are escalated
appropriately.
Option: describe at a high level any specific issue management goals for this project.
Identify the roles for assuring issue management objectives are met throughout the project life cycle.
Option: identify roles for developing the prioritization and escalation rules in the issue management planning
activity.
Change Management Strategy for Phase 3

The change management strategy is a high-level statement of the general approach to change management
issues for these key items:
 Anticipated change management challenges

 Key project constraints
 Key customer practices for managing change
 A concise statement of change management practices
Risk Management Strategy for Phase 3
Risk areas
Describe at a high level the most significant areas of risk for this project.
Critical stakeholder risk tolerances and thresholds

Include this block if the stakeholders have identified areas of risk where either risk cannot be tolerated at all
or for which the risk threshold is very low
Risk management objectives

Identify the project’s overall objectives for managing risk.
High-level risk management process

Identify at a high level the process to be followed for assuring risk management objectives are met
throughout the project life cycle.
Risk decision makers

Identify the roles for assuring risk management objectives are met throughout the project life cycle.

Project Charter Approval Signatures
Project Manager
___________________________________________________________ __________________________
(Signature) (Date)
Name
Position
Organization
Project Sponsor
___________________________________________________________ __________________________
(Signature) (Date)
Name
Position
Organization
Project Customer
___________________________________________________________ __________________________
(Signature) (Date)
Name
Position
Organization
Project Customer
___________________________________________________________ __________________________
(Signature) (Date)
Name
Position
Organization

Template - Charter EZ, V2.2

Uploaded by

Copyright:

Available Formats

Template - Charter EZ, V2.2

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Template - Charter EZ, V2.2

Uploaded by

Copyright:

Available Formats

Template: Project Charter EZ

Change the template as appropriate for your project.

Project Name Project name

Project Goals Optional for EZ charter

Critical Success Optional for EZ charter

Project Assumptions Optional for EZ charter

Project Constraints Optional for EZ charter

Template: Project Charter v2.2 Page 1 of 4

High-Level Milestones and Timeline

Project Communication Objectives

Template: Project Charter v2.2 Page 2 of 4

Issue Management Strategy

Change Management Strategy for Phase 3

 Anticipated change management challenges

Risk Management Strategy for Phase 3

Critical stakeholder risk tolerances and thresholds

Risk management objectives

High-level risk management process

Risk decision makers

Template: Project Charter v2.2 Page 3 of 4

Template: Project Charter v2.2 Page 4 of 4

You might also like