tezvyn:

The 3 Cs: Card, Conversation, Confirmation

AI-drafted, machine-checkedSource: agilealliance.orgintermediate

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.

Read the original → agilealliance.org

Get five bites like this every day.

Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.