> Earler this week I posted the following question to
> comp.object, unaware that comp.software.extreme-programming
> existed. I am reposting it here to hear from XP'ers about
> where the methodology has succeeded.
> * * *
> I recently read Kent Beck's XP book and subsequently read some
> other things on various agile methodologies. I like "agile",
> but the descriptions of XP scare me a bit. My own take on XP
> is that it wouldn't be good for programming consultancies
> because fixed-price fixed-schedule bids would be hard to
> estimate, it wouldn't be good for large systems, and the
> cultural and paridigm shifts necessary would leave only very
> trusting or desperate customers in in-house situations: web
> apps, perhaps. And the economic downturn will probably reign
> this in a bit.
> XP is getting support from a number of people whom I respect,
> including Martin Fowler, Bob Martin, and even Tom DeMarco.
> But, to me, it sounds like an idea that has come and gone.
> Where is it being used successfully today? (companies or
> markets) If it is so popular, it must be working somewhere. I
> have seen the "Wiki web" but its "Projects" section seems to
> include a lot of projects that are trying a feature or two of
> XP: pair programming, unit testing. I'm not sure most of these
> actually belong there
programming situation. Several other papers are also experience reports.
These are good things to read if you want to see how XP is really being
Consider that most (probably 80%) of software development is done with
no methodology at all ["code-n-fix"]; XP is a big step up for most of