The document discusses learning customers' language by understanding their problems, asking questions, and listening to their stories. It recommends asking questions like "What problem are we trying to solve?" and "Why are we doing that right now?". It also suggests using personas, task matrices, mockups, and customer stories to understand needs from the customer perspective in a format of "As a [role] I need to [action] so that [happy result]". Behavior driven development and executable specifications are presented as ways to capture stories and test acceptance. Resources on SpecFlow, StoryQ and examples of personas are provided.

1. Learn Your Customers’ Language John Smith | Orlando, FL @onefloridacoder | onefloridacoder@live.com

2. The Problem

3. Answers Think Ahead Ask More Questions Take the Customer to Dinner

4. new Answers(); Don’t Think Ahead Sooner Ask Better Questions Look for Better Answers

5. Don’t Think Ahead Sooner Understand The Problems

6. Don’t Think Ahead Sooner Black and White

7. Ask Better Questions “What problem are we trying to solve?” - Scott Densmore “Why are we doing that right now?” - Z

8. Look for Better Answers Listen To Your Customers’ Stories Play The Ball Where It Lies

9. Customers’ Stories Personas Task Matrices

10. Mockups / Wire Frames

11. One Customer Story As a <role> I need to <action> So that <some happy result>

12. Another Story Version Given <some condition> When I <action> Then <some result happens>

13. Behavior Driven Development Demos(d => { d.SpecFlow(); d.StoryQ(); });

14. Behavior Driven Development Executable Specifications

15. Behavior Driven Development Executable Specifications Acceptance Testing

16. Questions

17. Resources SpecFlow https://github.com/techtalk/SpecFlow http://www.specflow.org/ StoryQ http://storyq.codeplex.com/ Personas http://www.rimakuprys.com/Personas_iTunes.pdf http://www.slideshare.net/lorielue/personas-in-product-design

18. Learn Your Customers’ Language John Smith | Orlando, FL @onefloridacoder | onefloridacoder@live.com