Before you start Extreme Programming Builder AU columnist Steve Hayes offers tips on how to plan for an Extreme Programming (XP) project. Written by Steve Hayes, Contributor June 11, 2004, 12:15 a ...

When a development team decides to migrate to extreme programming (XP), the natural tendency is to focus on the programming practices, including unit testing, continuous integration, refactoring ...

Extreme programming (XP) is a software development approach built around rapid iterations, an emphasis on code writing and working closely with end users to achieve business results. The 12 basic ...

Extreme programming (XP) is a software development methodology that makes coding the primary activity. By promoting values such as simplicity and feedback, XP allows Java programmers to ...

Part of planning for an Extreme Programming (XP) project is deciding what content goes into specific iterations. A tool called the Planning Game can help.

For the last five years, a software development methodology called Extreme Programming (XP) has been receiving more attention. It is either admired or condemned from a multitude of sources.

Alrite, this time I am going to discuss Scrum and eXtreme Programming (XP). I would like to discuss Scrum and XP this time because I often get a question “When should I use Scrum or XP?”.

XP is also gaining popularity at universities on this side of the pond. Courses about the technique have begun cropping up in computer science curricula in the U.K.

Most of us realize that adopting Extreme Programming (XP) techniques has a big impact on application development. But what about testing? To answer this question, Lisa Crispin and Tip House have ...

Later this year Addison-Wesley will publish the first two XP books— Extreme Programming: Embracing Change, which is my XP manifesto, and Extreme Programming: Playing to Win, which is a more ...