Recap In a previous article from series, we discussed a problem space with some hypothesis which Mark was going to solve by developing a great mobile app. We did it to help Mark to understand how the development process should look like and how to avoid problems as Mark had. You can read about the whole situation in PART 1 and in PART 2.
A better understanding of the client's needs
Requirements created at the beginning of work with the client in the BDD methodology are saved using the Gherkin language. Such a record is unambiguous, transparent and most importantly - easy to understand for all interested parties. Requirements in Gherkin have a characteristic syntax: functionalities are described through scenarios. Each functionality described by means of scenarios fulfills the client's business goal.