Pink Elephant
The IT Service Management Experts

Troy's Blog

The Hitch Hiker's Guide to the IT Galaxy and Beyond
Don't Panic

Home

Author

Troy Dumoulin Photo

Troy DuMoulin, VP, Research & Development

Troy is a leading ITIL® IT Governance and Lean IT authority with a solid and rich background in Executive IT Management consulting. Troy holds the ITIL Expert certifications and has extensive experience in leading IT Service Management (ITSM) programs with a regional and global scope.

He is a frequent speaker at IT Management events and is a contributing author to multiple ITSM and Lean IT books, papers and official ITIL publications including ITIL’s Planning To Implement IT Service Management and Continual Service Improvement.

 

The Guide

"This blog is dedicated to making sense out of the shifting landscape of IT Management. Just when we thought we had a good handle on managing technology, the job we thought we knew is being threatened by strange acronym’s like ITIL, CMMI, COBIT, ect.. Suddenly the rules have changed and we are not sure why. The goal of this blog is to offer an element of sanity and logic to what can appear to be chaos."


Hitch Hiker's Guide to the Galaxy

"In many of the more relaxed civilizations on the Outer Eastern Rim of the Galaxy, the Hitch Hiker’s Guide has already supplanted the great Encyclopedia Galactic as the standard repository of all knowledge and wisdom, for though it has many omissions and contains much that is apocryphal, or at least wildly inaccurate, it scores over the older more pedestrian work in two important respects.

First, it is slightly cheaper: and secondly it has the words DON’T PANIC inscribed in large friendly letters on its cover."
~Douglas Adams

Syndicate

Troy On Twitter

Recent Entries

Categories

Links

Other Blogs

Archive


Thursday, March 27, 2008

Virtual Dialog With The ITSM Vendor Community

Leveraging The Power Of The Internet To Promote Best Practices

Pink Elephant’s relationship with software vendors has long been one of collaboration and mutual respect. While Pink is neutral in regards to ITSM technologies we fully acknowledge the critical success factor of process automation.  To gain the promised benefits from ITIL adoption an organization must have a solid strategy around their use of integrated service management tools.

You can read more about my thoughts on this concept in the following blog articles:

For this reason we often work with many different vendors in our efforts to research, document and promote IT management best practices. Over the past couple of weeks I had the opportunity to participate as a guest speaker with two separate vendors. “Epicor and StackSafe”

Epicor ITSM Webcast

On March 18th I participated in a Webcast with Epicor who have a solution called “Epicor ITSM”. In this webcast session I provided a general update on trends related to ITIL adoption and ITSM tools. You can watch this session “Tools and Trends for Aligning IT with Business Growth” hosted by James Norwood of Epicor at the following Link:

Tools and Trends For Aligning IT With Business Growth


StackSafe Interview

On March 17th I had the pleasure to provide an interview to Dennis Powell of StackSafe which has a very interesting product that supports Release and Change Management in relationship to providing a means to test and assure the production readiness of new releases being deployed to the production environment. Incidentally StackSafe won the Vendor Innovation award at our 12th annual ITSM Conference.

Pink Elephant ITSM Awards
The following is a partial transcript of the interview I had with Dennis and can be found in its entirety with audio on his blog at the following link:

Troy DuMoulin Discusses ITIL V3 and Beyond


Interview Transcript - Part 1

SS: How did you get into best practices and standards, what made you become interested in the topic?

TD: I’ve been doing this for the past ten years and I started getting into it from being introduced to Pink Elephant as one of the first North American employees. We were discussing something new and interesting called ITIL. As I got more into it I realized how rare service management and standards are.

How many industries have a common code of practice for conducting business or doing a certain activity? Think about it, is there a course or university where you can go to get a standard process for accounts payable, or a standard way of engineering? No.

But in IT we have a rare commodity which is a standard approach to managing and delivering services. What I found fascinating is the connection to other things that IT does; relationship to project management, application development, governance, etc.

The challenging part with the growing awareness of service management is that our IT education institutions are still producing people with no knowledge of the management side of IT. They graduate knowing how to create a system, develop an application, and build a data center but have no concept of what it means to be a Service Provider. I find that astounding. The education side of our industry is still behind.


SS: How can companies benefit from implementing ITIL V3? What would you cite as the ROI? (Financial savings? Freeing up resources? Technological advantages?)

TD: The benefit of implementing standards is a big topic. To simplify this, think of IT as three broad categories of activity:

  * Managing Operations and Technology,
  * Managing Projects
  * Managing Services and Service Delivery

These are three different things.

Because of our historical background, we’re very segmented by silo and technology domain. Most frequently organizations will first focus on optimizing and reducing cost in an operational sense, or focus on project management methodologies to improve the ROI on projects to receive benefits more quickly.

