What You Need to Know About ITIL V3

What is ITIL?

ITIL (Information Technology Infrastructure Library) is a widely recognized set of best practices for IT service management (ITSM) that aims to align IT services with the needs of businesses. ITIL provides a practical, no-nonsense framework for identifying, planning, delivering, and supporting IT services to the company. 

Originating in the 1980s as a collection of books developed to standardize IT management practices across the UK government, ITIL has evolved through several revisions, the latest being ITIL 4, to accommodate the changing landscapes of IT and business integration. 

ITIL guides organizations on using IT to foster business transformation and growth, focusing on processes, tasks, and checklists. ITIL is not specific to any organization, meaning any organization can apply it to establish integration with the strategy and deliver value.

What is ITIL V3?

ITIL is a framework consisting of best practices and processes that can be adopted in order to provide IT service management (ITSM). Since its first publication in the 1980s, ITIL has become one of the most widely used framework by organizations to provide ITSM. The framework places importance on improving customer satisfaction by providing effective service delivery while being cost effective.

Over the years, the different versions of ITIL have released in order to stay aligned with changing business requirements. Termed ITIL V3 the third version of ITIL best practices framework was released in 2007. An update to ITIL V3 was made in 2011, because of which, ITIL V3 is also called ITIL 2011 V3. This latest version is more suited for today’s business environment because it includes strategic elements so that the IT service management is more aligned to the business requirements.

What are the guiding principles of ITIL V3?

Focus on value

ITIL emphasizes the importance of consistently delivering value to customers and the business. In other words, every action, decision, and service should be evaluated based on the value it offers stakeholders. This principle encourages organizations to understand their customers' needs, preferences, and perceptions of value to ensure their services meet those expectations effectively. It's not just about the IT services in isolation but how these services contribute to achieving business objectives and enhancing customer satisfaction.

Design for experience

ITIL insists on designing services with the end-user experience in mind. Designing for experience goes beyond functional requirements to include user satisfaction, usability, and the overall customer journey and interactions with the service. 

This principle encourages the inclusion of user experience (UX) considerations from the earliest stages of service design, aiming to create more engaging, intuitive, and satisfying services. It acknowledges that a positive user experience is critical to the perceived value of the service and, by extension, to the service provider's success.

Start where you are

This principle advises against reinventing the wheel when improving or developing new services. It suggests evaluating existing services, processes, and capabilities before making significant changes or new projects. Organizations can often save time and resources, reduce risks, and build on proven practices by understanding and leveraging what is already in place. It promotes a pragmatic approach to service improvement, focusing on incremental gains rather than wholesale transformations.

Work holistically

Work holistically emphasizes the need to consider the entire system when designing, implementing, and managing services. This principle acknowledges that all service components, including processes, people, partners, and technology, are interconnected and must be coordinated effectively to deliver value. 

This principle encourages a comprehensive approach that looks beyond silos and individual elements and aims for a cohesive and integrated service management strategy that supports the organization's objectives.

Progress iteratively

Progress iteratively with feedback encourages organizations to approach service development and improvement in manageable increments. This allows for regular feedback and adjustments, making it easier to respond to changes and correct course as needed. It supports a more agile and responsive approach to service management and reduces the risk of large-scale failures to enable more frequent value delivery to customers and the business.

Observe directly

Direct observation stresses the importance of obtaining firsthand information to make informed decisions. Direct observation and data collection from the service environment are more reliable than assumptions or second-hand reports. This principle supports a culture of evidence-based decision-making, where people take action according to real-world insights into how users utilize services and how well they perform.

Be transparent

This principle advocates for openness and honesty in all aspects of service management. It involves sharing information freely within the organization and with customers, fostering trust, and enabling better collaboration. Transparency helps stakeholders understand decision-making processes, how services perform, and how issues are addressed, contributing to a more inclusive and accountable service management practice.

Collaborate

This principle emphasizes working with customers and partners across organizational boundaries. It recognizes that effective service management requires input and cooperation from various stakeholders. Collaboration encourages sharing knowledge, skills, and experiences, leading to more innovative solutions and a more substantial alignment between IT services and business needs.

Keep it simple

Keep it Simple advises focusing on what is truly necessary and avoiding overcomplication. It suggests simplifying processes, reducing bureaucracy, and eliminating redundant activities that do not add value. This principle promotes efficiency and effectiveness, making service management more agile and adaptable. Organizations can ensure their efforts deliver the most impact by concentrating on the essentials.

ITIL V3 Certification

