Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Use Cases are more like a <a href="http://en.wikipedia.org/wiki/Design_by_contract" rel="nofollow">contract</a> 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.</p> <p>User stories are written by the customer/stakeholder/client/user. User stories aren't very detailed and are relatively open to interpretation.</p> <p>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.</p> <p>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.</p> <p>See also <a href="https://en.wikipedia.org/wiki/User_story#Comparing_with_use_cases" rel="nofollow">User_story#Comparing_with_use_cases on Wikipedia</a>, as well as the chapter "What Use Cases are Not" in the book <a href="http://rads.stackoverflow.com/amzn/click/0321205685" rel="nofollow">User Stories Applied</a>.</p> <p>Lastly, <a href="http://alistair.cockburn.us/Stop+confusing+use+cases+and+user+stories" rel="nofollow">according to Allistair Cockburn...</a></p> <blockquote> <p>A user story is synonymous with “feature” as used in the 1990s, a marker for what is to be built, fine-grained enough to fit into modern iteration/sprint periods.</p> <p>A use case provides a contextual view of what is to be built, serving to bind the organization together, among other things.</p> </blockquote>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload