When It Becomes Common, It Probably Is Ruined

I have noticed lately that everyone is using Agile software development.  I wrote about this trend at Symantec previously, and since leaving, I have noticed it in a number of other larger companies I interact with somewhat regularly.  ”We use Agile, and you should too!”  It is sad to watch, because the fundamental principles of Agile development are being eroded by the tyranny of process.  Having to define all of the requirements ahead of time for a project, whether you call them User Stories or some other fancy word, is still the same old way of doing things.  The point is that you DON’T know everything now, but you are confident you can figure out the things you don’t know as you go.

Everyone wants in to the Church of What’s Happening Now.  The problem is that when everyone starts going to that church, that church starts to suck because of all the people.  The new members want the church to bend this way or that to ensure continuity.  Well, guess what.  The very reasons that were given for adopting the new thing are most often times the reasons people don’t like it when they get there.  ”We can’t have 500 data points about a project and generate lots of meaningless reports?  How will we measure our worth to our company?  We need a meeting to discuss our backlog and groom it and stroke it and pet it.”

What I have concluded is that the agile methodology as it was originally intended is now dead.  Those of us that liked its way of doing things ( with modification ) are having to move on because the bloat boat is docking at a port nearby.

Stop talking about it and just let it die.