Over the years, the popularity of ITIL V3 has increased significantly; it has become one of the widely used methodology to ensure a seamless flow of ITSM process. ITIL V3’s wide acceptance globally and its popularity has made ITIL V3 certification one of the most coveted certification in the IT industry. As mentioned above, ITIL V3 is more aligned to the business requirements of today and ITIL V3 certification can be achieved after completing five levels:

Foundation Level

This is the entry level certification that provides the candidate taking the certification with a general background on the fundamental terminology and concepts in ITIL service lifecycle, interaction between the different lifecycle stages and the processes adopted for ITSM.

Practitioner Level

The second stage in the ITIL certification level is the Practitioner level. This level will equip the candidate taking the ITIL certification with capabilities to adopt and sustain ITIL.

Intermediate Level

IT industry recognized qualification level is the Intermediate level where module level focus in provided on IT service management.

Expert Level

Candidates completing the Expert level certification will be able to showcase superior ITIL V3 best practices skills and possess a detailed and in depth knowledge on the entire ITIL V3 process.

Master Level

Candidates vying to complete the Master level in ITIL V3 certification should aptly demonstrate their knowledge on ITIL V3 and provide supporting documentation including successes achieved in practical assignments where ITIL V3 was implemented for IT service management.

ITIL V3 Fundamentals

ITIL V3 Incident management

In today’s business environment, it is imperative to ensure the business operations are conducted seamlessly without any hurdle. In case of an unexpected disruption to a service within the organization, productivity gets compromised. ITIL V3 Incident Management process adopts a set of best practices for effective incident handling and incident resolution to ensure smooth business operations with minimal or no downtime.

ITIL V3 Change management

Change is inevitable in every organization; technologies continually change and have to be replaced, existing solutions/applications have to be upgraded, etc. ITIL V3 provides a set of best practices termed Change Management to handle, prioritize and roll out changes efficiently. By utilizing change management effectively, downtime can be avoided.

ITIL V3 Problem management

The Problem Management team is responsible to perform a Root Cause Analysis (RCA) and to find a permanent fix/workaround for recurring incidents. It is recommended to have an effective communication strategy and to follow a proactive approach to avoid any major incident occurrence. Problem is one or more incidents with an unknown root cause. Problem management maintains a known error database, KEDB whose solution is unknown.

ITIL V3 Framework

The core of the ITIL v3 framework revolves around the ITIL Service Lifecycle and a set of supporting processes and best practices for each stage. The 5 ITIL Stages are:

• ITIL Service Strategy

• ITIL Service Design

• ITIL Service Transition

• ITIL Service Operation

• ITIL Continual Service Improvement

ITIL was designed such that the lifecycle stages together form a closed-loop process. This is important because most service management activities aren’t performed when creating services from scratch, they are activities that fix or enhance an existing service. Each stage of the service lifecycle is represented by one of the ITIL volumes and is self-contained while at the same time integrating into the overall ITIL framework.

ITIL Service Strategy

The purpose of Service Strategy is to provide a strategy for the service lifecycle and to ensure that the service is fit for purpose and fit for use. The strategy should be in sync with the organizations business objectives as well as customer needs. Starting from an assessment of customer needs and the marketplace, the Service Strategy lifecycle stage determines which services the IT organization is to offer and what capabilities need to be developed.

• Strategy Management for IT Services - Assess the service provider's offerings, capabilities, competitors as well as current and potential market spaces to develop a strategy to serve customers.

• Service Portfolio Management - Ensures that the service provider has the right mix of services to meet the required business outcomes at an appropriate level of investment.

• Financial Management for IT Services - Manage the service provider's budgeting, accounting, and charging requirements.

• Demand Management - Understand, anticipate and influence customer demand for services to ensure that the service provider has sufficient capacity to meet the required demand.

• Business Relationship Management - Identifies the needs of existing and potential customers and ensures that appropriate services are developed to meet those needs.

Within Service Strategy, Service Portfolio Management helps the organization manage services as a holistic portfolio; demand management is concerned with understanding and influencing customer demand by modeling user profiles and patterns of business activity; Financial Management is concerned with understanding costs and opportunities associated with services in financial terms. Working together, these processes provide the capability for your organization to make informed decisions about what services to provide and how they should be constructed.

ITIL Service Design

The Service Design lifecycle phase is about the design of services and all supporting elements for introduction into the live environment. The scope of the Service Design lifecycle stage includes the design of new services, as well as changes and improvements to existing ones.

