What are the three attributes of an effective User Story?

• A. Card, Conversation, Confirmation
• B. Card, Consensus, Completion
• C. Contract, Collaboration, Commitment
• D. Context, Change, Clarity

Answer: (A)

The main concept being tested is that an effective User Story rests on three elements known as the Three Cs: Card, Conversation, Confirmation. The Card is the lightweight, visible artifact in the backlog that captures the gist of the request in a concise form. The Conversation is the ongoing dialogue between the team and stakeholders to explore details, refine scope, and align understanding as more is learned. The Confirmation provides the acceptance criteria or testable conditions that show when the story is done and functioning as intended.

For example, a Card might state a simple user need, while the Conversation fleshes out how the feature should behave, what constraints exist, and any edge cases. The Confirmation then defines exact criteria the team can validate—such as specific acceptance tests and performance expectations—so there’s a clear, shared target for done.

Other option phrasings don’t align with this practical trio because they don’t emphasize the essential, testable nature of a story (Confirmation) and the collaborative, evolving dialogue (Conversation) that typically accompanies backlog work, nor do they reflect the lightweight, portable artifact (Card) used to communicate intent.