A User Story includes which three things? (Choose three.)

Question

Options

• AWho
• BLevel of Risk
• CWhy
• DWhat
• EDefinition of Done
• FHow

• A
  92% (34)
• B
  3% (1)
• F
  5% (2)

Explanation

A User Story follows the classic template: "As a [Who], I want [What], so that [Why]" - capturing the user role, the desired functionality, and the business value behind the request. This three-part format ensures stories remain focused on user needs rather than technical solutions.

Why the distractors are wrong:

• B (Level of Risk) - Risk is assessed during planning (e.g., sprint planning or backlog refinement), not defined within the story itself.
• E (Definition of Done) - The DoD is a team-level agreement applied across all stories, not a component written inside a single story.
• F (How) - User Stories deliberately omit implementation details; how something is built is left to the development team to decide.

Memory tip: Use the phrase "3 Ws" - Who, What, Why - or remember the template sentence: "As a [Who], I want [What], so that [Why]." If you can fill in that sentence, you have a complete User Story.

No community discussion yet for this question.