Resource Library

As long as I've been involved in service management, one of the perennial debates that's really never been resolved focuses around how many discrete processes ITIL describes. No such single list exists in the ITIL core books. However, section 4.1 of each of the ITIL 2011 core books shows the processes described within that specific book. When we deliver accredited ITIL training, if it is describe in section 4.1 of any of the ITIL core books, then it is considered a "process".

What's the correct sequence of activities for handling an incident? Find out why categorization occurs before initial diagnosis in the ITIL incident management process flow so you can answer this common ITIL Foundation exam question.

None of us have much time to waste, so what can you do when your environment changes quickly and you need to come up to speed on a device that you have never seen before? You find the quickest way to bring yourself up to speed. Some of you will have experience with other vendors’ equipment, and some of you will not have much experience at all; therefore, we will focus on topics that will get your feet wet the quickest and have you talking Junos in no time.

Previously I discussed service providers and their risks in the example of my involvement with a landscaping company. ITIL clearly states that services, “…deliver value to customers by facilitating outcomes customers want to achieve…” However, sometimes organizations and people focus on outputs as opposed to outcomes, which sacrifices some of the value of the service. This leads to a question, what is the difference between an outcome and an output?

Regardless of your vendor preference or your experience on the Juniper JUNOS CLI, assuming you have a point of reference to another vendor, your first thought when experiencing JUNOS is, “I have been here before.” The CLI is familiar, convenient, and polished. The similarities between JUNOS CLI and another CLI such as Cisco’s IOS are not what I want to focus on here however; it is their differences I want to focus on. But first, when you connect to a JUNOS powered device and access Operational Mode (see Brad Wilson’s blog post Introduction to Juniper Junos), it looks very much like the User EXEC Mode in IOS. In fact, there are a lot of JUNOS commands that are very much like the IOS User EXEC Mode commands.

Organizations that plan for and conduct supplier management according to defined processes and boundaries are more likely to receive predictable, high-quality goods and services from their suppliers in a timely manner.

ITIL is generally not prescriptive. In reality, the CSI Register at any given organization might look significantly different than the example given in the CSI book. The fields given in this example are important. 

Many I&O leaders and customers see little value from investments in ITIL. Not getting the Return on Investment (ROI) you expect normally comes from using ITIL incorrectly. You, your staff, and your customers must share the same goals and understand exactly what to expect from your ITIL investments. The goal of ITIL is not “business and IT alignment” or “competitive advantage from IT investments.” Instead, its first goal is to stabilize service operation. This builds a base for the second goal: increasing value through service optimization. You must have clear-cut, documented, and managed expectations for each activity, and order is vital. Success requires that you stabilize service delivery before trying to optimize. Focusing on the correct goal and linking each ITIL task to that goal is the correct use of ITIL.

Traditionally, ITIL and TOGAF professionals have been part of different teams within an organization. Due to the ongoing alignment of business and IT, these professionals now often find themselves on the same team. Because of this crossover, there is a growing trend towards organization of work based on multiple best practice models. 

As a power user, find out if you're ready for the SharePoint Site Collection and Site Administration class and how it can benefit your organization.