Agile/XP

[scotspine]

not to worry dp. keep at it and i'm sure you'll eventually come across someone who has lots of cash, is a .not guru and who is dripping with it experience

[DimPrawn]

Pair programming can be fun with a 23 yr old girlie grad who is turned on by money, .NET prowess and all round IT experience

Sadly, i've never met such a person, but hey, that thought alone makes me an XP Pair programming supporter.

[Skeptical]

IMHO This has to be the worst project methodology that I have ever come across. Pair programming takes it to the extreme.

On every Agile project I've seen there is a lot of friction between developers and management. Dispite the claims that Agile produces much less buggy software than other methods because it uses pair programming I have found the opposite, I have also found that these projects take much longer to develop - a good 50% longer and with double the resources due to pair programming.

With every other methodology I've used such as DSDM, RUP etc etc there is one big thing that seperates them from Agile - discipline or lack of in Agiles case. On projects using DSDM and RUP etc I have never come across a developer who would say "thats not RUP or DSDM and I'm not doing it" but in Agile developers refuse to do anything they think is not Agile. There is a real lack of respect from purist Agilers.

Anyone else had experiences of Agile - good or bad.

No methodology is good or evil in itself. I think that agile has received too much attention because of its idealism, and because of its very loud supporters.

Things I like in agile and XP: automated building/testing, continuous refactoring, shifting attention from formal documents towards code.

Things I do not like:

Lack of upfront design - absense of planning never saves effort in the long run, good design just doesn't happen by accident.

Pair programming. Why not simply double your programmers' salaries/rates, or hire someone who's twice more expensive and twice more motivated.

On-site customers. Maybe a good idea but it has no place in a software development methodology, it should be decided by marketing or product management people.

[privateeye]

IMHO This has to be the worst project methodology that I have ever come across. Pair programming takes it to the extreme.

On every Agile project I've seen there is a lot of friction between developers and management. Dispite the claims that Agile produces much less buggy software than other methods because it uses pair programming I have found the opposite, I have also found that these projects take much longer to develop - a good 50% longer and with double the resources due to pair programming.

With every other methodology I've used such as DSDM, RUP etc etc there is one big thing that seperates them from Agile - discipline or lack of in Agiles case. On projects using DSDM and RUP etc I have never come across a developer who would say "thats not RUP or DSDM and I'm not doing it" but in Agile developers refuse to do anything they think is not Agile. There is a real lack of respect from purist Agilers.

Anyone else had experiences of Agile - good or bad.