We know that DevOps is a culture, a subset in Agile, where developers, other IT professionals and QA team work together, to build the product/service. This DevOps means actually an increased level of communication and collaboration between these people. What about BDD?
Well, BDD is even more than this. In BDD, beyond these professionals, even the non-IT stakeholders are committed to the product/service success. They can be involved in writing the features (Gherkin files), since these are in plain English. From my experience, at some point in time they would even enjoy this activity, when realizing its beauty: "Wow, I can write on my phone the product specifications, even when I travel. This is a cool thing!"
One of the problems I had was to respect the ubiquitous language everywhere, in order for the Jenkins server to correctly capture them.
Another problem I faced, but only in the beginning phase, was that... actually development teams do NOT love too much BDD, due to its nature apparently non-technical. But this is only when the project has began, for a couple of days/weeks.
So, this is the reason why I stated that BDD is more than DevOps: involved stakeholders. BDD is even more than TDD, on another perspective of things: the requirements and development approaches.
I worked with these sets of methodologies for a couple of years and I do recommend you to take a look over them, as part of your next big step. Enjoy!
Keep up to date