What are the elements of user stories?

Question

Options

• AGrouping, ranking, negotiation, decision trees
• BMain topic, keywords, metrics, indicators
• CConversation, acceptance criteria, title, statement of value
• DState tables, flow diagrams, process models, matrices

• A
  2% (1)
• B
  2% (1)
• C
  96% (44)

Explanation

User stories follow the "3 Cs" framework - Card, Conversation, and Confirmation - and the standard template captures a title, a statement of value ("As a [user], I want [goal] so that [benefit]"), conversation (collaborative discussion between stakeholders and the team), and acceptance criteria (the conditions that define "done"). These four elements in option C are the canonical components taught in Agile and Scrum frameworks.

Why the distractors are wrong:

• A (grouping, ranking, negotiation, decision trees) - these are generic analytical techniques, not structural elements of a user story.
• B (main topic, keywords, metrics, indicators) - this sounds like document metadata or reporting terminology, not user story components.
• D (state tables, flow diagrams, process models, matrices) - these are structured analysis/design artifacts used in traditional or systems engineering, not Agile user stories.

Memory tip: Think "CATS" - Conversation, Acceptance criteria, Title, Statement of value. If a user story lacks any of these, the team won't know what to build (title/statement) or how to know when it's done (acceptance criteria/conversation).

No community discussion yet for this question.