Re: Proposed edit
There is a good reason why I called 'agile' "Fragile". 90% of the releases of one project I worked on were total crap and nowhere near good enough for an 'Alpha' release from the old waterfall system. By the time we were supposed to ship the finished product it was nowhere near ready. Then the automated build process fell in a heap and no one realised for a week.
Two of us took the code (basically forked it) and went offsite for two weeks out of reach of the rest of the team and especially the people running (sic) the agile process.
We returned with a product that worked and was solid enough to go out for field testing.
Most of the people who championed Agile left shortly after that and moved on to wreak havoc at other comanies. We returned to a more sane development process and everyone was a lot happier. Deadlines were met with ease if you have a team that is motivated and not dictated to by the process.
Biting the hand that feeds IT
