This is a hands-on practical session about agile testing where participants split into groups and learn how to do story mapping and how to write Given-When-Then Behavior-Driven Development (BDD) tests.
This workshop by Jon Kern covers the use of Story Mapping and BDD-style techniques to break down feature requests for Agile Testing. Behavior-Driven Development is an Agile software methodology that enhances collaboration between developers, testers, and business stakeholders. It is used to define system behavior through concrete, plain-language examples (Given-When-Then). It bridges communication gaps by focusing on user-centric functionality and business outcomes, reducing waste and producing automated, “living” documentation.
Story mapping is an Agile technique that visualizes a user’s journey through a product by arranging user stories on a two-dimensional map. It organizes tasks chronologically (horizontal axis) to show the workflow, while prioritizing, detailing, or grouping functionalities (vertical axis) for release planning. This collaborative, user-centric approach provides a holistic view of the product, fostering a shared understanding and preventing feature-driven, disjointed development.
These two videos emphasize the importance of collaboration between Business, Dev, QA, UX, by lowering organizational boundaries, silos, and spheres of traditional organizational influence, command & control. The presenter explains how BDD starts, as a means of expressing requirements (defining what “done” looks like) and feeds into the actual development life cycle. Jon Kern explains why he insists that teams should use BDD and TDD with test automation.
Video producer: https://agile-serbia.rs/
Techniques like story mapping and Behavior-Driven Development are useful to involve all the Agile teams in software quality assurance.