Card Conversation and Confirmation
What is Card Conversation and Confirmation?
Card, conversation and confirmation (the three Cs) is Ron Jeffries' model of a user story: a brief written card, a discussion between requesters and builders, and acceptance criteria that confirm the story is done.
Updated November 2026 · 3 min read
Card, Conversation and Confirmation, often called the three Cs, is a model for how user stories work in agile development. The card is a short written statement of the story, the conversation is the discussion between the people who need the work and the people who will build it, and the confirmation is the set of acceptance criteria or tests that show the story is done. The model's main point is that the written story is only a reminder; shared understanding comes from the conversation, and agreement is captured in the confirmation.
Ron Jeffries, one of the creators of Extreme Programming, described the three Cs in a 2001 article. At the time, XP teams wrote stories on index cards, and the small size of a card was deliberate: it could not hold a full specification, so the team had to talk.
The three Cs explained
| Element | What it is | Example |
|---|---|---|
| Card | A brief statement of the need, often in the format "As a [user], I want [goal] so that [benefit]" | As a returning shopper, I want to reorder a past purchase so that I can restock quickly |
| Conversation | Discussion between product owner, developers, testers and others to explore details, edge cases and options | What if an item is out of stock? Should prices update to today's price? |
| Confirmation | Acceptance criteria or tests that define done | Given a past order, when I select Reorder, then in-stock items are added to my cart at current prices |
Card
The card names who the story is for and what they want. It should be small enough to finish in one iteration and clear enough to start a conversation. Today the card is usually a ticket in a tracking tool, which makes it tempting to fill it with paragraphs of detail. The principle still holds: keep the card short and put the effort into the conversation. See user story.
Conversation
The conversation happens mostly during backlog refinement and continues during the sprint. It is where hidden assumptions, edge cases and simpler alternatives come out. A useful conversation includes at least the product owner, a developer and someone thinking about testing, a combination some teams call the "three amigos." Notes, sketches or examples from the conversation can be attached to the card, but the shared understanding is the real output.
Confirmation
Confirmation records what was agreed as concrete, testable acceptance criteria. Many teams write them in the Given, When, Then format from behavior-driven development, which can turn directly into automated acceptance tests. Confirmation closes the loop: the story is done when these criteria pass and the work meets the team's definition of done.
Three Cs example: A reorder story
Consider a hypothetical grocery delivery app. The card reads: "As a returning shopper, I want to reorder a past purchase so that I can restock quickly." In a 20-minute refinement conversation, the tester asks what happens to items that are out of stock or no longer sold, and the developer asks whether to use the old prices. The product owner decides that discontinued items should be skipped with a message, out-of-stock items should be saved for later and current prices should apply.
The team writes four acceptance criteria: in-stock items are added at current prices; discontinued items are skipped with a notice naming them; out-of-stock items are added to a saved list; and the cart total updates immediately. During the conversation the developer also notes that the order history page already loads past items, so the build is smaller than expected, and the team sizes it at 3 points instead of the 8 it had guessed. Without the conversation, the team would likely have built a version that silently failed on discontinued items and found the gap in production.
Common pitfalls
- Turning the card into a specification. Long tickets replace conversation instead of prompting it.
- Skipping the conversation. Stories handed over without discussion recreate the handoff problems agile tries to remove.
- Vague confirmation. "Works correctly" cannot be tested. Criteria should be specific and observable.
- Writing criteria after building. Confirmation agreed late tends to describe what was built, not what was needed.
The three Cs complement the INVEST checklist for good stories, support the team's definition of ready and connect to acceptance test-driven development.
Frequently asked questions
Who created the card, conversation and confirmation model?
Ron Jeffries, one of the creators of Extreme Programming, described the three Cs in a 2001 article. XP teams then wrote user stories on index cards, and the small card was deliberate: it could not hold a full specification, so the team had to talk through the details and then agree on criteria that would confirm the story was done.
Who should take part in the conversation step of the three Cs?
At minimum, the conversation should include the product owner, a developer and someone thinking about testing, a combination some teams call the three amigos. It happens mostly during backlog refinement and continues through the sprint, surfacing hidden assumptions, edge cases and simpler alternatives. Notes or sketches can be attached to the card, but shared understanding is the main output.
How should confirmation be written in the three Cs model?
Write confirmation as specific, observable acceptance criteria, agreed before the work is built. Many teams use the Given, When, Then format from behavior-driven development, which can become automated acceptance tests. Vague criteria such as works correctly cannot be tested. A story counts as done when its criteria pass and the work meets the team's definition of done.
Related terms
User Story
A plain-language statement of what a user wants to do and why.
Backlog Refinement
Preparing upcoming backlog items so they are ready to plan.
Acceptance Test-Driven Development (ATDD)
Agreeing acceptance tests before building a feature.
Confidence Vote (Fist of Five)
A show of fingers that tests whether a team really believes its plan.