During our journey to implement Test Driven Design, we chose to use TDD katas to teach the team in small, bite-sized chunks. Along the way, we learned a great deal about unit tests and how they can drive design. However, we also learned some valuable team skills and highlighted some misconceptions we had been carrying.
Come learn how TDD can highlight just how far away you team members may be from each other (code/design-wise), what causes friction on the team, how people approach problems, and what can be taught by code examinations. We'll show how TDD can highlight and cross-pollinate best practices, coding styles, modern language element usage, and even cause friction for those who may prefer to overengineer systems (and what you can do to smooth that over). Along the way, we'll cover just what exactly is a TDD kata and how you can add it to your toolbox.