Training: "Behaviour-driven development: writing software that matters"

Track: Tutorial

Time: Tuesday 13:00 - 16:00

Location: Rutherford Room


Behavior-driven development (BDD) is an evolution of the ideas behind agile software delivery. With its roots in test-driven development, domain-driven design, and automated acceptance testing, BDD focuses on the ways an application is expected to work - its behaviour. By constantly reflecting on the varied points of view of different stakeholders, BDD helps ensure that product owners and the development team are in sync on what is really needed and what to work on next.

In this highly-interactive session, Dan North introduces the principles behind BDD and describes how it works in practice. He provides an overview of the methodology of BDD: understanding your domain and who your stakeholders are, identifying and exploring requirements, automating acceptance criteria, and delivering working and tested software. Dan then looks at the nature of change and describes how to implement BDD in different contexts, including applying it to an in-flight project, managing distributed or large-scale development, and working with legacy systems. Dan encourages both experienced and novice agile managers and practitioners to join this session and bring with them their current challenges—and war stories.
Let me know if there's anything else you need.

Dan North, ThoughtWorks

 Dan  North Dan is a principal consultant with ThoughtWorks, where he writes software and coaches teams in agile and lean methods. He believes in putting people first and writing simple, pragmatic software. He believes that most problems that teams face are about communication, and all the others are too. This is why he puts so much emphasis on "getting the words right", and why he is so passionate about behaviour-driven development, communication and how people learn. He has been working in the IT industry since he graduated in 1991, and he occasionally blogs at