1. Why use them?
   1. Making Tacit Knowledge more explicit
   2. Ubiquitous Language
   3. Rapid feedback cycles through verbal, "face-to-face" interaction
   4. Encourage deferring details until really needed
   5. Units of planning and delivery
2. 3C Properties
   1. Card
   2. Conversation
   3. Confirmation
3. Acceptance Criteria
   1. Happy path
   2. What other circumstances?
   3. Which other assumptions?
   4. What can go wrong?
4. INVEST in good stories
   1. Independent
   2. Negotiable
   3. Valuable
   4. Estimatable
   5. Small
   6. Testable
5. Not to be mistaken with
   1. Contract
   2. Specification
   3. Use Case
   4. Technical tasks
6. Splitting Stories
   1. Along CRUD operations
   2. Along data boundaries
   3. Along operational boundaries
   4. Along cross-cutting concerns
   5. One vs. Many
      1. 1 item, many items
      2. Single user, multi-user
      3. One level, Multiple levels
   6. Main flow vs. Alternate flows
   7. Functional vs. Non-Functional aspects
   8. Manual vs. Automated
   9. Spike + implementation
7. Smells
   1. Stories that mandate implementation
   2. Stories with weak Goals
      1. Self-referencing Goal
      2. System Goals rather than user goals
   3. "Temporarily Untestable" stories
8. Books & Resources
9. Guidelines for good stories
   1. Start with Goal Stories
   2. Slice the cake
   3. Write Closed stories
   4. Identify general constraints separately
   5. Size the story to the horizon
   6. Keep the UI out as long as possible