The acceptance criteria associated with a user story:

Question

Options

• Aare often written in a rule-oriented format using the template referred to as "Given/When/Then"
• Bare often documented following in rule-oriented format using the following template: "As a [role], I
• Ccan be written in different formats and represent an aspect of a user story referred to as
• Dmust be written in one of the two following formats: scenario-oriented or rule-oriented

• A
  2% (1)
• B
  7% (3)
• C
  89% (39)
• D
  2% (1)

Explanation

The acceptance criteria associated with a user story are the conditions that must be met for the user story to be considered done and to deliver the expected value to the user. They are often written in different formats, such as rule-oriented, scenario-oriented, or table-oriented, depending on the nature and complexity of the user story. They represent an aspect of a user story referred to as confirmation, which is one of the so called "3 C's" of user stories. The other two aspects are card and conversation. Card refers to the concise and informal description of the user story, usually following the template: "As a [role], I want [feature], so that I can [benefit]". Conversation refers to the ongoing dialogue between the stakeholders and the team members to clarify and refine the user story and its acceptance criteria.

No community discussion yet for this question.