testing, abandoning the solid requirements process, and really spend all our time coding in XP. So once you get the tests done, oh everybody just sits down and hacks. That's not the case at all. Actually, what happens is the analysis and design in XP lifecycle takes up 40% to 65% of the time. Coding is a mere 5%. And testing and support is actually 30% to 55%.
Carol: Yes. Is that my guest?
Caller: No, sorry. Not your guest. Just an interested caller.
Carol: Oh, okay. I'll just finish this thought, and then I'll have my caller come on. So XP really focuses on doing a good job of analysis and design. Coding, once we have the requirements right. And then doing the testing and support and building the system iteratively. And caller, you're on the air. Hello? Okay, that's fine. We'll go to break and we'll be back with more of Quality Plus Technologies e-Talk! with Carol Dekkers as soon as we get back from this short break.
Hi, welcome back to Quality Plus e-Talk! This week we're having what I would call the essence of a virtual interview. This is...when we're in computers, I know that technology is never fool-proof, and people are never fool-proof, and one of the things that I've realized is that today we're really taking an interview to the "extreme," and we're having a virtual interview. So I guess that's something a little bit interesting, and as a host, it's very challenging. It's something that I have to learn, gee, what if my guests don't phone in? So we're going to talk about Kent Beck and Ward Cunningham, rather than with them, but that's okay. And I have a caller. Danny?
Carol: You had a question for me.
Caller: Right. I've been reading some about Extreme Programming, and it strikes me that the different elements of it don't seem to be really closely related. And some of them are more controversial than others. So you'll talk about the pair programming. I personally think that's a good idea. But some people will kind of shy away from that, the idea of putting everybody in a room together with no walls and all of that, you know, certainly goes against the idea of peopleware and giving them their own office. So some people might want to reject some parts of it. And is that okay? Can you pick up some pieces of it and call that Extreme Programming or call that a good thing to do?
Carol: Well, one of the things I think that's a very good question. And I think that with backgrounds of engineers, computer scientists, by and large, and then two-year degrees, and we've really got a mix in software of all different backgrounds. We have the traditional structured math majors, engineers, computer scientists, software engineers. And then we have the liberal arts people who have backgrounds in French, in music, and all sorts of things. And they're all thrown together in programming. And I think a lot of times what happens is people don't want to change a lot. The older programmers really don't want to embrace XP. Some of them do, because of what they think XP is. I've heard from one of my colleagues who's doing a review of Kent Beck's book, he had heard and read on the Internet a lot about how XP is just anarchy. Where you just kind of do whatever you want. And I think that really fits into what you're saying, Danny, that it kinds of looks