Extreme Programming (XP) was conceived and developed
to address the specific needs of software development
conducted by small teams in the face of vague and
changing requirements. This new lightweight methodology
challenges many conventional tenets, including the longheld
assumption that the cost of changing a piece of
software necessarily rises dramatically over the course of
time. XP recognizes that projects have to work to achieve
this reduction in cost and exploit the savings once they
have been earned.
1