A project team working on a complex product and the work breakdown structure (WBS) is finalized. The team determines that the best approach is to use an adaptive delivery method and is now tasked…

Question

Options

• AGenerate use cases for each WBS element and prepare a requirements document.
• BCreate themes for each WBS element and organize them into iterations for delivery.
• COrganize the WBS into a set of related themes, epics, and user stories.
• DProduce a release plan for each WBS element and organize them into iterations for delivery.

• A
  8% (2)
• B
  19% (5)
• C
  69% (18)
• D
  4% (1)

Explanation

When converting a traditional WBS to an adaptive approach, the hierarchy maps to the agile artifact hierarchy: high-level WBS deliverables become themes (strategic groupings), features and capabilities become epics (large bodies of work), and detailed work packages become user stories (individual, deliverable units of functionality). This preserves the full scope captured in the WBS while restructuring it for iterative, incremental delivery. The other options - generating use cases, creating release plans, or creating simple iterations per element - do not represent the standard adaptive conversion approach and skip the theme/epic/story hierarchy that gives the backlog its structure.

No community discussion yet for this question.