What the ... is BDD!

1. Discovery
   1. Really understand it
      1. e.g. Example Mapping (structured conversation technique)
      2. Concrete Examples
      3. Sometimes called ‘three amigos’
      4. Colour coding of cards - e.g. red cards for deferring if the answer can’t be answered right then
      5. 6 people max in the room (5 or 6 is great)
      6. Suggestion: 30mins in the calendar every day after the standup
      7. The closer to the actual work starting the better
      8. One story per meeting (i.e. per day)
   2. 
2. Formulation
   1. Capture it in a format that is shareable and broadly understandable
      1. e.g. Gherkin
      2. BRIEF (Brief, < 5 lines ideally)
         1. B - Business Readable (can include technical terms - IF the consumers are technical, e.g. an API product)
         2. R - Read Data - examples should be real data (e.g. VAT calculation should be actual calculation for the nominated item)
         3. I - Intention Revealing - don’t focus on implementation (i.e. ‘click this button’) but on the activity/outcome
         4. E - Essential - only include the elements essential to communicate point. Anything incidental should be removed. If important it can be in another spec
         5. F - Focused
      3. Recommend a pair independently works on prepping the spec based on the examples
      4. After writing specs, share for review with others from the example mapping session (e.g. Product owner to review)
      5. The review is the opportunity to find out how the people who learnt something in the session actually understood what they learnt and if it aligns with the intention
      6. To ensure it’s being reviewed - include ‘incorrect stories’ to find out if they get caught? (Only half joking…)
      7. Timescale... longer than you'd think...
   2. 
3. Automation
   1. Drive a test
      1. Cucumber family of tools understand Gherkin (Specflow, Behat, Good)