Project Purpose Measurable Project Objectives and Related Success Criteria High-Level Requirements High-level Project Boundaries and Key Deliverables Overall Project Risk Summary Milestone Schedule No. Milestone

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

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

3. High-Level Requirements

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

4. High-level Project Boundaries and Key Deliverables

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

6. 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.	Milestone	Date