PMI-ACP · Question #592
During iteration planning, it was determined that an epic should be decomposed. What was the determining factor?
The correct answer is A. Size and priority. An epic is decomposed into user stories when two conditions align: it is large enough to warrant breakdown (size) and it is important enough to be worked on soon (priority). Size determines whether an epic can fit within a sprint as-is; if it cannot, it must be broken down…
Question
During iteration planning, it was determined that an epic should be decomposed. What was the determining factor?
Options
- ASize and priority
- BMinimum marketable features
- CRelease plan
- DSprint mapping
How the community answered
(38 responses)- A95% (36)
- C3% (1)
- D3% (1)
Explanation
An epic is decomposed into user stories when two conditions align: it is large enough to warrant breakdown (size) and it is important enough to be worked on soon (priority). Size determines whether an epic can fit within a sprint as-is; if it cannot, it must be broken down. Priority determines when decomposition needs to happen - there is no value in breaking down an epic that won't be worked on for many sprints. Minimum marketable features (B) and release plans (C) are planning inputs but are not the primary triggers for epic decomposition decisions. Sprint mapping (D) is an output of planning, not a determining factor. Size and priority together are the standard agile criteria for decomposing epics during iteration planning.
Topics
Community Discussion
No community discussion yet for this question.