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 once you have something worth automating.
- similarly, 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 mitigation to the point that pre-approval is an acceptable risk, then change gets out of the way (it's called standard change). Absolutely, the Cloud mavens need to convince the Change gatekeepers that automated change is an acceptable risk. Why not?
Frankly, in a normal world, it's hard to argue with Skep. He makes a lot of sense.
But the world is not normal and people nor logical. Change is happening.
I coined the phrase "ITILista" to provoke the process-obsessed, lack of customer-centric, literal-interpreting and yes, techno-phobic people that I've run into my last few years in the ITSM world. It's dismissive, because I've seen this people create projects that drag and drag producing very little value - arranging the decks of the Titanic while Rome burns, to mix my metaphor.
Despite ITIL being about IT, I see a willfull disregard for technology-led change in a small, but vocal part of the ITSM community -- usually some consultants -- who often don't have technology or tool skills.
But Cloud computing a storm that will re-make IT organizations. It is here and doesn't need our permission to come into our lives. Like the internet before, it's re-making some industries and creating collateral damage in others. This one affects the very future of IT departments.
And yes, ITSM people will have an important role to play but only if if they learn the language of the cloud and the technology of the cloud. Those who don't, will not have a job in IT - something I see happening already.
Take Skep's second point. That whole conversation about "having to convince Change gatekeepers," drives people crazy. It's absolutely the worst worst worst way to engage in this conversation.
You know what dev and qa people are doing when they confront that? They go and use a public cloud! And they do it with the blessing of the business. They are aligned! They get projects done. Oh, there are and will be issues, but so what? In this economy getting stuff done now matters.
Meanwhile the ITSM people don't have any visibility and are out of the loop, and then out of a job. Much of the desire for providing private clouds comes from the realization of this trend. It's eiher IT provides the service with convenience, agility, customer self-service and control, or the customer has a choice.
So it's important to understand cloud automation,
- Understanding how provisioning works, vmotion, drs, layer 2 networking, are super important to make risk assesments.
- Understanding how Service Profiles in Unified Computing are making provisioning more responsive and safer allows us to make better decisions about workload management.
- Understanding how cloud bursting allows us to move capex to opex and capacity management are important, but it's not appropriate to every workload.
I can keep on going, but if these three bullets did not make sense.. that's the point. There's a language and understanding chasm between clouderati and ITIListas.
And there are a lot more cloud-people than ITIL people. Just Vmworld alone had 17,000 people attend; ITSMf (where I'm speaking next week), will have between 1,500-2,000 people. No contest when it comes to who owns the dominant language. So it's incumbent on ITSM people to learn the technology of the cloud in order to bring their relevant experience.
The clouderati for the most part won't bother with ITIL.
Heck, one of them told me yesterday I tried to understand ITIL. Had one of my guys explain it for a day. I just gave up. Didn't seem relevant. Waste of time. I am not making this up. Fair or unfair. Smart or stupid. It is what it is.
Here's another example about the chasm between clouderati and ITILista. In our LinkedIn community, over the years there's still arguments over whether you need a tool for a service catalog (and one in which Rob and I agree). In the cloud / virtualization space, it's just accepted and it's part of the architecture of every cloud. No argument; let's just get on with the project.
It boggles my mind that in 2010, there are more people talking service catalog, demonstrating service catalog tools, and implementing them at a cloud show than there are at ITMSF Fusion.
I'm not anti ITIL;I'm just saying that technology, automation have to be part of the skill set in 2010.
I do worry about my ITSM reader's future job prospects. The world is changing and there will be fewer jobs in IT. Those that remain will need to know cloud. That's the message.
I appreciate Skep taking on this topic and giving me the opportunity to more fully rant. :)
What do you think?