Project Charter

[Click here and type Project Name - Line of Business]

Management Sponsor: [Click here and type primary business

sponsor]

Project Manager: [Project Mgr.]

Date: [Click here and type date]

Version [Click here and type version, e.g. 1.0]

 [Click here and type Project Name - Line of Business]

Approvals
Executive Sponsor: Date:
[Click here and type name]

Primary Business Sponsor: Date:

[Click here and type name]

Project Manager: Date:

[Click here and type name]

IT Manager: Date:
[Click here and type name]

Operations Manager: Date:

[Click here and type name]

Finance: Date:
[Click here and type name]

Other technology: Date:

[Click here and type name]

[Click here and type Other Group as applicable - Delete if none]: Date:
[Click here and type name]

Comments:

Project Charter Page 2 of 9

 [Click here and type Project Name - Line of Business]

Revision History

Document/Dept. Owner: [Click here and type department owner name]

Created By: [Click here and type name] Date: [Insert date]

Revised By Date Revised New Version #

Project Charter Page 3 of 9

 [Click here and type Project Name - Line of Business]

Table of Contents

I. BACKGROUND INFORMATION........................................................................................................................5

II. MISSION STATEMENT.........................................................................................................................................5

III. BENEFITS, RISKS & ACTION ITEMS................................................................................................................5

IV. HIGH-LEVEL BUSINESS REQUIREMENTS.....................................................................................................5

V. KEY DEPENDENCIES............................................................................................................................................5

VI. WORKING ASSUMPTIONS..................................................................................................................................5

VII. PROJECT SCOPE....................................................................................................................................................6

VIII. DEPLOYMENT APPROACH................................................................................................................................6

IX. BUSINESS CASE......................................................................................................................................................6

X. PROJECT ORGANIZATION AND GOVERNANCE.........................................................................................6

XI. PROJECT ROLES AND RESPONSIBILITIES...................................................................................................8

XII. PROJECT CONTROL PROCEDURES/PLANS..................................................................................................8

XIII. ADDENDUMS...........................................................................................................................................................9
A. As Needed or Warranted..........................................................................................................................................9

Project Charter Page 4 of 9

 [Click here and type Project Name - Line of Business]

I. Background Information

[<<Click here and insert background information from the business case>>]

II. Mission Statement

[<<Click here and insert a mission statement/objective for the project>>]

III. Benefits, Risks & Action Items

Benefits:

 [<<Click here and insert benefits of the project>>]

Risks:

 [<<Click here and insert items that are potential risks to the project>>]

Action Items:

 [<<Click here and insert items requiring action/attention for the project>>]

IV. High-Level Business Requirements

 [<<Click here and type HIGH level requirements>>]

V. Key Dependencies

