Re:Warning Signs that Agile Is Declining
by berntb on Wednesday January 18, 2012 @01:46AM
(#3478368)
Thanks. Automated testing, yes. But e.g. TDD?
Re:Warning Signs that Agile Is Declining
by Silhouette on Wednesday January 18, 2012 @04:55AM
(#3478855)
I'm not claiming TDD as something widespread before Agile. I'm claiming TDD as something unproven that the Agile consultants started mixing in later. (Please see the list in my second post to this thread.)
Re:Warning Signs that Agile Is Declining
by wpietri on Wednesday January 18, 2012 @09:23PM
(#3482929)
For the third time: you are incorrect about the history. Test-first development was created by working programmers as part of Extreme Programming before the term "Agile" even existed.
Re:Warning Signs that Agile Is Declining
by Silhouette on Thursday January 19, 2012 @12:51AM
(#3483371)
I'm not necessarily disputing that, though I note that you have changed from TDD to merely test-first development, which I don't think is the same thing.
My point is that TDD, like several of the other practices in XP that do seem to have originated with those people during that time period, is to this day not proven as any better practice than the alternatives.
I didn't have anything specific in mind; I'm going by my own experience, discussions with past colleagues, and conferences over the years more than anything. That said, it's not hard to turn up examples with a few minutes looking through my bookshelf and Google Scholar.
For automated testing, just stick search terms like "automated software testing" into Scholar and set the latest year to, say, 2000. You'll turn up dozens of papers going back decades that talk about techniques similar to what we would call unit testing today.
Continuous integration is another obvious one. The likes of Grady Booch were writing about the advantages of frequent integration builds by the early '90s. The term "continuous integration" appears in Object-Oriented Analysis and Design with Applications (1993), for example.
The prior existence of refactoring techniques is kind of obvious, as people had been discussing simple transformations like moving functions and data up and down a class hierarchy since the dawn of OOP. If you want a specific citation, Design Patterns (1995) mentions the specific term "refactoring" a few times, in turn citing academic papers on the subject cowritten by one of the authors as early as 1990, around a decade before Fowler's book and several years before Beck coined the term according to some Agile advocacy.
That's all I've got time for now, but I'm sure you could find eqally authoritative sources for the other things I talked about if you genuinely want to know.