Description
User stories have three critical components often called the 3Cs: card, conversation, and confirmation. User stories are often written on cards, or a digital equivalent. The card does not contain all the information, but is a reminder of what the story is about for the requirements discovery and backlog grooming ceremony. The detail about each requirement, epic, or story is communicated from the product owner to the agile team through conversation that involves an exchange of views, scenarios, and operational workflow. The product owner typically defines the confirmation, or acceptance criteria, directly before user stories are selected for each sprint.
Communication of the confirmation criteria to the agile team ensures that the team and the product owner have a shared understanding of the product’s features and functions. The product owner may also capture confirmation criteria in acceptance tests that are performed for each user story. When the acceptance tests yield passing results, it confirms to the customer that the associated user story is truly done.
Typical Roles
Scrum Team
Product Owner
Stakeholder
Scrum Master
Desired Behaviors
- 1.
Specific acceptance criteria (definition of done) is established for each user story.
- 2.
The acceptance criteria is shared with, and agreed to, by the team.
- 3.
The product owner confirms that each story is complete before it can be considered “done.”
- 4.
All acceptance tests are in a passing state before product or service is delivered.