1. classic way
   1. As a <role or persona>, I can <goal/need&gt; so that <why>
   2. As a <particular class of user>, I want to <be able to perform/do something&gt; so that <I get some form of value or benefit>
      1. As a <type of user>, I want <some feature> so that <some reason>
         1. https://www.mountaingoatsoftware.com/agile/user-stories
         2. https://www.smartsheet.com/user-story-templates
2. BDD
   1. Scenario -> Given -> When -> Then
      1. https://www.targetprocess.com/blog/bdd-and-user-story-specification-examples/
      2. https://medium.com/@nic/writing-user-stories-with-gherkin-dda63461b1d2
3. Agile way
   1. description
   2. acceptance criteria
4. by David Evans
   1. In order to <why>, for <who>, we will <what>, whereas currently <now>
      1. https://twitter.com/DavidEvans66/status/730743246050168832?s=20
5. Job story
   1. When a <situation>, I want to <motivation> so I can <expected outcome>
      1. https://www.intercom.com/blog/using-job-stories-design-features-ui-ux/
      2. https://hbr.org/2016/09/know-your-customers-jobs-to-be-done?source=post_page---------------------------
6. I will be interesting
   1. About Story Mapping using 5W2H
      1. https://www.xmind.net/m/p3qe/
   2. Some notes about BDD
      1. https://www.xmind.net/m/9vqi/
   3. Using checklists for US informal review
      1. https://www.xmind.net/m/BS6v/
   4. A few notes about software requirements
      1. https://www.xmind.net/m/KJdm/