Which statement is true about Features and Stories?

Question

Options

• AFeatures should be small enough to fit into an Iteration
• BFeatures can be larger than an Iteration but Stories should be small enough to fit into an Iteration
• CThey are prioritized by the team
• DThey are estimated like User Stories

• B
  92% (23)
• C
  4% (1)
• D
  4% (1)

Explanation

Option B is correct because in scaled agile frameworks like SAFe, Features represent larger chunks of functionality that span multiple Iterations (Sprints), while Stories are decomposed from Features and sized to fit within a single Iteration - this is a fundamental sizing hierarchy.

Why the distractors are wrong:

• A reverses the rule: it's Stories, not Features, that must fit within an Iteration; Features are intentionally larger.
• C is misleading because Features are prioritized by Product Management at the Program level, while Stories are prioritized by the Product Owner at the Team level - not "the team" for both.
• D is incorrect because Features are estimated using different techniques (e.g., t-shirt sizing or weighted shortest job first), while User Stories use story points; they don't share the same estimation approach.

Memory tip: Think of the hierarchy as a Russian nesting doll - a Feature is the outer doll that contains multiple Stories (inner dolls). The outer doll is too big to fit in one Iteration box, but each inner Story doll fits perfectly inside it.

No community discussion yet for this question.