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.