group that meets kind of ad hoc, and they send email messages. The warning I'll give you is if you get involved with the Extreme Programming e-group, make sure that you do not ask for emails, because you will get 60 to 80 to 100 email messages per day from postings and threads. And these things will come on Saturdays and Sundays. I should have known something was strange when I signed up for the e-group back in December, early December, and the first message that was posted that came into my email box was one from somebody that I thought was very strange. I didn't think it even fit in with the whole context of the e-group on Extreme Programming. And what it was was a posting by somebody who said, "How do I handle email on vacation?" I thought that's odd--that doesn't seem like an Extreme Programming issue. But what they meant was, how do I handle the number of postings that will be in my mailbox when I get back from vacation and try and be able to go through this? Because if you're gone for two weeks, I can guarantee you, you probably have 400 messages. To get involved in the e-group, you would go to groups.yahoo.com---it used to be e-groups.com--and you would select Extreme Programming. You can use that in the search at the very top, you'll register, it's a free registration, and you can get involved and see the people, the interaction, and the changes that go on and the postings and the concerns of e-programmers everywhere.
Let me tell you a little bit about Extreme Programming, and we'll walk through that. And then we'll talk about the metrics that we can use, or maybe not use, especially in Extreme Programming.
XP is a lightweight, efficient, low-risk, flexible, predictable, scientific, and fun way to develop software. That's Kent Beck speaking. "Lightweight." What does that mean? Well, it's certainly not the old methodology-prone method of taking a look at things. And the fuller values are really communication. One thing that XP, or Extreme Programming, does is it puts at the heart of system development, the customer. The user. The people who are actually going to be working with the system, living, breathing, eating with it over the next several years. And it really forces the users to be part of the process, through the planning games, through stories. No longer can you have a user say, "I don't have time for that meeting." Users are actually in the same room as the programming team. Users work along with and build the requirements on an iterative basis. You can't escape. And if you don't like your users, you'll learn to like them. If your users don't like you, they'll learn to like you. Because communication's really the fundamental piece of Extreme Programming.
One of the other values is simplicity. And that comes through in refactoring, which is one of the major concepts. Taking a look at small, bite-sized pieces. Now, Extreme Programming is not for everyone. It is not for the huge, monolithic Department of Defense projects. It is really intended for programming teams of about three to ten people where your requirements are not solid. You're not stuck in a traditional environment. You're really a new type of company, where your system developments can work within some new ideas.
Feedback is also one of the values of XP, and courage. And that's a very interesting thing, because one of the things I've noticed about the XP e-group is that everybody seems to have a sense