1. WHY
    1. to support the production of products with the highest possible value for the customer
  2. WHO
    1. business analysts
    2. testers
    3. stakeholders
    4. Agile team
  3. WHERE
    1. During requirements elicitation
      1. A few notes about software requirements
        1. https://www.xmind.net/m/KJdm/
      2. Let's cook a new feature
        1. https://www.xmind.net/m/6HxCaW/
      3. Some formats for User Stories
        1. https://www.xmind.net/m/NJa52w/
      4. Some patterns for USs decomposition
        1. https://www.xmind.net/m/XxQwDp/
  4. WHAT
    1. Acceptance criteria are part of US/requirements
      1. US has been implemented as expected
      2. “what” to test
      3. Acceptance test cases
  5. WHEN
    1. ATDD
      1. produced collaboratively during requirements analysis by business analysts, product owners, testers and developers
    2. BDD
      1. requirements are defined in a ‘Given – When –Then’ format
        1. become the acceptance test cases and also serve as the basis for test automation
        2. use a pattern
          1. Given [a situation]
          2. When [an action on the system]
          3. Then [the expected result]
      2. Some notes about BDD
        1. https://www.xmind.net/m/9vqi/
  6. HOW
    1. writing Acceptance Criteria
      1. precise, measurable and concise
      2. do not include technical solution details
        1. What shall be achieved?
      3. address as quality characteristics as functional requirements
        1. Performance efficiency
        2. Compatibility
        3. Usability
          1. UX-testing. Let's think about mental models using 5W2H
          2. https://www.xmind.net/m/JM3d4u/
          3. Some notes about Hick’s law and Fitts's law for Testing
          4. https://www.xmind.net/m/kHez6g/
          5. Some notes about Accessibility Testing using 5W2H
          6. https://www.xmind.net/m/9dBuaX/
          7. Some notes about Visual Testing using 5W2H
          8. https://www.xmind.net/m/NYeNjC/
          9. Some notes about UX-testing
          10. https://www.xmind.net/m/MF9T/
        4. Reliability
        5. Security
        6. Maintainability
        7. Portability
    2. methods
      1. walkthroughs
        1. Use INVEST
      2. technical reviews
        1. Using checklists for US informal review
          1. https://www.xmind.net/m/BS6v/
      3. iteration planning
        1. Impact mapping for strategic planning
          1. https://www.xmind.net/m/VCsS9v/
        2. About Story Mapping using 5W2H
          1. https://www.xmind.net/m/p3qe/
        3. Discovery phase for your Team
          1. https://www.xmind.net/m/rZpAL5/
      4. Three Amigos
        1. About Three Amigos using 5W2H
          1. https://www.xmind.net/m/6M6t/
      5. Design Sprint
        1. Some notes about Google Ventures method and Design Sprint via 5W2H
          1. https://www.xmind.net/m/QLfvdG/
        2. Some notes about the Design Sprint
          1. https://www.xmind.net/m/GieRNn/
    3. Test Techniques for Acceptance Testing
      1. Business process-based testing, possibly combined with decision table testing, validates business processes and rules
      2. Experience-based testing
      3. Risk-based testing
      4. Model-based testing
        1. Model-based testing: using GraphWalker (offline)
          1. https://www.xmind.net/m/GiwQ/
      5. Exploratory Testing
        1. Exploratory Testing. How to Start
          1. https://www.xmind.net/m/U9bj/
    4. Business Process Modeling
      1. use BPMN and DMN notations for acceptance testing
  7. HOW MANY
    1. depends on your processes
    2. find balance