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.
Mark Levison has been helping Scrum teams and organizations with Agile, Scrum and Kanban style approaches since 2001. From certified scrum master training to custom Agile courses, he has helped well over 8,000 individuals, earning him respect and top rated reviews as one of the pioneers within the industry, as well as a raft of certifications from the ScrumAlliance. Mark has been a speaker at various Agile Conferences for more than 20 years, and is a published Scrum author with eBooks as well as articles on InfoQ.com, ScrumAlliance.org an AgileAlliance.org.
Your experience matches mine. Read more at Crouch, Touch, Pause…Engage
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?
It works in waves – you work with one groupdepartment 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.