Skip to main content

The ITIL Application Management Lifecycle and SDLC

Image
By
I often get questions on the differences and similarities between the Software Development Lifecycle (SDLC) and the ITIL Application Management Lifecycle. Is the ITIL framework just another rebranding of SDLC? SDLC defines the organization’s standards for the creation and maintenance of applications. The SDLC can be divided into ten phases during which defined IT work products are created or modified. The phases range from initiation, design, development, implementation, operations & maintenance to disposition. The tenth phase, disposition, occurs when the system is disposed of and the task performed is either eliminated or transferred to other systems.

The ITIL Application Management Lifecycle presents a more holistic, service-oriented view. It allows for greater alignment between the development view of the applications and the live management of those applications. This ITIL lifecycle focuses on the overall management of applications as part of IT services. Understanding the characteristics of each phase of the Application Management Lifecycle is crucial to improving the quality of the service delivery.

The Application Management Lifecycle phases are:
  • Requirements – requirements gathered based on the business needs of the organization
  • Design – requirements translated into specifications
  • Build – application and the operational model are made ready for deployment
  • Deploy – operational model and application are put into the existing IT environment
  • Operate – the IT service provider operates the application as part of the business service
  • Optimize- performance is measured, improvement discussed, and more development is initiated if needed.
One important thing to remember is that these phases are CIRCULAR; Optimize feeds into the Requirements phase. Each step of the lifecycle uses business priorities as the driver. The performance of the application in relation to the overall service is measured continually against the Service Levels. Please remember an application is not a service, it is just one component of many that is needed to provision a business service. 
We need to integrate the SDLC activities into the larger context of the ITIL Application Management Lifecycle. It should be similar to the approach in how we integrate a governance framework such as COBIT, or a program methodology such as PMI. We need to understand the strengths and weaknesses of each lifecycle; look for integration points and overlaps. They need to both be aligned as part of the overall strategy of delivering valuable IT services to the business. More information on the ITIL Application Management Lifecycle can be found in the Service Operations book, section 6.5.4 page 130.


 


Comments

Post a Comment

Popular posts from this blog

Four Service Characteristics

By
Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.”  Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...
Post a Comment
Read more

What is the difference between Process Owner, Process Manager and Process Practitioner?

By
This article was originally published in 2015. With the Introduction of ITIL 4, some of the concepts have changed in ways that are described below. ITIL 4 has also introduced new roles, as explained in our blog ITIL 4 and the Evolving Role of Roles . Before we dive into the difference between these roles, let’s first look at a key update in ITIL 4 – the shift from processes to practices. ITIL 4 has evolved to focus on holistic practices vs. isolated processes. By definition, a practice is a set of organizational resources designed for performing work or accomplishing an objective. For example, the purpose of the incident management practice is to minimize the negative impact of incidents by restoring normal service operation as quickly as possible. All organizations recognize the need to allocate resources to the management of incidents and mature their capabilities in that area. In ITIL 4, each practice includes resources based on the four ...
1 comment
Read more

What Is A Service Offering?

By
The ITIL 4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group.   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions 1. Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.      ...
Post a Comment
Read more