Comment Re:Agile is like ITIL (Score 1) 507
Adhering to all of ITIL, for example, is a really good way to ensure your production systems almost never change. The number of people and sheer volume of paperwork, tickets and meetings to get anything even scheduled for a change in a "true ITIL" system is beyond insane
What I learned in my years in IT Compliance (SOX) is two things:
a) nobody really understands these things (ITIL, SOX, Agile, take any buzzword you want), including the people charging you at high-class escort levels for consulting.
b) there are many ways to skin a cat.
SOX is actually very simple, but consulting companies are not interested in simple, they're interested in selling a lot of expensive consulting hours, so they turned it into this monster. I was the Senior Manager for SOX in a 2500 people company and I was not overworked. Another company in the same corporate structure had a room full of people doing SOX, and I dare say their compliance wasn't better than ours.
ITIL is more formalized, but I don't see why anything in it has a hard requirement for the insanity you describe. I'm fairly sure the issue wasn't with ITIL, but with the particular way it was implemented. I'm almost certain it was implemented by outside consultants, am I right?
Just like nothing in Agile prevents you from making architecture decisions early on. It just tells you to keep an open mind for changing them. And nothing in ITIL tells you that you can't change anything, it just tells you to do it in a way that properly tracks the change.
I'm not saying these things are not often nightmares in the real world. I am saying that they do not have to be. There is no "it has to be horrible" clause in ITIL.