What is the difference between User Stories and Use case scenario , purpose-wise ?
What is the difference between User Stories and Use case scenario , purpose-wise ?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What is the difference between User Stories and Use case scenario , purpose-wise ?
Use Cases are more like a contract while Use Stories are a planning tool. Consequently, Use Cases usually outlive User Stories since they (should) serve as documentation that concretely reflects the built system.
User stories are written by the customer/stakeholder/client/user. User stories aren’t very detailed and are relatively open to interpretation.
Use cases are more formal in structure and are often written by a someone on the team – requirements engineer/product manager. They are often more detailed, breaking down an interaction into individual steps, and clearly identifying pre-conditions and post-conditions such as failure conditions and success conditions.
While one Use Case can cover many scenarios – success and failure; validation errors; sub use-cases and extensions – a User Story is more limited in scope, usually describing a single scenario.
See also User_story#Comparing_with_use_cases on Wikipedia, as well as the chapter “What Use Cases are Not” in the book User Stories Applied.
Lastly, according to Allistair Cockburn…