This question reinforces a fundamental concept in the PMBOK® Guide regarding the structure of the Work Breakdown Structure (WBS). While a project manager may be tempted to break work down as far as possible, there is a specific formal " stopping point " in the WBS hierarchy.
Why Choice D is correct:
The Definition of a Work Package: The Work Package is the lowest level of the WBS. It is the point at which cost and duration can be estimated with high confidence and where the work can be effectively managed and controlled.
Control Accounts: Work packages are often grouped into Control Accounts for management and reporting purposes, but the decomposition process itself stops once you reach a manageable " unit " of a deliverable.
Accountability: A work package represents a specific deliverable or project work component that can be assigned to a single person or a specific team.
Analysis of other options:
A (Activity level): Activities are the specific actions required to complete a work package. While work packages are decomposed into activities, this happens during the Define Activities process in Schedule Management, not during the creation of the WBS.
B (Deliverable level): " Deliverable " is a generic term. While the WBS is deliverable-oriented, it contains many levels of deliverables (from the whole project down to sub-components). The specific name for the lowest level of that decomposition is the work package.
C (Task level): Similar to activities, " tasks " are generally considered smaller units of work within an activity or work package. Breaking a WBS down to the task level is often considered micromanagement and makes the WBS too complex to maintain.
Key Concept: The Project Management Institute (PMI) teaches that proper decomposition is a balance. By stopping at the Work Package level (Choice D), the project manager ensures that the scope is clearly defined without the overhead of tracking every minute task, providing the perfect foundation for the Scope Baseline.
