Exam CAPM topic 1 question 298 discussion

When transitioning from a traditional (predictive) to an adaptive (agile) delivery method, the goal is to shift from a document-driven, hierarchical structure like the WBS to a value-driven, incremental delivery model such as: Themes → Epics → User Stories

Why the other options are less suitable: A. Generate use cases for each WBS element and prepare a requirements document: ❌ Use cases and detailed requirements documents are more aligned with traditional, predictive projects rather than adaptive Agile frameworks. B. Create themes for each WBS element and organize them into iterations for delivery: ❌ Themes alone are too high-level; user stories and epics are needed to break down work into actionable pieces. D. Produce a release plan for each WBS element and organize them into iterations for delivery: ❌ A release plan is important but does not address the need to break down the WBS into Agile-friendly units like themes, epics, and user stories.

C. Organize the WBS into a set of related themes, epics, and user stories. Explanation: To successfully transition from a traditional WBS to an adaptive approach, the team needs to break down the work into smaller, more manageable units. This is best achieved by: Organizing the WBS into themes: These represent broad areas of the product. Identifying epics: These are larger bodies of work within a theme. Creating user stories: These are granular descriptions of desired product features.