An input to the Create WBS process is a:

According to the PMBOK® Guide, specifically within the Project Scope Management knowledge area, the Create WBS process involves subdividing project deliverables and project work into smaller, more manageable components.

Project Scope Statement as a Primary Input: The Project Scope Statement is the most critical input for creating the Work Breakdown Structure (WBS). It contains the detailed description of the project scope, major deliverables, assumptions, and constraints. Without this detailed definition of what needs to be accomplished, the team cannot accurately decompose the work into work packages.

Other Key Inputs:

Project Management Plan: Specifically the scope management plan, which defines how the WBS will be created from the scope statement.

Project Documents: Including the Requirements Documentation, which describes the high-level requirements that must be met by the deliverables defined in the WBS.

EEFs and OPAs: Standard industry WBS templates or organizational policies for work breakdown.

The Process Logic: The flow of scope management moves from Collect Requirements → Define Scope (resulting in the Scope Statement) → Create WBS (resulting in the Scope Baseline). Therefore, the output of the previous process (the Scope Statement) becomes the direct input for the next.

Comparison with other options:

A. project charter: This is an input to the Define Scope process. While it contains high-level information, it lacks the technical detail required to build a WBS.

B. stakeholder register: This is primarily used in Collect Requirements and Plan Communications Management to identify who has a " say " in the project, but it does not define the work to be broken down.

D. requirements traceability matrix: This is a document that links product requirements from their origin to the deliverables that satisfy them. While it is a project document, it is used more for Validating Scope and tracking, rather than as the foundational architectural input for the WBS.