According to the PMBOK Guide, the Create WBS process is the process of subdividing project deliverables and project work into smaller, more manageable components. To perform this decomposition accurately, the project manager needs specific inputs that define what needs to be built.
* Requirements Documentation: This is a key input. It provides the detailed description of what the project must deliver to meet stakeholder expectations. Since the WBS is a deliverable-oriented decomposition of the work, the requirements documentation ensures that all necessary features and functions are accounted for in the breakdown.
* Other Key Inputs to Create WBS:
* Project Scope Statement: This is the primary input, as it describes the work that will be performed and the work that is excluded.
* Scope Management Plan: Provides the " how-to " for creating the WBS from the scope statement.
* Enterprise Environmental Factors (EEFs): Industry-specific WBS standards relevant to the project ' s domain.
* Organizational Process Assets (OPAs): Policies, procedures, and WBS templates from previous projects.
Analysis of Other Options:
* B. scope baseline: This is the output of the Create WBS process, not an input. The Scope Baseline consists of the Project Scope Statement, the WBS, and the WBS Dictionary.
* C. project charter: While the Charter provides a high-level description of the project, it is an input to the Define Scope process. By the time you reach Create WBS, you use the more detailed Project Scope Statement derived from the Charter.
* D. validated deliverables: These are an output of the Control Quality process and an input to Validate Scope. They are not used to create the work breakdown structure, which is a planning activity.