You are on page 1of 4

Project Charter

[Insert Project Name]

Type the author name Last Updated: October 16, 2012

Project Charter [Insert Project Name]

Introduction
Provide a paragraph or two describing the project and a bit of background information, if relevant. [Insert Introduction]

Objectives
Provide high level goal(s) of the project with resulting final deliverable(s) and/or outcome(s) [Insert Objectives]

Scope
Provide a high level description of the projects scope. This should include what is within scope, and what is not in scope. For larger projects, this description is high level and there should be a reference to a more detailed scope description in the Project Management Plan. [Insert Scope]

Constraints, Assumptions and Risks


Provide a list of any project constraints, assumptions and risks that are known at the current time. For larger projects, this list can be expanded upon in the Project Management Plan, if required. A reference to this document should be included. If a Project Management Plan is not created for this project, a risk statement and an indication of how risks will be managed should be included here. This section should also refer to where the Risk Register is found. [Insert Constraints, Assumptions and Risks]

Dependencies
Provide a list of any project dependencies that are known at the current time. For larger projects, this can be expanded upon in the Project Management Plan, if required. A reference to this document should be included. [Insert Dependencies]

Page | 1

[Insert full path and file name]

Project Charter [Insert Project Name]

Budget
Provide an estimation of all project costs that are known at the current time. For larger projects, this can be expanded in a Budget/Financial Plan for the project, if required. A reference to this document should be included. [Insert Budget]

Timeline
Provide an estimated project timeline, including milestones. For larger projects, this can be expanded in the Project Management Plan, if required. A reference to this document should be included, as well as references to project schedules and critical path documentation. [Insert Timeline]

Strategy
The strategy is also sometimes referred to the Approach or Outline of Work. For larger projects, this will be high level in the charter with a reference to where further information will be documented (typically in a Project Management Plan). This strategy usually contains high level project governance information. This is also where you may outline any phases the project may be broken into, the use of pilots or focus groups, etc. [Insert Strategy]

Resource Roles and Responsibilities


Include a description of the roles required for the project and what those roles will be responsible for. With larger projects, this may be high level and expanded upon further within a Project Management Plan. If resource names are known, they can be listed under the required role. If time estimates are known for each role, it can be listed within the charter or a statement indicating where time estimates will be recorded could be used instead. If backfilling of their functional roles is required for the project, this should be noted in this section as well. [Insert Roles and Responsibilities]

Approval
This charter formally authorizes [PROJECT XXX], based on the information outlined in this charter. Should any of this information change throughout the duration of the project, it shall be discussed by Page | 2 [Insert full path and file name]

Project Charter [Insert Project Name]

[insert statement according to projects governance on where changes are discussed] and documented under [insert statement where projects documented changes are recorded]. Approved by: [insert who has approved the charter] Approval Date: [insert date the charter is approved] This approval was discussed by [insert where this approval was discussed] and documented at [insert where documentation for approval resides].

Revision History
Provide a chart where document revisions are recorded. This chart should include who made the revision, the date made, what was revised, who it was reviewed & approved by, and the date it was reviewed & approved. [Insert Revision History chart]

Page | 3

[Insert full path and file name]