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.
In Questioning Extreme Programming, the author helps you examine and answer the following questions:
Is the cost of change really low?
Does XP allow proper testing?
Does XP make sense?
Is XP a return to the dark ages?
Can we adopt XP practices for other approaches?
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 informed decisions about Extreme Programming, and whether it is suitable for their organization. Readers will also be able to determine whether Extreme Programming is inappropriate for a particular project. The author challenges you to look past the hype and start asking the hard questions about how software is built. Discover for yourself.