The continuous delivery of business value by DevOps is enabled by reducing defects that cause loop backs and delays, by making testing take less time, and by decreasing the size of features that flow through the pipeline. Acceptance Test-Driven Development (ATDD) / Behavior Driven Development (BDD) helps with these aspects of software delivery. With ATDD/BDD, product owners, testers, and developers create tests that describe the desired behavior of the system. Defects can be discovered earlier in the development cycle. In this session, Ken Pugh introduces ATDD/BDD, explains how it works, and outlines the different roles that team members play in the process.
Ken Pugh helps companies evolve into lean-agile organizations through training and coaching. His interests focus on collaborating on requirements, delivering business value, and using lean principles to deliver high quality quickly. His seventh book Lean-Agile Acceptance Test-Driven Development: Better Software Through Collaboration addresses these issues. As a SAFe SPC4, he emphasizes building in quality with Acceptance Test-Driven Development (ATDD) / Behavior Driven
6:00 - 6:30: Arrivals and Networking
6:30 - 7:30: Presentation and Q & A