Get 30% off on toolkits, course exams, and Conformio yearly plans.
Limited-time offer – ends April 25, 2024
Use promo code:

ITIL Application Management Lifecycle – within IT Service Lifecycle

Everything we use on our computers and mobile devices are applications of some sort. Even now, as you’re reading this blog post, you are using an application for browsing the web. I’m guessing that you’ve sent and received several e-mail messages today using e-mail application software, and probably used a word processing and / or spreadsheet application as well. Those, and many other applications, have their roles firmly established within our daily routine – so much so that we almost take them for granted. But, if you use those applications within a business environment, and for the business itself, then you’ll need to make sure such applications can be depended upon, are best fits for the task, and are cost effective. Not only that, but business applications (and business supporting applications) must be compatible with the business environment, meet certain security requirements, and be easy to operate and maintain. How to effectively balance between all those requirements is the topic of ITIL Application Management Lifecycle.

ITIL Application Management Lifecycle

Application Management is responsible for managing applications throughout their lifecycles. Application Management is a function, which supports and maintains operational applications and also plays an important role in the design, testing and improvement of applications that form part of IT services.

Figure 1 – ITIL Application Management Lifecycle

The Application Management Lifecycle, as shown in Figure 1, consists of six logical and easy-to-understand phases:

  1. Define – the requirements for a new application are gathered, based on the business needs of the organization.
  2. Design – is the phase during which requirements are translated into specifications for the IT components that are required. Design includes the design of the application itself or of any customization to standard packaged software, and the design of the environment or operational model that the application has to run on.
  3. Build – both the application and the operational model are made ready for deployment. Application components are coded or acquired, integrated and tested. For purchased software, this will involve the actual purchase of the application, any required middleware and the related hardware and networking equipment. Any customization that is required will need to be done during this phase.
  4. Deploy – both the operational model and the application are deployed. The operational model is incorporated into the existing IT environment and the application is installed on top of the operational model, using the Release and Deployment Management process described in the ITIL Service Transition.
  5. Operate – the IT services organization operates the application as part of delivering a service required by the business. The performance of the application in relation to the overall service is measured continually against the Service Levels and key business drivers.
  6. Optimize – the results of the Service Level performance measurements are measured, analyzed and acted upon. Possible improvements are discussed and developments initiated if necessary. The two main strategies in this phase are to maintain and/or improve the Service Levels and to lower cost.

Application Management Lifecycle within ITIL Service Lifecycle

It is important to distinguish that applications themselves do not equate to a service. It is common in many organizations to refer to applications as “services”; however, applications are but one component of many needed to provide a business service.

In case of Software as a Service (SaaS), the end user uses application software (generally stored and executed in the cloud) on demand via thin client hardware or via web services – without usage of any resources on his part, other than those required to access the SaaS provider. And, even in those cases, the software application is a service frontend, but not the service itself.

Figure 2 – Application Management Lifecycle vs. ITIL Service Management Lifecycle matrix

So, what does all this mean for the Application Management Lifecycle? In general, as the complexity of applications increases, so does our effort to manage them. Fortunately, the Application Management Lifecycle is strongly tied to the ITIL Service Management Lifecycle (as shown in Figure 2), allowing us to handle all challenges associated with it in a way we are already familiar with, and which is considered to be the best practice.

With all of our (business) dependence on applications, both business representatives and IT organizations must be aware of the benefits that good Application Management brings. It ensures not only functionality required, but it also ensures that the application selected will fit well within the current business environment, and more importantly, will not increase operational and management costs.

You can also check out this free sample of the Application Management Function to learn about the process responsible for managing applications throughout their lifecycle.