Ambysoft logo

Test Driven Development (TDD) Survey Results: October 2008

Follow @scottwambler on Twitter!

Perfect Software This survey was performed the second week of October 2008 and there was 121 respondents. The survey was announced on the Extreme Programming (XP) and Test-Driven Development (TDD) mailing lists and summarized in Test-Driven Development (TDD): Reality over Rhetoric. The goal was to find out what agile developers were actually doing to compare it with what's being talked about.

The Survey Results

Some findings include:

Figure 1. Testing/Validation practices on agile teams.

Testing/Validation Practices

Figure 2. Requirements capture practices on agile teams.

Requirements Capture Practices

Figure 3. Design capture practices on agile teams.

Design Capture Practices



Survey questions

The Survey Questions (70 K)

Survey Data File

Raw Data (141 K)

Survey Presentation

Summary Presentation (174)

What You May Do With This Information

You may use this data as you see fit, but may not sell it in whole or in part. You may publish summaries of the findings, but if you do so you must reference the survey accordingly (include the name and the URL to this page). Feel free to contact me with questions. Better yet, if you publish, please let me know so I can link to your work.

Links to Other Articles/Surveys

  1. My other surveys

Why Share This Much Information?

I'm sharing the results, and in particular the source data, of my surveys for several reasons:

  1. Other people can do a much better job of analysis than I can. If they publish online, I am more than happy to include links to their articles/papers.
  2. Once I've published my column summarizing the data in DDJ, I really don't have any reason not to share the information.
  3. Too many traditionalists out there like to use the "where's the proof" question as an excuse not to adopt agile techniques. By providing some evidence that a wide range of organizations seem to be adopting these techniques maybe we can get them to rethink things a bit.
  4. I think that it's a good thing to do and I invite others to do the same.

Suggested Reading

How to Measure Anything This is an eye-opening book for anyone who is trying to understand how to measure concepts, such as developer productivity levels for example, which are often perceived as difficult to measure. If you choose to think outside of the metrics box for a bit you'll quickly realize that you can easily measure information which is critical to your decision making process.