The ability of this project to successfully complete the defined mission statement is dependent upon the
following:

 Executive Sponsorship and related support

 Line of Business buy in
 Empowerment and support of project teams
 Dedicated Resources:
 [<<Click here and insert involved LOB's>>]
 Cross dependent resources are not adversely impacted
 Timely escalation and resolution of issues
 Approval of implementation costs and allocation
 Achievement of committed project dates
 [<<Click here and insert other dependencies as needed>>]

VI. Working Assumptions

This project is being initiated with the following assumptions in mind:

 [<<Click here and insert assumptions from the business case and elsewhere>>]

Project Charter Page 5 of 9

 [Click here and type Project Name - Line of Business]

VII. Project Scope

Phase Task Activities & Deliverables

Frame Idea Develop Project Request Investigate solutions

Access Concept Gain approval and structure project Planning Business Case, Project
Charter
Validate Scope [Insert major tasks] [Insert major activities/deliverables]
Design [Insert major tasks] [Insert major activities/deliverables]
Build Construction/Testing/Pilot [Insert major activities/deliverables]
Launch Deployment [Insert major activities/deliverables]
Maintain Ongoing Maintenance [Insert major activities/deliverables]

In Scope

 [<<Click here and insert items In Scope>>]

Out of Scope

 [<<Click here and insert items Out of Scope>>]

VIII. Deployment Approach

Timeline

[<<Click here and insert a statement on the projected completion date - if known>>]

Milestones

 [<<Click here and insert milestone dates - if known>>]

IX. Business Case

Refer to the Business Case document – file name “[Insert business case file name]” located on the main project
repository site.

Please note there is no business case for the project charter assignment. The Business case reference above is for
future use.

X. Project Organization and Governance

[Click Here and type a paragraph relating to the general scope of the project.]

Overall Governance Structure

Governance of this project is comprised of a Steering Committee and a Project Leadership Team. A Project
Support team (subject matter experts) consists of individuals with expert technical and/or business knowledge

Project Charter Page 6 of 9

 [Click here and type Project Name - Line of Business]

necessary for the successful completion of this project will support the Project Leadership Team. The specific
roles and responsibilities of the Steering Committee and the Project Leadership Team are described below.

Steering Committee

The Steering Committee is responsible for monitoring the project’s progress against plan, based on information
provided by the Primary Business Sponsor, Project Manager and the Leadership Project Team. The Steering
Committee is also responsible for setting and maintaining project scope, resolving project issues that require
Senior Management attention (including those of a cross-organizational nature), allocating resources (when
requested by the Primary Business Sponsor, Project Manager and/or the Leadership Project Team), establishing
and reaffirming priorities, and resolving inter-project issues and conflicts. Finally, the Steering Committee, either
directly or through the Project Manager, is responsible for communicating status of the Project to Executive
Management when requested or as deemed necessary.

Chairman: [Click Here and type Name, Full Title, and LOB.]

Members: [Click Here and type Name, Full Title, and LOB.]

Steering Committee meetings will be conducted monthly, and may schedule others as needed to address issues.
Minutes will be distributed to those attending, the Project Leadership and Support Teams.

Project Leadership Team

The Project Leadership Team is comprised of staff from the IT and business community, and will develop the
appropriate structure and approach to execute this project.

Telephone
Name Area Role E-mail Address
Number
[Type Name] [Type Area] [Type Function] [Type Phone] [Type Name]

Weekly Project Leadership Team meetings will be held and minutes are maintained. The Project Leadership
Team can elect to bring relevant Support Team Members as necessary.

Support Team

In addition to the Project Leadership Team, the project will also be staffed with a Support Team of technical
experts, business experts, business partners, legal, audit, etc., who will be involved as appropriate.

Support Team members will attend Project Leadership Meeting as invited.

Meeting Times and Frequency:

Steering Committee: Monthly – [Indicate day and week of meeting, TBD if unknown]

Project Team: Weekly – [Type Day of week and time - TBD if unknown]
Sub-project team meetings to be held as needed.
Meeting minutes to be distributed to Project Team members

Project Charter Page 7 of 9

 [Click here and type Project Name - Line of Business]

XI. Project Roles and Responsibilities

 [Type Name of the Program Manager], Primary Business Sponsor. Role: Provide leadership and
establish tactical direction for the project team within the context of the business unit. The Primary
Business Sponsor is ultimately accountable to oversee the following: coordination and alignment of the
project team; acquisition of user participation and resources; determination of overall project scope;
coordination of status and related issues with Executive Sponsor; and achievement of end goals and target
date.

 [Type Name of the Project Manager], Project Manager. Role: The Project Manager is ultimately
accountable for the timely and accurate completion of deliverables and the successful achievement of
project goals at each phase in this role. The Project Manager will work in close coordination with the
Primary Business Sponsor and respond to their directives. This includes, but is not limited to: training
and communications, mock support, conversion tasks, and day 2 support.

 [Type Name of the IT Manager], IT Manager. Role: Responsible for all technology deliverables, as well
as ensuring that all technology and development requirements are identified and that related costs, and
benefits, are assessed accurately and completely. This includes related support groups (IT, I&A, I&O,
Vendor), error resolution, day 2 support, communications with downstream users groups, IT training
support and mock support.

 [Type Name of the Business Analyst], Business Analyst. Role: Responsible for…..

 [Type Name, role and high level responsibilities for others as known/defined]

XII. Project Control Procedures/Plans

 Change Control Procedures

The project is following the established [Primary Business] change control process. For detailed
information, use this web address: [ ]

 Communications Procedures
The [Primary Business PMO] will house all project information including milestones, issues, meeting
minutes, project documentation, etc. Project status information is rolled up into the monthly [Primary
Business] status report for executive management review.

 Escalation Procedures
The status of the project is determined by three categories, Green, Yellow and Red, which are further
explained below:

o Green: No major issues, the program/project is on schedule

o Yellow: Issues exist, options are available, workarounds are in place; the schedule could be impacted
if the issues are not resolved in a timely manner

o Red: Major issues exist; cannot proceed to the next phase, or cannot complete a major milestone until
the issue is resolved; impacts to quality, cost and the schedule could result if the issue is not resolved
in a timely manner

Project Charter Page 8 of 9

 [Click here and type Project Name - Line of Business]

At any time during the life cycle of a project that the status is downgraded to Yellow or Red, the
Executive Sponsor and the Steering Committee will be notified. Below, the process for resolving and
monitoring Yellow and Red issues has been provided:

o Yellow and red issues will be documented in weekly status reports and discussed at the bi-weekly
meeting held with Project Team, the businesses, and IT partners.

o Red issues are communicated to the appropriate personnel for resolution and monitored accordingly.

 Issue Monitoring
The [Primary Business PMO] is being used to monitor and resolve project issues.

 Procurement Plan
The project will utilize the standard [organization] procurement process.

 Project Completion Procedures

The project plan includes information on tasks, start and end dates, % complete and assigned resources.
Milestones are tracked in the [Primary Business PMO].

 Quality Assurance Procedures

The project team will develop and utilize a test plan to ensure compliance to requirements. There are
three stages of testing planned: system, unit and user acceptance. Other quality assurance procedures
include the [Primary Business] change control process, user-training plan, and the change implementation
process guidelines.

 Review/Approval Procedures
The project is using the Delivery Process for project management discipline. Approvals will follow the
current processes in place within the [Primary Business] and the [organization].

 Risk Management Procedures/Contingency Plan

Contingency plans will be developed throughout the planning phase of the project, and further evaluated
when Yellow or Red issues are identified. These plans will be reviewed and agreed upon by the Project
Lead, [Primary Business] Sponsor, and Executive Sponsor. Other Project Team, Support Team and/or
Steering Committee Members may be solicited for advice and/or contingency plan resolution based on
the severity of the issue.

XIII. Addendums

A. As Needed or Warranted

Project Charter Page 9 of 9