Explanation/Reference:
Explanation:
4.1.3.1 Project Charter
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 business needs, assumptions, constraints, the understanding of the customer's needs and high-level requirements, and the new product, service, or result that it is intended to satisfy, such as:
Project purpose or justification,

Measurable project objectives and related success criteria,

High-level requirements,

Assumptions and constraints,

High-level project description and boundaries,

High-level risks,

Summary milestone schedule,

Summary budget,

Stakeholder list,

Project approval requirements (i.e., what constitutes project success, who decides the project is

successful, and who signs off on the project),
Assigned project manager, responsibility, and authority level, and

Name and authority of the sponsor or other person(s) authorizing the project charter.

Process: 5.3 Define Scope
Definition: The process of developing a detailed description of the project and product.
Key Benefit: The key benefit of this process is that it describes the product, service, or result boundaries by defining which of the requirements collected will be included in and excluded from the project scope.
Inputs
1. Scope management plan
2. Project charter
3. Requirements documentation
4. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Product analysis
3. Alternatives generation
4. Facilitated workshops
Outputs
1. Project scope statement
2. Project documents updates