Hey there everyone! It is me. I would like to add some thoughts to my last posting about the advantage to developing a Service Catalog and CMDB as parallel initiatives. While I would agree that this may add some additional complexity to the project, I think the value that can be captured from such an approach will bring about true measurable value to the organization that may not be achieved otherwise.

The inherent nature of ITIL processes almost always leads to ITIL gridlock. In my experience on implementing an individual ITIL process, there is always a grocery list of opportunities that need to be placed on hold until a dependency can be addressed by another process area. This is especially a challenge in the initial phases of an ITIL implementation because typically most of the support structure needs to be addressed to properly establish a portion of an ITIL discipline. Establishing SLM is no exception. In fact, initiating the discipline of SLM by starting to create a Service Catalog is commonly one of the most significant challenges in adopting ITIL processes. This is largely due to two factors. The first is dealing with the organizational challenges from adopting and working in a service-oriented structure. The second has to do with addressing the management of a Service Catalog structure.

These are the two points I will like to discuss next time we have a chance to chat. So enough from me (for this time); I would like to hear from everyone with your thoughts on SLM and the dependencies that Service Catalog has on the CMDB. I welcome your thoughts and questions.

Also, check out our new White Paper on “How To Develop a Service Catalog”.

Technorati Tags: help desk software help desk itil service helpdesk software desk helpdesk itil software support software

—–