What we learned from TDD (besides T and D)

Abstract:
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.
an experienced software developer, IT manager, agilist, and entrepreneur with 25 years of experience. I have led teams of 5-15 at most companies I've been involved with. I can't say I've ever had a cushy position with nothing keeping me up at night either.

Rob Nickolaus Bio:
I've been fortunate to help organize the Lincoln Agile Community. Agile is my passion. I get how it can transform how we approach problems both from the technical and business perspective. It has been a game changer for me.

With development experience spanning a couple of decades, I've been exposed to C#, SQL Server, ASP.NET, VB.NET, as well as a multitude of other languages/applications all the way back to C/C++, FORTRAN, and assembly. I have spent considerable time in marketing and analytical applications including data warehouses and business intelligence apps. My current projects are mostly ERP, operational and web-based systems.