Changing the project workflow with behat

One can expect to see references to Behat framework in more technical tracks like DevOps or Coding and development. Test-driven development has become another buzzword, but is it enough for the project success to have someone in the team who knows a little bit of Gherkin?

We argue that the answer is no, and you have to change both project planning and issue flow (whatever project management software you use).

We want to explain suggested shift of roles, from perspectives of a ScrumMaster  and a developer