Test-Driven Development in the Larger Context: TDD & ATDD PMIs Disciplined Agile

Scott L. Bain
Senior Technical Trainer at PMI

"Test-Driven Development" was originally suggested by Ward Cunningham in the mid 1900's as a way for developers to generate code from unit tests. In the ensuing years it has also been suggested that organizations can drive requirements into development by writing acceptance tests to guide the process. Which of these should we call "TDD"? Which, if either, is more important, or should take precedence in terms of our attention and allocation of resources? Should we do them both? can they work together? How does ether relate to traditional testing?

This presentation will clarify the relationship between these two processes, how they are different, how they are the same, and most importantly how they can work together synergistically. We will demonstrate how TDD can strengthen any agile process. Along the way you will learn why you should become "test driven", what that means, and a powerful way to do it.

TDD is a very powerful paradigm for software development from business prioritization to requirements analysis through product design to working code. Join us and learn how it works, and where you fit into the process.

If you would like to be a future speaker for Agile Boulder, please use this Submission Form.