PROJECT CHARTER

Name of Project or Initiative:
Date:

PURPOSE

(Describe the business need, opportunity or problem that the team has been formed to address, i.e. the project justification.)

DELIVERABLES

(Provide a high-level list of “what” needs to be done in order to complete the project or initiative (the deliverables will define “what success looks like” for this initiative. Each deliverable should be sufficiently detailed so that the Team will understand what needs to be accomplished. Describe the deliverable using action words (verbs) such as “deliver”, “provide”, “create”, “research”, etc. Deliverables should be measurable, so the Project Sponsor and Team can determine whether the deliverable has been successfully completed at the project’s conclusion.

SCOPE DEFINITION

Scope sets boundaries for the Team and empowers them. Scope should be defined to provide the Team clear authority to explore and challenge existing processes, practices, etc., or to conduct research, make contacts, consult with experts, etc. in certain areas. Out-of-scope areas should also be defined so the Team does not waste valuable cycles or cause undue disruption to the rest of the organization. For example, a Team working on process improvement may be authorized to recommend changes to roles and responsibilities, and to recommend new positions (in scope), but may not be authorized to investigate performance and pay of people currently involved in the process (out of scope).

PLAN & MILESTONES

A high-level timeline with significant project milestones, generally tied to deliverables.

ASSUMPTIONS, CONSTRAINTS & DEPENDENCIES

Identify the assumptions that the team should incorporate into its planning; especially include $$ budgeted for the study, if any, so the team knows its spending authority. List any constraints (potential factors that will impact the delivery or make it difficult for the team to produce its deliverables; list dependencies as well. Consider time, cost, date, and regulatory issues as constraints or dependencies to the project. Keep in mind the kind of help you will need from project sponsors to remove obstacles and make sure necessary dependencies are in place.

RELATED DOCUMENTS

TEAM STRUCTURE (Add or delete lines as needed.)

Indicate Team Leader if one is being recommended/appointed.
Name / Area / Role

SPONSOR & PROJECT BOARD APPROVAL (Note: Project Board should be comprised of key stakeholders and not necessarily executive management.) (Add or delete lines as needed.)

Project Sponsor (signature): / Printed Name and Title: / Date:
Project Board Member (signature): / Printed Name and Title: / Date:
Project Board Member (signature): / Printed Name and Title: / Date:
Project Board Member (signature): / Printed Name and Title: / Date:

For Internal Use OnlyPage 1 of 3