Extreme Programming (XP) has been the subject of heated debate since its arrival on the programming scene in 1998—understandably so, as it contradicts many traditional software development beliefs. We've heard success stories about sweeping changes made to organizations as a result of XP. We've read books about how this approach can work for our teams. However, are there times when XP isn't appropriate? There are certainly instances when making the leap to XP could potentially jeopardize a whole project. What's missing from all of this rhetoric? Witness Pete McBreen, software craftsman, examine the issue from both sides.