• Design Coordination - Ensures the consistent and effective design of new or changed IT services, service management information systems, architectures, technology, processes, information, and metrics.

• Service Catalog Management - Ensure that a Service Catalog is produced and maintained, containing accurate information on all operational services and those being prepared to be run operationally.

• Service Level Management - Negotiate Service Level Agreements with the customers, designing services in accordance with the agreed service level targets and ensuring that all Operational Level Agreements and Underpinning Contracts are appropriate.

• Risk Management - Identify, assess and control risks, including analyzing the value of assets to the business, identifying threats to those assets, and evaluating how vulnerable each asset is to those threats.

• Capacity Management - Ensure that the capacity of IT services and the IT infrastructure is able to deliver the agreed service level targets in a cost-effective and timely manner.

• Availability Management - Responsible for ensuring that all IT infrastructure, processes, tools, roles, etc. are appropriate for the agreed availability targets.

• IT Service Continuity Management - Ensures that the IT service provider can always provide minimum agreed Service Levels, by reducing the risk from disaster events to an acceptable level and planning for the recovery of IT services.

• Information Security Management - Ensure the confidentiality, integrity and availability of an organization's information, data and IT services.

• Compliance Management - Ensure IT services, processes and systems comply with enterprise policies and legal requirements.

• Architecture Management - Define a blueprint for the future development of the technological landscape, considering the service strategy and newly available technologies.

• Supplier management - Ensure that all contracts with suppliers support the needs of the business and that all suppliers meet their contractual commitments.

The purpose of ITIL Service Design is to ensure that the services being developed fulfill the organizational intent described in service strategy and take into consideration things like supportability, risk management, and business continuity. The more service integration and management issues that can be addressed during service design, the easier service transition becomes.

ITIL Service Transition

The objective of ITIL Service Transition is to build and deploy IT services and ensure that changes to services and service management processes are carried out in a coordinated and safe way.

• Change Management - Control the lifecycle of all changes to enable beneficial changes to be made, with minimum disruption to IT services.

• Change Evaluation - Assess major changes before those changes are allowed to proceed to the next phase in their lifecycle.

• Project Management - Plan and coordinate the resources to deploy a major release within the predicted cost, time and quality estimates.

• Application Development - The development and maintenance of custom applications as well as the customization of products from software vendors to provide the IT services that users need.

• Release and Deployment Management - Plan, schedule and control the movement of releases to test and live environments -ensuring that the integrity of the live environment is protected and that the correct components are released.

• Service Validation and Testing - Ensure that deployed releases and the resulting services meet customer expectations, and to verify that IT operations can support new services.

• Service Asset and Configuration Management - Maintain information about configuration items required to deliver an IT service, including their relationships.

• Knowledge Management - Gather, analyze, store and share knowledge and information - improving efficiency by reducing the need to rediscover knowledge.

In this phase of the lifecycle, the design is built, tested and moved into production to enable the business customer to achieve the desired value. This phase addresses managing changes and transition planning to ensure that all stakeholders are prepared for the service release.

ITIL Service Operation

The objective of ITIL Service Operations is to make sure that IT services are delivered effectively and efficiently by fulfilling user requests, resolving service failures, fixing problems and carrying out routine operational tasks

• Event Management - Ensure CIs and services are constantly monitored, and to filter and categorize events to decide on appropriate actions

• Incident Management - Manage the lifecycle of all incidents to return the IT service to users as quickly as possible. Provides permanent or temporary resolution to end-users to restore normalcy as soon as possible

• Request Fulfillment - Fulfill service requests, which in most cases are minor changes and/or requests for information.

• Access Management - Grant authorized users the right to use a service while preventing access to non-authorized users.

• Problem Management - Manage the lifecycle of problems to prevent Incidents from happening, and to minimize the impact of incidents that cannot be prevented. Root cause analysis, RCA is performed to find a permanent solution

• IT Operations Control - Monitor and control the IT services and their underlying infrastructure, including the execution of day-to-day routine tasks related to the operation of infrastructure components and applications.

• Facilities Management - Manage the physical environment where the IT infrastructure is located, including things like power and cooling, building access management, and environmental monitoring.

• Application Management - Responsible for managing applications throughout their lifecycle and making decisions to support continuous improvement of application components.

• Technical Management - Provides technical expertise and support for the management of the IT infrastructure

• Closure - Set up an automation rule to automate ticket closure process or let end users close tickets themselves through the self-service portal.

