Those of us who come from consulting know how big companies work. They are usually synonymous with tedious processes, very long times and suffer greatly in deliveries watching the dead-line to come closer and closer. I guess BDD can help a lot, actlually, BDD is a communication framework.
Of course, the question is: “if the agile methodologies have long existed and their effectiveness has already been proven … why do not use agile instead ? …”
There are several reasons, let’s look at some:
Firstly, agile works very well on small computers and above all if they are geared to develop. Outside of the developer ecosystem, people do not understand why they have to “split” projects into smaller, more manageable, deliverables. A manager or product manager, wants his functionality (all) finished.
Then there is the possibility of making mistakes. The traditional corporate culture, it prefers that the teams on the verge of arriving at the dead-line are weekends working “is being remedied”. It seems that if there is someone working late, everything is done … and if it does not come with all the expected functionalities, the project fails, most of the times is a matter of how we communicate the functionalities…
Although it seems risky … I think BDD can help solve this problem.
How can BDD help to communicate the product
BDD is a “language” that can at last help the understanding of what is asked, and yes, that’s communication, or in other words: that’s to explain our product with more detail in a language that all the roles involves can understand .
Give a try to know more about about BDD if you’re not a developer but a person involved in any of the process. Does not matter if you’re not developer, BDD is for everyone !
If you want to know more, there are tones of information about BDD on the internet.
And… for those who are developers and thinks… “yes, but I prefer TDD“, just a thing… BDD can be together with TDD. You can take the best from both worlds.