Do PROJECT CHARTER FOLLOWING THIS TEMPLATE

PROJECT : DESIGN AND CONSTRUCTION OF AN ELECTRIC CAR

Document Code: PMBOK4.1.3.1

<DESIGN AN CONTRACTION OF AN ELECTRIC CAR>

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.

List of Changes

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

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

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

1. High-Level Requirements

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

1. High-level Project Description, Boundaries and Key Deliverables

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

1. Summary Milestone Schedule

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

No.MilestoneResponsible PartyDate