of waterfowl. One of the most interesting things about Kent Beck is that he has been around what seems to be forever, but I know he's not that old. And when you pull up his name on the Internet, you will find Kent Back's name everywhere, along with the other two "extremos," which are kind of like the three tenors of the opera world. The three "extremos" are really Ron Jeffries, Ward Cunningham, and Kent Beck, who have been involved with object-oriented programming and Extreme Programming for a very long time.
Kent wrote a book called Extreme Programming Explained: Embrace Change. And that came out last year. And it has been a very, very insightful and actually a bible for many people who are looking at changing the way they develop software, changing some of the things that they know don't work, the traditional ways of building software. And Kent put those in his book, Extreme Programming Explained: Embrace Change, and we'll back to talk with Kent Beck after these short messages.
And we're back with Quality Plus e-Talk! I haven't yet heard from Kent Beck and Ward Cunningham. I'm not sure what's going on on the Oregon coast, but we're going to wait for them to phone in. Meanwhile, for anyone who's listening that doesn't know a lot about Extreme Programming, let me just bring you a little bit up to speed.
Extreme Programming, to a lot of people, they might look at that as being something similar to bungee jumping, or they have visions of people with laptops jumping off with bungee cords, or everybody's got piercings in the office, or something like that. But really, that's not the case in Extreme Programming at all. Well, a lot of people might say, you know, "extreme," that means taking risks. Extreme anything, if you take a look at extreme sports, the EXPN games, or the X-games or anything like that, it really means going to the edge, and really taking life-threatening risks. And XP couldn't be further from the truth.
XP really takes and minimizes risk by focusing on the things that work well and leveraging that. Let me give you a little bit of setting the scene for XP. Kent Beck in his Extreme Programming Explained book said risk is the basic problem, and I'll quote him: "Software development fails to deliver and fails to deliver value. This failure has huge economic and human impact. We need to find a new way to develop software." And that kind of sets the stage for what Extreme Programming takes a look at.
What kind of things are plaguing us? Well, we've got things like false features, we've got cancellations, we've got changes in business, we've got defect-prone software that's delivered, we've got in this Internet age especially, situations where we have customers who can kind of tell you what they need in their software, especially if it's Web-based software. But they can't tell you really what they need sometimes until after they've seen what they don't need. And we used to call that prototyping in software development. Now we've got the challenge of really kind of Internet seed development. It was explained to me in this type of manner, that typically what we do on large projects, is we will plan, we will plan kind of like AAA, the automobile association, will do TripTiks. If you want to go from where I live in Tampa to Jacksonville, for example, TripTiks will give you every stopping point, every light change, basically, that you go on I-75. And it's all planned out