XP is nothing new
December 31, 2009 · 7 Comments
When the subject of Agile Methods and Extreme Programming come up in conversation, I find a lot of people tend to dismiss it as some sort of "new fad". I'm on the XP mailing list (on Yahoo! Groups) and someone just posted today that the first message was posted ten years ago (December 31st, 1999). Kent Beck's book "Extreme Programming Explained" was published in October 1999 after he had been refining the XP techniques for three years (on the Chrysler Comprehensive Compensation payroll system). Many of the techniques in XP predate that substantially: test first development - commonly referred to as TDD (Test-Driven Development) - can be traced to NASA's "Project Mercury" in the early 1960's; refactoring, incremental designs, and other techniques that are considered part of XP were documented in a book published in 1984 ("Thinking Forth" by Leo Brodie).
No, XP is nothing new, it's just become increasingly popular as more people try it and find benefit in its practices.
Over the last three or four years I've been adopting a variety of Agile Methods on projects to see whether they help with some of the typical problems we all run into these days: tight deadlines, vague and changing requirements, poor estimates, lack of visibility into progress. I've been pretty pleased with the results. Agile Methods aren't a panacea: being agile doesn't make you a better developer (or project manager) overnight but it does help give you a better handle on the status of a project, it lets you maintain measurable forward movement, the focus on testing increases your confidence in "completion" as well as providing a safety net while you're making improvements in the code structure.
So perhaps before dismissing XP and Agile as "some new fad", you might make it one of your resolutions for 2010 to try these decade(s) old approaches?
BTW, some of those other "new fads" that you think are challenging the CF establishment... you know, new fangled stuff like Ruby and Python? Just remember those languages pre-date CFML! Happy New Year! :)
Tags: programming

7 responses so far ↓
1 Mark Lapasa // Dec 31, 2009 at 11:04 PM
2 Bob Silverberg // Jan 1, 2010 at 8:11 AM
3 TJ Downes // Jan 2, 2010 at 8:05 AM
I agree with your thoughts on Agile. Agile is a process, and regardless of which flavor you choose, the success is dependent upon following the process. I've seen far too many people say they were doing Agile when, in reality, what they do is waterfall project management with more meetings. TO be successful there are definitely things that need to be followed to see the gains offered by any Agile process.
I've found a decent tool for planning that I am messing around with, TargetProcess. There's a free community edition that supports 5 users that will get you started. The downside is that it requires IIS/.NET. They do have as hosted version, but aside from the trial it is not free. http://www.targetprocess.com
4 Sean Corfield // Jan 3, 2010 at 4:34 PM
"Are there any [books] that you'd particularly recommend?"
I am a little ashamed to admit that I'm not really much of a book reader. I pick up most stuff from either general online reading or from teams I work with over the years.
5 Simon Horwith // Jan 3, 2010 at 8:07 PM
6 Sean Corfield // Jan 3, 2010 at 11:30 PM
7 Matt b // Jan 4, 2010 at 3:35 AM
is a classic
Leave a Comment