Do you know this problem? New features should be developed, but communication with the customer is difficult. People talk past each other. Requirements are unclear. Finally, when the feature is implemented, it turns out the customer actually had a different requirement: “But we thought that does something completely different!”
One solution to this problem is to intensify communication between the customer and the development team and get feedback as soon as possible. An agile process model that focuses on this is Behavior Driven Development (BDD).
BDD focuses on the behavior of the user and attempts to establish consistency between requirements, implementation, and testing – a common understanding. For this purpose, examples are specified, so-called scenarios, which describe the behavior. This is often done during “3 Amigos Sessions”, in which business, developers, and QA work together.