In the PMBOK Guide, the process of Create WBS involves subdividing project deliverables and project work into smaller, more manageable components. The lowest level of the WBS is a critical milestone in planning.
Why Choice C is correct:
Defining the Work Package: The lowest level of a WBS is officially called a Work Package. A work package is the point at which the cost and duration for the work can be reliably estimated and managed.
The 8/80 Rule: Project leads often use the " 8/80 rule " as a guideline for decomposition-a work package should take no less than 8 hours and no more than 80 hours of effort.
Deliverable-Oriented: The WBS is a deliverable-oriented hierarchical decomposition. It focuses on what is being delivered, rather than the chronological actions taken to create it. Once you reach the level where a single person or team can be held accountable for a specific deliverable, you have reached the work package level.
Analysis of other options:
A (Decompose to the activity or task level): This is a very common point of confusion. In the PMI framework, Activities and Tasks are part of the Project Schedule, not the WBS. You decompose the WBS into work packages first, and then later, in the " Define Activities " process, you break those work packages down into the activities needed to complete them.
B (Decompose until all risks are identified): While a detailed WBS helps in identifying risks, " risk identification " is not the criteria for WBS completion. You could identify risks at a very high level or a very low level; it doesn ' t provide a standardized " stopping point " for the structure.
D (Decompose until a WBS dictionary is obtained): This is a circular argument. The WBS Dictionary is a document that provides detailed information about each component in the WBS. You don ' t decompose to the dictionary; you create the dictionary to describe the components (like work packages) you have already decomposed.
Key Concept: The Project Management Institute (PMI) emphasizes that the Work Package (Choice C) is the " bottom line " of the scope baseline. Breaking the WBS down too far (to tasks) leads to micromanagement and bloated documentation, while not breaking it down far enough leads to poor cost estimation and lack of control. Identifying the work package level is the key to balanced project oversight.