Two recent conversations I've had, leave me with questions about my
assumptions in how long it takes to really learn TDD and the short term
effects on productivity.

Ideally I would like pointers to peer review studies (I seem to remember a
few kicking around at Agile 2007, but can't find them now). Failing that
anecdotal would a be good start.

1) How long does it take to get a developer back to where they were before
in terms of productivity?
2) To become really productive? I.E. more so than they were before.

In both cases it can be assumed the developers are working as part of
supportive agile, have had training, access to books and ongoing coding
dojos (http://www.notesfromatooluser.com/2008/10/tdd-randori-workshop.html).
Effectively with everything put in place so they can succeed.

3) What is the effect on their productivity during the learning period?
Guesstimates will be fine here. In this case the point is to communicate
with management and make clear what effects the adoption of TDD will have in
the short term. Yes of course will emphasize reduction in complexity and
therefore the improved quality.

Cheers
Mark Levison

Blog: http://www.notesfromatooluser.com/
Recent Entries: Agile/Scrum Smells:
http://www.notesfromatooluser.com/2008/06/agilescrum-smells.html
Agile Games for Making Retrospectives Interesting:
http://www.notesfromatooluser.com/2008/10/agile-games-for-making-retrospectives-\
interesting.html


[Non-text portions of this message have been removed]