CAPM Practice: Explain the components of an adaptive plan
Question 51 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: A large user story that spans multiple iterations and must be broken into smaller stories before implementation
Explanation
An epic is a large backlog item representing significant functionality that can't fit in a single iteration. Epics are broken into user stories for iteration planning. Epics → Features → User Stories → Tasks form the planning hierarchy.
**Why not B:** This choice conflates the literary meaning of "epic" with agile terminology. In agile planning, an epic is a large work item in the backlog, not a recognition mechanism or gamification reward for completing stories.
**Why not C:** Epics in agile are forward-looking backlog items representing future work to be done. They are not retrospective documentation of project history or origin stories.
**Why not D:** The daily standup is a short synchronization ceremony, not a backlog artifact. An epic refers to the scope and scale of a work item, not the duration of a meeting; conflating the two misapplies the term entirely.
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