The challenge with this is that it is still very fragmented. You can get projects up and running and get good at delivering on time and on budget, or you can optimize the technical domains to a certain point – but the real benefit or cost saving opportunity is when you realize there is all this redundancy across these silos. Each silo has to recreate the same practices over and over again, so there is redundancy across the entire system.

When we talk about version 3 and ROI you have to understand that it’s only when you start looking across the silos for new ways to optimize across the organization as opposed to within a specific project or domains that you begin to get that benefit.

There are three different types of improvement you can realize when you talk about ROI or improvement by using standards: cost-savings, quality improvement, and productivity. We did a survey recently with BMC of 800 companies on usage of best practices and what they got out of it. The majority said efficiency which falls under the categories of productivity and quality. Hard cost savings are difficult to attest to when you don’t have a good understanding of your current costs.

If you think of ROI primarily in terms of cost-savings, then it is very difficult to find justification for implementing practices that don’t currently exist. You will be successful at reducing outages, incidents and failed changes; however, most companies will find it hard to equate these to hard savings. The adoption of best practice typically means the reduction of waste and redundancy; however, it also means an increase in net new activity that was not done before. This means that while quality and productivity can improve dramatically the reduction of cost is less apparent. This is why we prefer to talk about Value On Investment versus Return.

The challenge here is that most organizations have no clue what the current cost of an Incident or failed Change is. Companies ask what is the ROI for implementing a process like Change Management or Incident Management? To answer that question you have to determine what is the current cost of an outage? Once that is identified and reduced by a certain percentage, I can give a real number.

The area where you can actually see a hard cost savings relatively quickly is around the IT Management tools in use in an organization. Many companies have significant redundancy here. When you have multiple monitoring, ticketing, or inventory tools in each silo, you will start to connect the fact that these processes and services are organizational wide – you will begin to understand tool usage is not by domain but is an enterprise issue. You must have a SINGLE workflow process and supporting tool for the entire enterprise. That reduction of redundant management tools based on reduced management and maintenance cost represents true hard savings and ROI from a service perspective.


SS: Are there legitimate reasons why a company should stay at ITIL V2 for the time being?

TD: If you truly understand what version 3 is, you’ll realize it’s not that different. All the processes that you know and understand in version 2 are still inherently a part of the package of version 3 but the scope has simply been enhanced with an increased emphasis on the Service Lifecycle.

An analogy I like to use is the idea of the Wizard of Oz. We have a person who is lost, and they find a path – the “Yellow Brick Road”, which is ITIL. Somewhere out there is the “Emerald City”, which is ITIL version 2, where all these processes are working flawlessly and integrated. On the way to the Emerald City, there are issues that arise (“flying monkeys”) in daily operations, but you continue down the path. Just as you are looking over the horizon, you see Emerald City, and think that’s the end. But to your shock and horror, you realize it wasn’t the end, it was simply a milestone. Beyond in the distance it is the “Diamond City”, which is version 3.

Version 3 is not a different beast or animal, it’s simply a different milestone down the path. The way organizations implement between version 2 and version 3 hasn’t changed. From an operational perspective, it’s the same. You’re simply walking a path and reaching a strategic level.


SS: What is the top challenge that you hear from companies who are in the midst of implementing ITIL?

TD: Without a doubt it’s organizational change and IT culture. The concept of working in a service mindset is a world of difference to a complete focus on the domain where each person manages their box or application as if it lives in mythical isolation from other technologies let alone the business. That comes back to the session in our recent conference in Vegas where I talked about focusing on optimization and cost-reduction as a total goal for IT.

I believe that the majority of executives believe that the “Total” goal of IT is to optimize performance and cost or technology silos. When you do this year over year you get down to the point where you’re razor-thin, consolidating data centers, moving to virtualization, and reducing people resources. You get down to a skeleton crew that is barely sufficient to manage the boxes and the applications, which gives no extra bandwidth to do these service management value-added activities above and beyond the technology optimization.

These organizations now have all these services to provide, but can’t afford to do it with the time and resources they have. There is a total paradigm shift from total cost-reduction as the primary goal to now adding value as a service provider. Being a service organization is about thinking, acting and being different in relationship to business value. The problem is they’re no longer at the resource level to expend the time and energy to do this. It’s kind of a Catch-22 situation. They want to get better and move to a service perspective, but often don’t have the resources.

Read part 2 of this interview not captured here at the following link:

ITIL V3 and Beyond Part 2

Troy’s Thoughts What Are Yours?

“Sometimes when I’m talking, my words can’t keep up with my thoughts. I wonder why we think faster than we speak. Probably so we can think twice.” ~ Bill Watterson

(0) Comments
Posted by Troy DuMoulin on 03/27 at 10:41 AM
ITIL & Beyond (0) TrackbacksPermalink

Don't Panic

Page 1 of 1 pages