HLST 4900

PROJECT CHARTER TEMPLATE

Why develop a Project Charter?

The project charter assists in a number of ways:

1. The project charter ensures that the client and project team are on
the same page as to what the project is to accomplish.
In engaging a new project with new clients and project teams there is
considerable opportunity to make incorrect/invalid assumptions about what the
project entails and how it will be done. Even within the team; culture, education,
technical language, work experience, etc. can all lead to different interpretations
of what is to done and how it will be done. Similarly the client makes
assumptions based on their ‘world’ about skills, needs, approach and other
variables that can lead to future problems.

2. The project charter makes it clear to the team and to the client who is
going to do what, when and how.
A common issue faced within projects is that the team members or the client
assume that certain information, access to people/expertise, external variables
are ‘magically’ going to be there when needed. The charter lays out what is
needed and expected throughout the phases of the project and addresses the
risk of that not happening.

3. The project charter provides a touchstone and milestones of

timelines and responsibilities.
One way to do this is a roles and responsibilities chart that lays out each team
member’s and the client’s responsibilities. This avoids both confusion and finger
pointing.

4. Laying out the project charter helps identify methodological issues

that can be discussed by the team and with the client before time,
effort or resources are wasted.

What is included in a Project Charter?

Project Purpose:
This section provides a brief overview of the project. What is the opportunity or
problem that is being addressed? What are the client/project needs that will be met
by the project? This section should provide some background and rationale for the
undertaking.

Project Sponsor:
Who is the client for the project? What are the approval/reporting expectations
for the project? What must the client bring to the project for success?

1
Project Team:
Who are the members of the project team and what are their key skills and
experience?

Project Goals and Objectives:

What are the project goals to be achieved?

Project Scope:
The scope defines the project’s limits and identifies the products to be delivered
by the project. The scope establishes the boundaries and will be useful in measuring
progress and success.

Assumptions:
What are the assumptions being made about the project? For example,
timelines, resources (your hours available), project meetings, communications for the
project, etc.

Constraints:
Discuss any restrictions or limitations that will affect the project.

Milestones:
What are the key events in the project lifecycle? When are the major decision
points and how will they be dealt with?

Roles and Responsibilities Chart:

Indicate by team member and by client what each is responsible for and by
when. What is the specific output and how will it be communicated and used by the
project team?

Risk Analysis:
What are the risks involved in completing the project successfully? For each risk,
identify the probability and expected severity. What will the team do if it occurs?

L. Zon
09/16