I am practicing Extreme Programing in our
project.In short it will be very useful to the
customer point of view.As a developer we have to die
to meet the schedule working 16 hrs a day, 7 days a
weak.
But the end product will be a matured product to
the customer.Since we are doing the project in the
Iteration basis, the defect will be identified then
and there and it will be corrected.
Agile model advicing about the pair programing
.Means 2 resource should be alloted to do a work.One
will be driver and the other will be guider.If we are
going to adapt this practice both the developer should
be matured enough to share the ideas while
developing.THen only it will be effective.
I can say Extreme Programing will make the
developer to do the work effectively and efficiently.

I will explain the Implementation of XP in brief.Btw
in OOPS language it is very easy to implement.
1.Requirement specification should be done like a
user manual.
2.The whole requirements should be BREAK into
multiple feature which can be implemented in 2 weeks
time.
3.If you feel it cannot be implemented in 2 weeks
break that features into many subfeatures that shall
be implemented in 2 weeks.
4.By now You will get the approximate schedule.
5.It advocates about Less documentation and more
productivity.
6.By the way we should not compromise on
maintaining the record.
7.For this purpose select the tool which are going
to minimize the documentation work.
8.For this we used SWIKI for document management
btn customer and us.
9.We used TogetherJ for Designing and CVS as a
version control tool.
10.This reduced our documentation work and more
consentration on real meat.
11.When comes to the implementation phase Pair
programmer should be used.i.e 2 programmer sitting
side by side implementing the same feature.By this the
bugs will be caught in the source itself.So the peer
review is also happened while implementing itself.
12.Before start implementing the features the
developers has to work with the Unit test cases using
JUNIT.Then start writing the real code for each
method.This is called "Test first principle".
13.Since we are releaseing the product to the
customer on iteration basis then and there the problem
will be esclarated to the developer and we can serve
to our best to the customer and keep the happy
customer always.
14.I am sure this XP is going to be a right way of
doing the project in future.
15.This is going to be a challenging task in the
initial periods.
16.My personal opinion by implement XP We are
keeping in happy customers.
For more information go through
WWW.THOUGHTWORKS.COM.

I think XP will not
work for my organization, when you have to wear many
hats XP will help you commit postal against your
co-workers.

u r right tc.don't follow XP.......................

You'll find an almost unlimited supply of support for XP. The
following link points to some of it's flaws:

www.softwarereality.com/ExtremeProgramming.jsp

Thanks for the link, but I don't think the book is a
good argument for against XP. I don't have a source
available at this time too. Keep on Googl(ing), I
guess.