2 ms·
I think you're being rather unfair to Agile. The basic tenets per the Agile Manifesto are reasonable enough, and don't imply any of the silliness you described
by Silhouette 17y ago
I think you're being rather unfair to Agile.
The basic tenets per the Agile Manifesto are reasonable enough, and don't imply any of the silliness you described.
Equally, the incremental style of development shared by all Agile processes has always been a better idea for most types of project than having some huge spec up-front and then not talking to anyone about it for six months. This was true long before anyone coined the term "agile" to describe the idea.
Of course, if you choose to adopt something like XP as your process, then you go a lot further. Personally, I consider XP a rather silly idea, because its basic principle is flawed: just because doing something can be helpful, that does not imply that doing it religiously all the time is better.
Likewise, the basic idea underlying Scrum is to have a prioritised list of stuff you need to get done, divided into practically sized chunks; to do a small number of them to make your next release that does more useful stuff than the last one; and then to repeat. Again, this is a sensible enough idea, and something that a lot of projects have done for much longer than the name "Scrum" has been around. It's only when you start adding on bucketloads of meetings and strict deadlines and people with silly job titles that it becomes rather comical.
These problems with taking basically good ideas too far are not Agile's problem. They are just what you get when consultants smell book deals.