You are on page 1of 7

Document Code: PMBOK4.1.3.

<Organization Name>

CEO of <Organization Name>


<Full Name>
<Name and authority of the sponsor or other person(s) authorizing
the Project Charter>

_______________________________

__________________ 2017

<Project Name>
Project Charter
Revision <6.0>

<Note: Text in brackets and/or blue italics is to inform/prompt the author and meant to be deleted or replaced by the
information specified therein before the finalizing/publishing the document. The Project Charter is created during process
4.1 "Develop Project Charter" as described in A Guide to the Project Management Body of Knowledge (PMBOK® Guide). It
is shown in the document code (the first two digits).

The Project Charter is the document issued by the project initiator or sponsor that formally authorizes the existence of a
project and provides the project manager with the authority to apply organizational resources to project activities. It
documents the high-level information on the project and on the product, service or result the project is intended to satisfy.

The Project Charter is developed on the basis of the Business Documents, the Agreements on project implementation and
other information like enterprise environmental factors and organizational process assets.

The Charter is developed by individual(s) external to the project, such as the sponsor, project management office (PMO)
or the portfolio governing body. The project initiator or sponsor should be at a level that is appropriate to procure funding
for the project. They either develop the Charter themselves or delegate this responsibility to the Project Manager. The
initiator’s signature on the Project Charter authorizes the project.

If the organization doesn’t use the Project Charter, it is necessary to obtain or develop the same information, which will be
used then to develop a detailed description of the Project Scope Statement and for further planning.

Attention! Before publishing the document, fill in the Quick Parts (blocks of text set in the boxes). Repeated Quick Parts
are updated automatically. Update the table of contents just before publishing.>

For internal use <Organization Name>, 2017 Page 1 of 7


<Project Name> Revision: <6.0>
Project Charter Date: 29 December, 2017
Document Code: PMBOK4.1.3.1

List of Changes
Date Revision Description Author
<m/d/yyyy> <6.0> Publication for use <Author>

 Revision: The revision number of the document (the first digit is increased and the second one is
set to zero if significant changes are made in the document; the second digit changes if the minor
changes are made).
 Description: A detailed description of the revision and the amendments (for example, Publication
for internal comments, Publication for use, Publication with changes in Chapter X, etc.).
 Author: Full name of the amendments’ author.

For internal use <Organization Name>, 2017 Page 2 of 7


<Project Name> Revision: <6.0>
Project Charter Date: 29 December, 2017
Document Code: PMBOK4.1.3.1

Table of Contents
1. General Provisions 4

2. Normative References 4

3. Terms, Notations, Abbreviations 4

4. Project Purpose 5

5. Measurable Project Objectives and Related Success Criteria 6

6. High-Level Requirements 6

7. High-Level Project Description, Boundaries and Key Deliverables 6

8. Overall Project Risk 6

9. Summary Milestone Schedule 6

10. Preapproved Financial Resources 6

11. Key Stakeholder List 7

12. Project Approval Requirements 7

13. Project Exit Criteria 7

14. Project Manager 7

15. Appendixes 7

For internal use <Organization Name>, 2017 Page 3 of 7


<Project Name> Revision: <6.0>
Project Charter Date: 29 December, 2017
Document Code: PMBOK4.1.3.1

1. General Provisions
<This section describes the general characteristics of this document folder and the set of documents to which it refers.
These general provisions can be modified or supplemented in accordance with the particular project requirements.>

1.1. This document refers to the project "<Project Name>", which is implemented by the organization
"<Organization Name>".
1.2. The Project Charter formulates the practical requirements and documents the high-level
description of the product, service or other deliverable that should meet these requirements and
will be result of the project.
1.3. The Project Charter is issued and signed by the Initiator or Sponsor of the project and formally
legitimized the existence of the project. It provides the Project Manager with the authority to use
the organizational assets in the project operations.
1.4. The approved Project Charter formally initiates the project.
1.5. If the project consists of several phases, the Charter can be updated to verify or improve the
decisions taken during the previous iteration of the Project Charter development. In such a case
the Charter is re-issued and signed as amended.

