and one does have power and budget while the other one doesn't.
This article via Federal Weekly has some nice smart quotes, from two good friends of min.
“I think we’re on the cusp of a new evolution in IT,” added Steinberg, who has helped the Homeland Security Department and other agencies adopt IT service management practices like those enshrined in ITIL. “What IT used to build and design on their own, they can now rent. Therefore, IT’s role is becoming more of a service integrator.” .... So most will have to learn some new ITIL skills if they also want to manage cloud services that way. Service portfolio, supplier management and solution sourcing will become the pre-eminent disciplines within IT service management, said Rob England, a consultant who created and writes "The IT Skeptic" blog.
This is a topic I have written before on Clouderati vs. ITILista and on I apologize for being too succesful.
In defence of we ITILista, let me say:
- we aren't anti-automation, or dismissive of automation. Process-geeks understand that you have to fix the process before you automate it, else you'll be accelerating backwards. Automation makes bad process faster. Automation is one of the later stages of refinement.
- likewise Change isn't cumbersome. It is about mitigating risk. I don't understand why we would want to drop risk controls. Once you refine your risk management to the point that pre-approval is an acceptable risk, then change gets out of the way (it's called standard change).
in both cases it is a question of maturity making automation possible. Until you get to that maturity level, automation is a technical fix to a non-technical problem: bad process.
Likewise outsourcing. Every wise head in the industry says fix it BEFORE you outsource it.
Cloud is a double whammy: outsourced automation. if you aren't ready to do it then don't. if you are ready, then ITIL won't get in the way - it will help.
Posted by: The IT Skeptic | Tuesday, September 14, 2010 at 04:47 AM