Are User Stories mandatory in Scrum?

• A. They are mandatory in all cases
• B. They are optional but can be useful; they consist of Card, Conversation, Confirmation
• C. They must be used only for large-scale projects
• D. They should replace acceptance criteria entirely

Answer: (B)

User stories are not mandatory in Scrum. Scrum doesn’t require a specific backlog-item format, so teams can describe work in different ways. They’re optional but can be useful for focusing on user value and guiding conversations about details, acceptance, and validation. A common way to think about them is the Card, Conversation, and Confirmation pattern: a brief Card that captures the idea, ongoing Conversation with the team and stakeholders to flesh out requirements, and Confirmation in the form of acceptance criteria or tests that show the work is done. This approach helps ensure a shared understanding and testable outcomes, but it’s not a formal Scrum requirement. The key is keeping backlog items small, valuable, and verifiable, whatever format you choose.