Which document includes the project scope, major deliverables, assumptions, and constraints?

According to the PMBOK® Guide, specifically the Define Scope process, the Project Scope Statement is the primary output that provides a documented description of the project scope, major deliverables, and the work required to create those deliverables.

Detailed Content: While the Project Charter contains high-level information, the Project Scope Statement contains a much more detailed description of the scope components. It explicitly includes:

Product scope description: Progressively elaborates the characteristics of the product, service, or result.

Deliverables: Any unique and verifiable product, result, or capability.

Acceptance criteria: A set of conditions that is required to be met before deliverables are accepted.

Project Exclusions: Explicitly states what is excluded from the project to manage stakeholder expectations (the " out of scope " list).

Assumptions: Factors in the planning process that are considered to be true, real, or certain without proof.

Constraints: Limiting factors that affect the execution of a project, such as budget, schedule, or resources.

Comparison with other options:

A. Project charter: The charter is a high-level document. While it may contain a summary of scope and major deliverables, the " detailed " and " typical " repository for specific assumptions, constraints, and granular deliverables is the Scope Statement.

C. Scope management plan: This is a component of the Project Management Plan that describes how the scope will be defined, developed, monitored, controlled, and validated. It does not contain the actual scope itself.

D. Project document updates: This is a generic output category. While the scope statement is a project document, this option is too broad to be the correct answer for a document defined by these specific contents.