There is an eXtreme Programming revival rising wave in the wake of the Software Craftsmanship tide. I do think this is great news, as coding practices and tools were put in a closet by most of the firms that went Agile the Scrum way. But, XP is not Scrum + Software Craftmanship, this simple arithmetic does not reflect the specific attributes of those ideas.
I do think that XP is the best project methodology bar none, assuming that:
- you really have an available user
- you will actually put your deliverables in production
- the project can be executed by 5-7 experienced developers
Looking at them, those criteria are success factors for many projects, whatever the methodology. Nonetheless, those are pretty restricting constraints; but the further you are from this ideal setup, the more likely you will encounter issues during the project.
Why do I mention that? Because despite all the love I have for XP, or maybe because of that, I understand its limitations. As the saying goes: with great powers come great responsibilities.
So use XP responsibly.
Don’t expect it to scale, nor to tolerate weaker environment/sponsorship.
Or even better, find and try ways to adapt WP practices for a different environment, and please, share your findings.