Skip to main content

The ITIL Application Management Lifecycle and SDLC

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 page130.



Comments

Popular posts from this blog

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem

What Is A Service Offering?

The ITIL4 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 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 than toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.               Note: Goods may not always be provided for every Service

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

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and th