The 3 Cs: Card, Conversation, Confirmation
A user story isn't a spec; it's a promise for a conversation. The 3 Cs model this: the Card is a placeholder, the Conversation clarifies requirements, and the Confirmation defines "done" with acceptance criteria.
The mental model
A user story is not a detailed specification document. It's a placeholder, a promise to have a conversation. The "3 Cs" framework—Card, Conversation, Confirmation—describes the life cycle of a story from a simple idea to a validated piece of work.
How it works
The process follows three stages. First, the CARD: a physical or digital card with a short, user-centric description of a requirement (e.g., "As a user, I want to reset my password"). It's intentionally brief. Second, the CONVERSATION: this is a collaborative discussion between the product owner, developers, and testers to explore the details, scope, and context of the card. This is where the real requirements are uncovered. Third, the CONFIRMATION: this is the output of the conversation, typically captured as a set of acceptance criteria. These criteria are concrete, testable conditions that must be met for the story to be considered "done."
When to use it
Use the 3 Cs model for every user story in an Agile backlog. It's the fundamental process for turning a high-level idea into an actionable and testable work item. It ensures shared understanding and prevents the "waterfall-in-a-sprint" anti-pattern where developers are just handed a list of tasks.
When not to use it
The model is less applicable for simple, unambiguous tasks that require no discussion, like "Upgrade the database server to version 5.8." However, even for technical tasks, a quick conversation can often prevent misunderstandings about scope or impact. The primary footgun is thinking a task is too simple for a conversation.
One canonical example
A product owner writes a card: "As a shopper, I want to see my order history." The team then has a conversation: "How many orders should we show? What details for each? What happens if there are no orders? Is it paginated?" They then create the confirmation: "1. The user can access the page from their account menu. 2. The page lists the last 10 orders. 3. Each order shows the date, total price, and status. 4. A 'View Details' link is present for each order." The card is the prompt, the conversation adds the meat, and the confirmation is the test.
Interview question
In the 3 Cs model, what is the main goal of the "Conversation" stage?
- a.To formally approve the story for development and assign it to a team.
- b.To draft the initial, high-level description of the user's need.
- c.To establish the specific, testable conditions for completing the work.
- d.To collaboratively discuss and clarify the detailed requirements of the story.Correct
Why? this is the answer
The Conversation stage is explicitly described as a collaborative discussion to explore details, scope, and context, where real requirements are uncovered. Option C describes the Confirmation stage, which defines the acceptance criteria as an output of the conversation.
Just read this? Test yourself on what you have been reading.
Read the original → agilealliance.org
- #agile
- #scrum
- #user stories
- #product management
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles