Testing and QA with eXtreme Programming Practices

A Java development project team had proceeded to 25% completion using the traditional waterfall development method when they were suddenly asked to adopt eXtreme Programming (XP) practices and continue with the project. While XP may be good for management because it provides good visibility on the product, it may not be so good for developers who have to change their processes quickly. And it certainly presents a challenge to QA and testing, whose roles are not well defined. Sit in on this real-world example and you'll examine the challenges of XP and learn how you can overcome them.