Probably not many, but I don't think that is necessary. He just has to show us a convincing list of projects (e), and demonstrate how these projects improved with the introduction of TDD, WITHOUT blurring the line between TDD and unit testing. Not student assignments, but real world projects where real jobs, real money, real stakes are on the line. The problem here is that if TDD is as effective as the zealots and XP gurus claim it is, then the evidence for it should be overwhelming.

Edit: (e) Listing projects that are: 1. real (not just student, testing or open source projects); 2. large enough that real stakes are on the line (I want to see an example of a 2 MLOC system before and after TDD, not the 70 KLOC of Fitnesse) would make me pay attention. Then I want to see how TDD improved the state of the project (and that picture has to include things like productivity and cost analysis of test first testing everything). Then I want to see why the same results could not have been achieved with "test last" or "test whenever" unit testing. Then I would want to see an explanation for the rate of success other people have had without ever practising TDD - because if TDD is as effective as the zealots claim, and if the zealots make a living making those claims, then that explanation HAS to be there.