Who signs the project charter

Project Charter And Project Management Plan

Project Charter
Revision <6.0>

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.>

[Type here]

List of Changes
Date

Revision

Description

Author

<6.0>

Publication for use

· 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.

Table of Contents 1. General Provisions 4 2. Terms and Abbreviations Error! Bookmark not defined. 3. Project Purpose 4 4. Measurable Project Goals and Objectives 4 5. High-Level Project Description and Boundaries 5 6. High Level Requirements 5 7. Key Project 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/ Exit Criteria 7 13. Project Exit Criteria 7 14. Project Manager 7 15. Appendixes 7

1. General Provisions

This document refers to the project "", which is implemented by the organization "".

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.

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.

The approved Project Charter formally initiates the project.

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.

Terms, Notations, Abbreviations

Term/Abbreviation

Definition

Project Purpose

· 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.>

Measurable Project Goals and Objectives

Business Goal 1:

· Project Objective 1.1:

· Project Objective 1.2:

· Project Objective 1.3

Business Goal 2:

· Project Objective 2.1

· Project Objective 2.2

Business Goal 3:

· Project Objective 3.1:

· Project Objective 3.2:

· Project Objective 3.3

High-level Project Description and Boundaries

High-Level Requirements

Requirements include the quantified and documented needs, wants and expectations of the Sponsor, Customer and other stakeholders of the project. The Project Charter contains high-level requirements only. A complete list requirements should be developed later in the Project Management plan as they become more concrete during the gradual elaboration of the project.

Overall Project Risk

Please note that the Project Charter contains high-level risks only. The complete list of risks should be presented in the Risk Register.>

High Level Constraints and Assumptions

Constraints:

· Constraint 1

· Constraint 2

· Constraint 3

Assumptions

· Assumption 1

· Assumption 2

· Assumption 3

Summary Milestone Schedule

No.

Milestone

Responsible Party

Date