Good news! Here’s video 11 in our series designed to jump-start your understanding of the core principles and practices of Agile Software Engineering (ASE). In this installment, one of our Lean-Agile thought leaders, Ken Pugh, talks about test-driven design.

As we learned in video seven, Behavior-Driven Development (BDD) is about the triad of customer, developer, and tester writing story tests from a point of view external to the application. Test-Driven Development (TDD) is about figuring out from those stories what internal entities are needed, then creating the internal code tests and components required to pass them.

Ken compares the timelines of the BDD and TDD test cycles and lays out the TDD cycle steps. Next, he describes an example story and a scenario for it to show how tests should be developed starting with the simplest, smallest ones and expanding outward.

Watch the implementing with quality video here.

Join us again soon for the final video in our series, “The Rest of the Story,” in which Ken shares insights into other Agile software engineering practices.

Here’s the previous video in our series, building systems with design quality.

Learn more about the Agile Software Engineering course here.   

Stay SAFe,

—Harry