CAPM Practice: Explain the components of an adaptive plan
Question 9 of 60 in Explain the components of an adaptive plan
Pick an answer below — you'll get the explanation instantly, no signup.
Show answer & explanation
Correct answer: Themes → Epics → User Stories: themes are highest-level strategic areas; epics are large features within themes; stories are implementable work items within epics
Explanation
The hierarchy (Themes → Epics → Stories) provides layered planning granularity. Themes represent large strategic objectives (e.g., 'Improve user onboarding'). Epics are large features within a theme (e.g., 'Streamlined registration flow') too big for one sprint. User stories are implementable within one sprint. This hierarchy supports both high-level roadmapping (themes/epics) and sprint-level planning (stories).
**Why not A:** Themes and epics are not predictive-only concepts. They are commonly used in adaptive planning to organize the product backlog and support roadmapping at different levels of granularity, connecting strategic objectives to sprint-level work.
**Why not B:** This reverses the hierarchy. Themes, not epics, are the highest-level strategic areas, and epics are large features within a theme. Themes group related work around a strategic objective rather than grouping sprints, and stories are implementable work items, not merely planning items.
**Why not C:** Themes, epics, and user stories are distinct concepts at different levels of granularity, not interchangeable names. A theme is a broad strategic objective, an epic is a large feature too big for one sprint, and a user story is small enough to complete within one sprint.
Key Concept
This question covers Explain the components of an adaptive plan under Explain the components of an adaptive plan (Agile Frameworks/Methodologies).
All 1,500+ CAPM questions are free
Sign up to track your progress, see detailed analytics, and get personalized study recommendations.
Sign Up Free