With the increasing pervasiveness of agile software development methods such as Scrum, new challenges have emerged in the holistic software development process encompassing requirements engineering, implementation and testing. The boundaries of these traditionally sepa-rated disciplines are becoming increasingly blurred. Therefore new pro-cesses need to be established to drive successful software development. Behaviour-Driven Development (BDD) is one particular methodology which can drive success by providing a common language for all involved disciplines and stakeholders. All collaborators work with a common understanding of the subject matter and concrete requirements of the software being developed. Software requirements are specified both in a general form as well as based on concrete examples by using a domain-specific language and predefined syntax. Such requirements can be elicited in cooperation with QA to create acceptance tests early on in the overall development process which furthermore are fully integrated with the requirements. Such scenarios are incrementally implemented by development during the course of which they are also enriched with automated tests, hence creating a living software specification document which is ensured to remain up-to-date even in the face of future changes to the specification.