title: Should design tasks be user stories?
body: <p>I'm trying to figure out when using user stories is appropriate. Always or not?</p>
  
  <p>For an example, think about a team starting to work on something from scratch, say a movie ticket reservation service. It's easy to come up with user stories for the functionality, like:
  "As an end-user I want to be able to browse the movies running in theater X" and so on.</p>
  
  <p>But before those can be implemented, the system needs to be designed: Architecture must be designed, database must be designed, technologies chosen for the GUI and business logic. </p>
  
  <p>How should these tasks appear in the backlog? Should they be user stories as well? If so, how do they comply with the INVEST mnemonic? They don't alone deliver anything for the end-user, but nevertheless they are needed before any feature can be implemented. </p>