Agile has a dark side?
I found this interesting article listing some of the “negatives about moving to an Agile software development process”:http://blogs.sourceallies.com/roller/page/aaron?entry=agile_s_dark_side.
bq. Being a self-proclaimed Agile Advocate I seem to find myself in discussions regard the bad points about agile. Book, articles, and talks on the subject of agile always paint the rosy happy story about using agile. I’m no fool, and I realize that things aren’t quite as happy as some people make it out to be. No one said that agile was a silver bullet. The reason that I’m an advocate for it is because I believe it is simply a better way to write software. Let’s get down to the meat of things. What is the “Dark” side of agile?
I don’t have enough experience with Agile to agree or disagree with any of the points listed, however, I have been thinking about the last one–Loss of Privacy. I have trouble with this point. I listen to Agile people and they push pair programming and team rooms. I then listen to people like Joel Spolsky and Paul Graham who both push the idea that programmers need offices and privacy in order to focus or, stated better, “to get in the zone”. Both views are based on experience so I am not sure which one to go with.
