1. Independent
   1. No dependency with other stories so that it can be executed in any order & can be prioritized based on value to the organization
2. Negotiable
   1. User stories are functional requirements in business terms but they are not contractual agreements
   2. Details can be negotiated & modified in a dialogue between customer and dev team
3. Valuable
   1. Understanding value of a functionality is useful in prioritizing & delivering top features during initial iterations
   2. Value of user story captured insection
4. Estimatable
   1. Developers need to come up with time to complete each user story, so it should be estimatable
5. Small
   1. User story needs to be small enough so that it can be accommodated in an iteration
   2. Big user stories are called ‘Epics’ that may contain a 1) complex user story 2) compound (multiple) user story
   3. Epics can be divided into multiple smaller independent user stories
6. Testable
   1. User stories should contain information with which test cases can be generated without much confusion & decision of done can be arrived