RT @ashic: Blogged: #Agile Fragile http://t.co/LQuKMOtx...
I’ve recently come across a quite senior person with an obscenely large number of years of experience during which time he has been involved in very large projects (think multi million pound) for very large organisations (think the likes of British Airways). He hasn’t ever worked in an Agile atmosphere. Now there’s nothing wrong in never having worked in an agile manner. However this individual has some very strong opinions about agile. In brief, his view seems to be that agile means “letting groups of people do their own thing and the hoping all of it holds together”. And he is in a role where he spreads his knowledge to many many others. It appears that other people seem to have a similar viewpoint – agile has no discipline or process. It means “winging” it as you go along. It’s about not thinking and just doing. Seriously, where do people get these ideas? I find it quite remarkable that such FUD exists in 2011.
Agile, in many ways, is far more strict than all that CMMI waterfall-y nonsense of years past. Yes, there are many flavours but to say there’s no process to it is ridiculous.
Those who practice TDD, CI, Continuous Delivery would all know about the rigour involved. I’ll just take TDD as a sample. If you’re doing strict TDD, you won’t be writing a single line of production code without a failing unit test. Think about the waterfall equivalent. Would you have test plans and “signed off” test cases that would achieve the same level of coverage? Probably not. You would be coding away at your hearts content only for weird errors to be found during the “testing” phase – at which point recovery may already be too difficult as a bunch of other things have been built in the mean time. In this case, who’s doing the “winging” and “hoping” it works.
Via Charalampos Arapidis