Resource Library

The ITIL® event management process defines three event types: informational, warning and exception. In this post, I will discuss the different event types and give real-world examples of each.

My most recent blog addressed whether PMP and CAPM boot camps are worth the time and effort. I concluded that for most exam writers, it really did make sense to buckle down and take advantage of all that a quality boot camp offers.

Most organizations quickly realize that knowledge management must be integrated with incident management in order to improve the quality of service and the efficiency of providing assisted service. What is not as quickly recognized is the value of integrating knowledge management with problem management.

A gap analysis is a tool that ITIL recommends organizations use to compare their current state to some future desired state.

For a project manager (PM) who has served as a military officer on a battalion or higher staff, the parallels between the military decision-making process (MDMP), the orders production process, and project management doctrine prescribed by the Project Management Institute (PMI) are difficult to ignore. Both the MDMP and the processes outlined in A Guide to the Project Management Body of Knowledge—Fifth Edition (PMBOK® Guide) are iterative in nature, allow for the introduction of changes to the original plan, assign tasks and responsibilities, and involve the concept of managing the scope of the operation or project.

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.

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. 

Once an organization has categorized suppliers, one of the benefits that is quickly realized is an understanding of how supplier changes affect the buying organization and vice-versa. Changes are the modification, addition, or removal of something from the environment. The scope and scale of each change can be different. Change management covers everything from regular, low-risk, operational modifications all the way to significant organizational strategic shifts.

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.

Lessons learned is a theory, or conclusion, based on evidence at a given time and describes what went wrong (as well as what went right) throughout the lifecycle of a project. Although it’s completed during the project closeout process, it should occur during the entire project lifecycle to ensure all information is captured and documented. Consequences of not having a project review of lessons learned are the increased likelihood of repeating actions that might have caused: