# 3 C's of User Stories The 3 C's is a framework created by [[Ron Jeffries]] that describes the essential components of a user story in [[Extreme Programming (XP)]] and agile development: **Card**, **Conversation**, and **Confirmation**. The framework emphasizes that user stories are not detailed requirements documents but rather placeholders for conversations. ## The Three C's ### Card A brief written description of the story, traditionally on an index card. The physical limitation of a card forces brevity and ensures the story remains a reminder to have a conversation rather than a complete specification. **Example: ** > As a user, I want to reset my password so I can regain access to my account. ### Conversation The dialogue between developers, product owners, and stakeholders that fleshes out the details of the story. This is where the real requirements emerge—through discussion, questions, and clarification. The card is just an invitation to this conversation. ### Confirmation The acceptance criteria or tests that confirm when the story is complete. These are often written as specific conditions that must be met, answering "How will we know when this is done?" **Example criteria:** - User receives reset email within 1 minute - Reset link expires after 24 hours - Password must meet security requirements ## Why It Matters The 3 C's framework shifts focus from written documentation to human communication. Stories are deliberately incomplete; they require conversation to be understood, preventing the false precision of detailed upfront specifications. ## References - https://ronjeffries.com/xprog/articles/expcardconversationconfirmation/ ## Related - [[Ron Jeffries]] - [[Extreme Programming (XP)]] - [[Agile Manifesto]] - [[Kent Beck]]