Measuring the Effect of TDD (2007) by Keith Braithwaite http://www.keithbraithwaite.demon.co.uk/professional/presentations/2007/agile/TDD.pdf
These are the slides from a talk given at Agile 2007, investigating the relationship between Cyclomatic Complexity and Test Driven Development for a number of projects. See http://peripateticaxiom.blogspot.com/search/label/test-first%20complexity for some more information on this topic. I hope that Keith will write a paper summarizing his findings to date.
An Initial Investigation of Test-Driven Development in Industry (2003) Boby George, Laurie Williams (North Carolina State University) http://collaboration.csc.ncsu.edu/laurie/Papers/TDDpaperv8.pdf
- A set of structured experiments with 24 professional pair programmers. Found that the TDD developers produced higher quality code, passing 18% more functional black box test cases than the waterfall-like developers, though taking 16% more time for development. The programmers which followed a waterfall-like process often did not write the required automated test cases after completing their code.
Effects of Test-Driven Development: An Evaluation of Empirical Studies (2006) Philip Ritzkopf (Embedded Software Group) http://www-i11.informatik.rwth-aachen.de/fileadmin/user_upload/Redakteure/Vorlesungen/05winter/MethEmpSWTechn/Ritzkopf__Philip.pdf
- Summarizes one case study (Maximilien and Williams 2003) and four experiments (Muller and Hagner 2002, George and Williams 2003, Geras, Smith, Miller 2004, and Erdogmus, Morisio Torchiano 2005)
On the Sustained Use of a Test-Driven Development Practice at IBM (2007) Julio Cesar Sanchez (IBM), Laurie Williams (North Carolina State University), E. Michael Maximilien (IBM) http://www.agile2007.org/downloads/proceedings/006_On%20the%20Sustained%20Use_860.pdf
- A post hoc analysis of a large-scale Java development project at IBM spanning five years and 10 releases, in which TDD was used throughout.
Extracted from StudiesOfAgileEffectiveness