Service operations oversee the daily overall health of the services that are delivered to users and business functions. This includes managing disruptions to service and ensuring restoration after incidents; and determining the root cause of problems. It also includes service desk activities such as handling end-user requests and managing service access permissions.

ITIL Continual Service Improvement

The Continual Service Improvement (CSI) process uses methods from quality management to learn from past successes and failures and improve the overall quality, cost performance and/or usability features to an existing service.

• Service Review - Review business services and infrastructure services on a regular basis to improve service quality and to identify more economical ways of providing a service.

• Process Evaluation - Evaluate processes on a regular basis, including identifying areas where the targeted process metrics are not reached and holding regular audits, maturity assessments and reviews.

• Definition of CSI Initiatives - Defining specific initiatives aimed at improving services and processes, based on the results of service reviews and process evaluations.

• Monitoring of CSI Initiatives - Verifying that improvement initiatives are proceeding according to plan and introducing corrective measures where necessary.

The Continual Service Improvement process aims to continually improve the effectiveness and efficiency of IT processes and services. Companies will often structure their improvement efforts into CSI Initiatives which are prioritized and managed ad projects as compared to other service management tasks that are treated as ongoing operations. The objective of CSI initiatives is to define and execute specific efforts aimed at improving services and processes based on the results of service reviews and process evaluations.

These 5 stages of the ITIL Service Lifecycle work together to support all aspects of service management including the creation of new services and making changes to existing services. Deciding which lifecycle stages are most important for your organization requires a solid understanding of your organization’s culture, strengths, and weaknesses so you can focus on the processes that will have the greatest impact on your company.

What’s the difference- ITIL V2 vs ITIL V3

Essentially, ITIL V3 or ITIL 2011 builds on the operational processes and best practices of ITIL V2 and strives to ensure IT service management is more comprehensive to suit today’s business climate. ITIL V2 was established in the 2000s and was more process focused.

ITIL V3 retains the five lifecycle publications that was was part of the previous versions. However, ITIL V3 has a very critical upgrade- it places great emphasis on aligning ITSM with business goals by focusing on strategic elements. Let us take a closer look at how ITIL V3 differs from the previous version ITIL V2.

What's the difference between ITIL V3 and ITIL V4?

The transition from ITIL V3 to ITIL V4 was a significant evolution in the ITIL framework. This progression addressed the changing dynamics and requirements of the modern digital and IT service management world.

While ITIL V3 introduced a comprehensive structure for IT service management through its Service Lifecycle approach, covering stages from service strategy to continual service improvement, ITIL V4 shifts towards a more holistic, flexible, and integrated approach.

ITIL V4’s most significant change lies in its integration with other contemporary frameworks and methodologies like Agile, DevOps, and Lean, moving away from V3’s more siloed and controlled approach to a collaborative, flexible model that encourages integration and adaptability.

This substantial rethinking aims to make ITIL more relevant in today’s fast-paced, interconnected IT environment. The emphasis on value co-creation, the introduction of practices over processes and functions, and the detailed attention to how services are developed, delivered, and continuously improved signify ITIL 4’s alignment with modern IT practices and challenges.

ITIL 4 also introduces new concepts, such as the Service Value Chain and practices, alongside a redefined focus on the guiding principles of ITIL Practitioner, making these core tenets more accessible and central to the framework. These changes reflect a broader understanding of value creation and service management, positioning ITIL 4 as a comprehensive framework adaptable to various organizational contexts and external methodologies.

ITIL V3 Foundation

ITIL V3 Foundation is the first level of certification that is provided when a candidate beings their quest to Master ITIL V3. Essentially, the ITIL V3 foundation level will provide an overall understanding of ITIL V3 terminology, basic definitions and concepts. The ITIL V3 foundation level can be taken by candidates who want to:

• Gain a beginners level knowledge on ITIL V3 framework

• Understand how to implement ITSM based on ITIL V3 framework.

Format of ITIL V3 Foundation Level Examination

The certification can be taken by anyone who wants to learn about ITIL processes and there is no eligibility criteria. ITIL foundation acts as a prerequisite to take other level exams. This enables individuals to start their career path in IT profession.Please note that there are no prerequisites to take the ITIL V3 foundation level exam. The format of the exam would be as follows.

• The foundation level examination comprises of 40 multiple choice questions and awards 2 credits to candidates who clear this level.

• A minimum of 65% (26/40) would ensure the ITIL V3 foundation level certification can be procured.

• It should be noted that ITIL V3 foundation level examination is a closed book exam.