Thanks James.

Upper management actually asked me to share my TDD experience as well & so I just published an article internally to our Embedded Software newsletter describing how TDD helped my project. Here's the summary from that article (I think the dates really say it all):

My doubts that TDD could be used for an embedded application with an emphasis on external peripherals have been eliminated, and I have found the time invested in writing tests and mocks to be well worth it.

I find it compelling that

1. I required only 4 days of actual hardware testing before achieving my integration goal and that goal came essentially 2 months ahead of schedule.
2. For the past 5 months, since May, I have not used the in-system Debugger at all and instead rely on TDD to minimize the introduction of bugs in the first place.

Based on my experience, I found TDD to be a positive feedback exercise – passing my first tests & catching bugs immediately, encouraged me to write more tests, which lead to more successful results until I now have a high level of code coverage and a handy set of regression tests. (And since I wasn’t frantically debugging in the lab, I had enough time to write this article!)

Thanks, Name Withheld

The course was excellent. We would have had a much more difficult time doing this on our own. We still have a lot of work to do but this is an excellent start.

Paul Kirkley
Sr. Manager, Embedded Software
Harmony Remote Controls, Logitech Canada Inc.

The [agile start up] workshop was everything I needed it to be. We will launch this process immediately.

Vann Hasty Director of Engineering Motorola, Inc.

I was skeptical of TDD and had the concern that it would slow development down, but now I am sold 100% on TDD. Thanks again, the TDD training and your balanced look at agile / scrum was greatly appreciated!

Gareth Pennington Software Engineer Logitech, Inc.

Five months after their training...

We're doing very well with Agile and TDD. I can't even imagine going back to the old ways! The Agile/TDD process is very satisfying as we show accomplishments after each iteration (with fully tested stories and test automation included!). I'm so happy that I don't have to create a giant Microsoft Project schedule that spans a year of effort only to see it fall apart a couple of months into the project. I will always use the Agile/TDD process, and if I move to a new company (ya never know, it could happen), I'll make sure they use Agile/TDD and call you in for training.

Don Joslyn Software Engineering Manager Motorola, Inc.