Template Courtesy of Elemental Projects

Project Charter

/

Version:

Project: / Id:
Project Manager:
Overview
Background and strategic alignment:
History, rational and relevant background information about the project.
High-level goal:
Short statement/snap-shot summing up the project’s objective/purpose.
Governance structure:
Individuals and/or groups that will authorise the project; direct the project manager; provide funding; and to whom the project manager reports and escalates major issues for support/resolution.
Key stakeholders:
Individuals and/or groups involved with the project, affected by the project, or able to affect the project, its execution, or its outcomes.
Alternative approaches:
Other options for achieving the project goal/benefits that have been considered, and the reason why these options were rejected in favour of the current approach.
Assumptions:
Uncertain conditions that are considered likely to be true, and on which current plans are based.
Constraints:
Known facts that will limit the team’s choices in relation to how the project is planned, implemented and closed.
Benefits (post-project)*
Positive results that will emerge after the project has closed / Is a Benefits Realisation Plan required to track this benefit post-project?
* For benefits expected to emerge, or continue to be tracked, AFTER the project has closed (e.g. efficiency, awareness, etc), the Benefits Realisation Plan provides the preliminary measurement of each benefit (like a "before picture"); as well as instructions for how to conduct subsequent benchmarks to measure the achievement/realisation of benefits long term (like an "after picture"). This enables a comparison of benchmarks to determine the effectiveness of the project in achieving the desired benefits. If you answer "yes" above, the Benefits Realisation Plan and benchmarking activities should be included as deliverables.
Project objective/s
Objective/s
What mustbe achieved, before the project closes, in order to call the project “successful”? / MeasurableSuccess Criteria
How will you prove that you have achieved the objective/s? This clarifies the line between “failure” and “success”, so it must be unambiguous – preferably quantifiable criteria that can be (easily) measured before the project closes. It may be arbitrary, and less aspirational than the objective, but serves to clarify what “success” means, to ensure that the project manager, project team, sponsor, and other stakeholders are all on the same page.
1.
2.
3.
Deliverables
Products, services and/or results to be created / Estimated due date / Estimated cost
Estimated project cost:
Estimated project duration:
Authorisation
Name of authoriser/s / Role / Sign-off / Date

Template courtesy of Elemental Projects –

Project Charter_170630Page 1 of 2