News for hackers. Stuff that matters.
Re:Three things I don’t like in the agile community by Ramone on Wednesday November 17, 2010 @04:07AM (#1913551)
I'd be interested to hear about (1) that scrum failure in the 10's of millions of dollars, and (2) what you prefer instead of Agile.

(I'm a developer on a scrum team and really think it helps us, but I'm not dogmatic about it or anything... I'd like to hear about the other side. I'm surprised that a huge scrum failure is possible because the customer is generally shown everything at regular small intervals, so it's hard to imagine how a project could get so far off course.)

edit: grammar

Re:Three things I don’t like in the agile community by raganwald on Wednesday November 17, 2010 @10:04AM (#1914427)
I don't know about that SCRUM failure, but the original XP project was a well-documented failure:

https://secure.wikimedia.org/wikipedia/en/wiki/Chrysler_Comp...

One way to explain things is to say that teams like Agile whether it's effective or not (for some definition of effective). Another way to explain this is to say that Agile can't make you succeed, but it's the fastest and cheapest way to fail.

When I'm selling snake-oil, I prefer the latter explanation.

Re:Three things I don’t like in the agile community by Ramone on Tuesday November 23, 2010 @07:35AM (#1933485)
"Another way to explain this is to say that Agile can't make you succeed, but it's the fastest and cheapest way to fail."

Well said... That really cuts through to both the reality of Agile, and the key advantage.