2. Normative References
<This section should contain a complete list of documents mentioned in this Charter. Each document should be identified
by a corresponding title, number (if applicable), date and name of publishing company or author. Define the sources that
can provide reference information. The table below is populated with samples.>

2.1. This document refers to the following documents:


Number Name Publishing Author
Date
A Guide to the Project Management Body of Knowledge
PMBOK® Guide 2017 PMI
— Sixth Edition
PMBOK4.1.1.1 Business Documents PM
PMBOK5.2.3.2 Requirements Traceability Matrix PM
PMBOK5.3.3.1 Project Scope Statement PM
PMBOK6.2.3.3 Milestone List PM
PMBOK7.3.3.1 Cost Baseline PM
PMBOK10.1.3.1 Communications Management Plan PM
PMBOK11.2.3.1 Risk Register PM
PMBOK12.2.3.2 Agreement PM
PMBOK13.1.3.1 Stakeholder Register PM

3. Terms, Notations, Abbreviations


<This section should contain the definitions of all terms, notations and abbreviations required to properly interpret this
document. The terms, notations and abbreviations should be arranged in alphabetical order. This information can be
presented in the form of the following table, or as a reference to a Project Glossary in the Communications Management
Plan>

3.1. Terms used in this document:

For internal use <Organization Name>, 2017 Page 4 of 7


<Project Name> Revision: <6.0>
Project Charter Date: 29 December, 2017
Document Code: PMBOK4.1.3.1

Term Definition
Organizational Process Plans, processes, policies, procedures and knowledge bases that
Assets are specific to and used by the performing organization.
Deliverable Any unique and verifiable product, result or capability to perform a
service that is required to be produced to complete a process, phase
or project.
Requirement A condition or capability that is necessary to be present in a product,
service or result to satisfy a business need.
Stakeholder An individual, group or organization that may affect, be affected by or
perceive itself to be affected by a decision, activity or outcome of a
project, program or portfolio.
Enterprise Conditions, not under the immediate control of the team, that
Environmental Factors influence, constrain or direct the project, program or portfolio.
Objective Something toward which work is to be directed, a strategic position
to be attained, a purpose to be achieved, a result to be obtained, a
product to be produced or a service to be performed.

3.2. Notations used in this document:


Notation Complete Form
Organization <Organization Name>

3.3. Abbreviations used in this document:


Abbreviation Complete Form
PMBOK A Guide to the Project Management Body of Knowledge

4. Project Purpose
<This section briefly describes the purpose of the project and its justification. The justification describes the necessary
information from a business standpoint to determine whether or not the project is worth the required investment.
Justification describes one or more of the following factors:
• Market demand (e.g., a car company authorizing a project to build more fuel-efficient cars in response to gasoline
shortages)
• Organizational need (e.g., a training company authorizing a project to create a new course to increase its revenues)
• Customer request (e.g., an electric utility authorizing a project to build a new substation to serve a new industrial
park)
• Technological advance (e.g., an electronics firm authorizing a new project to develop a faster, cheaper and smaller
laptop after advances in computer memory and electronics technology)
• Legal requirement (e.g., a paint manufacturer authorizing a project to establish guidelines for handling toxic
materials)
• Ecological impacts (e.g., a company authorizing a project to lessen its environmental impact)
• Social need (e.g., a nongovernmental organization in a developing country authorizing a project to provide potable
water systems, latrines and sanitation education to communities suffering from high rates of cholera).
These factors may also be called incentives, opportunities or business requirements. The basic point of all these factors is
that management should decide what the response should be to them, and what projects should be authorized and fixed in
the Charter.>

For internal use <Organization Name>, 2017 Page 5 of 7


<Project Name> Revision: <6.0>
Project Charter Date: 29 December, 2017
Document Code: PMBOK4.1.3.1

