Section: Volume D
Explanation
Explanation:
Process: 4.1. Develop Project Charter
Definition: The process of developing a document that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
Key Benefit: The key benefit of this process is a well-defined project start and project boundaries, creation of a formal record of the project, and a direct way for senior management to formally accept and commit to the project.
Inputs
1. Project statement of work
2. Business case
3. Agreements
4. Enterprise environmental factors
5. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Facilitation techniques
Outputs
1. Project charter

Section: Volume B

Explanation/Reference:
Explanation:
Process: 11.3 Perform Qualitative Risk Analysis
Definition: The process of prioritizing risks for further analysis or action by assessing and combining their probability of occurrence and impact.
Key Benefit: The key benefit of this process is that it enables project managers to reduce the level of uncertainty and to focus on high-priority risks.
Inputs
1. Risk management plan
2. Scope baseline
3. Risk register
4. Enterprise environmental factors
5. Organizational process assets
Tools & Techniques
1. Risk probability and impact assessment
2. Probability and impact matrix
3. Risk data quality assessment
4. Risk categorization
5. Risk urgency assessment
6. Expert judgment
Outputs
1. Project documents updates

Section: Volume C
Explanation:
5.3.3.1 Project Scope Statement
The project scope statement is the description of the project scope, major deliverables, assumptions, and constraints. The project scope statement documents the entire scope, including project and product scope. It describes, in detail, the project's deliverables and the work required to create those deliverables. It also provides a common understanding of the project scope among project stakeholders. It may contain explicit scope exclusions that can assist in managing stakeholder expectations. It enables the project team to perform more detailed planning, guides the project team's work during execution, and provides the baseline for evaluating whether requests for changes or additional work are contained within or outside the project's boundaries.
The degree and level of detail to which the project scope statement defines the work that will be performed and the work that is excluded can help determine how well the project management team can control the overall project scope. The detailed project scope statement, either directly, or by reference to other documents, includes the following:
Product scope description. Progressively elaborates the characteristics of the product, service, or result

described in the project charter and requirements documentation.
Acceptance criteria. A set of conditions that is required to be met before deliverables are accepted.

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. Deliverables also include ancillary results, such as project management reports and documentation. These deliverables may be described at a summary level or in great detail.