The Art of Agile Development: Chapter 4: Adopting XP

Book cover for “The Art of Agile Development, Second Edition” by James Shore and Shane Warden. Published by O'Reilly. The cover has a large sticker on it that says “Early Release: Raw and Unedited.” The cover artwork shows a water glass containing a small sapling. The sapling has small green leaves. There is a goldfish in the glass.

Second Edition cover

The second edition of The Art of Agile Development is in development! Visit the Second Edition page for information about the open development process, how to get the Early Release, and more!

Full Text

The following text is excerpted from The Art of Agile Development by James Shore and Shane Warden, published by O'Reilly. Copyright © 2008 the authors. All rights reserved.

Adopting XP

"I can see how XP would work for IT projects, but product development is different." —a product development team

"I can see how XP would work for product development, but IT projects are different." —an in-house IT development team

Before adopting XP, you need to decide whether it's appropriate for your situation. Often, people's default reaction to hearing about XP is to say, "Well, of course that works for other teams, but it couldn't possibly work for us."

XP's applicability is based on organizations and people, not types of projects.

Question that assumption. I've helped a wide variety of teams adopt XP: 20-person teams and one-person teams; huge corporations and small startups; shrinkwrap, in-house, and outsourced software vendors; proprietary and open source developers. Through these experiences, I've learned that software teams are more similar than they are different. XP's applicability has far more to do with your organization and the people involved than the type of project you're working on.

If you liked this entry, check out my best writing and presentations, and consider subscribing to updates by email or RSS.