Extreme Programming (XP) has been the subject of heated debate since it burst on to the programming scene in 1998. Understandably so, because it contradicts many traditional software development beliefs. We’ve heard success stories about sweeping changes made to organizations, and all of the good that has come as a result of them. We’ve read books about how this approach can work for our teams. But what about the times when it isn’t appropriate? There are certainly instances when making the leap to XP could sacrifice a whole project. What’s missing from all of this rhetoric? Witness Pete McBreen, software craftsman, examine the issue from both sides. In Questioning Extreme Programming, the author helps you answer such Is the cost of change really low? Does XP do proper testing? Does XP make sense? Is XP a return to the dark ages? What can other approaches learn from XP? Do you need process improvement or process change ? Why are developers so zealous about adopting XP? Is XP suitable for your projects? What is the next step after Extreme Programming? After reading this thought-provoking book, software developers can make an informed decision about Extreme Programming, and whether it is suitable for their organization. Readers will also be able to determine whether Extreme Programming is inappropriate for their project. Discover for yourself. Look past the hype, and start asking the hard questions about how software is built.