According to the Agile Practice Guide and the PMBOK® Guide, moving from a predictive (Waterfall) framework to an adaptive (Agile) framework requires a shift from " task-oriented " structures to " value-oriented " structures.
Why Choice D is correct:
Structural Alignment: In a predictive approach, the Work Breakdown Structure (WBS) is a hierarchical decomposition of the total scope. In an adaptive approach, the equivalent hierarchy is the Product Backlog, which is organized by value.
The Conversion Process:
Themes: High-level functional areas or business goals (often corresponding to the top levels of a WBS).
Epics: Large bodies of work that can be broken down into smaller tasks (corresponding to WBS work packages).
User Stories: The smallest units of work that deliver a specific value to the end user (corresponding to the activities derived from work packages).
Outcome: By mapping WBS elements into these categories, the team ensures that the original scope is preserved while making it " consumable " for iterative development.
Analysis of other options:
A (Generate use cases and requirements document): This is a traditional requirements gathering approach. While use cases are helpful, simply writing a requirements document does not " convert " the WBS into a delivery framework; it just creates more documentation.
B (Release plan for each element): A release plan is a timeline. While you eventually need one, you cannot build a release plan directly from a raw WBS without first translating the work into backlog items (User Stories) that the team can estimate and prioritize.
C (Create themes and organize into iterations): This is close, but it skips the necessary granularity. Iterations (Sprints) are populated by User Stories, not broad Themes. Without breaking themes down into epics and stories (as seen in Choice D), the work is too large to fit into a typical 2-week iteration.
Key Concept: The Project Management Institute (PMI) emphasizes that in an adaptive environment, work must be decomposed by value rather than just by " work type. " Choice D provides the necessary structural bridge to take a finalized scope (WBS) and turn it into a living Product Backlog that an Agile team can actually execute.