5. Measurable Project Objectives and Related Success Criteria


<This section describes the measurable project objectives and related success criteria:

 Objective is something toward which work is to be directed, a strategic position to be attained, a purpose to be
achieved, a result to be obtained, a product to be produced or a service to be performed.
 Criteria are the standards, rules or tests on which a judgment or decision can be based or by which a product,
service, result or process can be evaluated.>
6. High-Level Requirements
<This section documents the requirements that satisfy the needs, wishes and expectations of the Customer, Sponsor and
other project participants. Requirements are the certain conditions or capabilities that must be met or possessed by a
system, product, service, result or component to satisfy a contract, standards, specifications or other formally imposed
documents.

Requirements include the quantified and documented needs, wants and expectations of the Sponsor, Customer and other
stakeholders of the project. In the phase of the Project Charter development, the requirements are usually less concrete;
they becomes more concrete during the subsequent processes according to the gradual elaboration of the project.

Please note that the Project Charter contains high-level requirements only. The complete list of requirements should be
presented in the Requirements Traceability Matrix.>
7. High-level Project Description, Boundaries and Key Deliverables
<This section provides a general description of the products or services that the project is supposed to produce; there is a
brief description of the business need, a very general description of the product and an initial strategic plan.>
8. Overall Project Risk
<This section describes the high-level risks and also provides a brief description of the project risk management
implementation and the risk tolerance levels of the project Sponsor and Customer.

Please note that the Project Charter contains high-level risks only. The complete list of risks should be presented in the
Risk Register.>
9. Summary Milestone Schedule
<This section contains an aggregate schedule of works showing the dates of the main milestones. The Customer or
performing organization can preset the milestones and the required dates of their execution. These dates can be identified
as constraints on the terms. Use the following table.

Please note that the Project Charter contains high-level milestones only. The complete list of milestones should be
presented in the Milestone List.>

No. Milestone Responsible Party Date


<Title of the milestone> <Customer or performing organization>
1.
2.
3.

10. Preapproved Financial Resources


<This section contains formal periodic restrictions on expenditures provided in the project or specified in the Agreement on
project implementation.

Please note that the Project Charter contains summary budget only. The itemized budget should be presented in the Cost
Baseline.>

For internal use <Organization Name>, 2017 Page 6 of 7


<Project Name> Revision: <6.0>
Project Charter Date: 29 December, 2017
Document Code: PMBOK4.1.3.1

11. Key Stakeholder List


<This section contains the list of individuals, groups or organizations who may affect, be affected by or perceive itself to be
affected by a decision, activity or outcome of a project.

Please note that only main stakeholders are specified in the Project Charter. The complete list of stakeholders should be
presented in the Stakeholder Register.>

Full Name Position/Organization Role in the Project Telephone/E-mail


<Position of the stakeholder and <What kind of work is <Key contact information
<Full name of the
organization name> performed by the stakeholder of the stakeholder >
stakeholder>
in the project>

12. Project Approval Requirements


<This section specifies what constitutes project success, who decides the project is successful and who signs off on the
project. This section also identifies the acceptance criteria, including performance requirements and essential conditions
that must be satisfied before the acceptance of the project deliverable.>
13. Project Exit Criteria
<This section specifies what conditions need to be met in order to close or to cancel the project or phase (e.g.,
documented approvals, completed documents, completed deliverables).>
14. Project Manager
<This section contains information about the assigned Project Manager, responsibility and authority level.
A Project Manager is identified and assigned as early in the project as is feasible, preferably while the project charter is
being developed and always prior to the start of planning. It is recommended that the Project Manager participate in the
development of the Project Charter because this document provides him/her with the authority to use the organization
assets to complete the project and responsibility for the project objectives achievement.>
15. Appendixes
<This section contains all appendixes to the document. In the absence of appendixes, this section is excluded.>

<Attention! Fill in the Quick Parts and update the Table of Contents before publishing the document.>

For internal use <Organization Name>, 2017 Page 7 of 7