Translations:Historia de usuario/2/en

Unlike traditional specification documents, a user story is not a closed contract: it is a starting point for conversation. Ron Jeffries described this idea with the three Cs: Card, Conversation, and Confirmation. The card is the physical or digital medium; the conversation is the dialogue between the team and the Product Owner that provides the real context; and the confirmation is the acceptance criteria that determine when the story is done.

Structure

The structure of a user story includes:

• Name: short and descriptive. It is used as a reference in the Product Backlog and in team conversations.
• Description: usually expressed with the formula As a [type of user], I want [functionality], so that [benefit]. It describes who needs the functionality, what they need, and why.
• Acceptance criteria: conditions that must be met for the Product Owner to consider the story done and acceptable.
• Additional information: priority, risk, size estimate, or other fields the team needs to manage the backlog.

User story example