TDD Adoption Strategies Article

January 8, 2009 in Software Development, TDD by Mark Levison

Eons ago I promised a blog posting on TDD Adoptions strategy. Well, the posting grew and grew and grew (can you tell I read a lot of kids books?) and along the way morphed into something bigger. In the end, I decided this article needed a wider audience, so I published it on InfoQ. Here’s the blurb:

Making TDD Stick: Problems and Solutions for Adopters

Teams in large organizations still struggle to adopt TDD. In this article Mark Levison shares problems he uncovered when he surveyed teams, and his own strategy to introduce TDD into an organization.

If you enjoyed this post, subscribe to my RSS Feed

3 Comments

January 12, 2009 at 1:26 pm | Carlton

Your experience matches mine. Read more at Crouch, Touch, Pause…Engage
January 12, 2009 at 1:27 pm | Mark Levison

I’ve just read your blog posting that is another interesting strategy my only question would be around how well does this scale. Can you handle 50 people this way? 200?
January 12, 2009 at 3:15 pm | Carlton

It works in waves – you work with one group\department at a time.

I have tried the one-day “This is TDD” approach and I would periodically get requests to come back. For the longest time I could not understand what was wrong and then I realized my approach was wrong. I was treating the situation like I was an external consultant, but forgot I was an internal consultant and had more flexibility on the schedule of the employees.