BDD Toolbox is an ongoing series of posts in which I’ll give you tools to do Behavior Driven Development well. Today we’ll take a look at Outcome Questioning – a tool to help ensure all relevant details are captured in your scenarios.  I’ve talked in the past about Behavior Driven Development and how I believe …

BDD Toolbox: Outcome Questioning Read More »

  In a previous post I wrote about how Jobs to be Done theory can be used to develop a clear and powerful mobile strategy. But once you have this mobile strategy in place, and have developed your stories, how do you then execute BDD well in an Agile environment? Going from a waterfall, fixed-price …

How to Do BDD and Agile Well for Your Mobile App Project Read More »

AT&T takes back their tantrum (and let us never speak of it again) One worry in the massively complicated, “if you don’t pick the right side you’re a bad person and should feel bad” Net Neutrality debate is the idea that without any financial incentive (that is, without the ability to charge content creators extra …

AT&T’s tantrum, Apple’s stumble, and Shazam’s BDD Read More »

Mobile app development needs to move fast, which means using Agile and Agile user stories.  Agile user stories typically follow the following format: As a __, I want to __, so that __. User stories are typically written by the Product Owner. In many cases, developers and QA resources are specifically excluded from this process. …

How a Cucumber Helps Your Three Amigos Speak Pidgin Read More »

Choosing the right level of concrete vs. abstract will help you derive the most value from Cucumber and BDD. I recently attended an amazing Cucumber workshop. During the training Aslak Hellesoy, the inventor of Cucumber, used a simple exercise to encourage people to make their examples more concrete. He would ask for someone to name …

BDD/Cucumber Basics: Make Your Business Rules Concrete; Leave Your Implementation Details Abstract Read More »