Application Management Lifecycle

From an operational perspective, we are primarily interested in the overall management of applications as part of IT services. These can be developed in-house or purchased off the self from third party developers. Because of our operational point of view, and the focus on ensuring these services/applications are delivered with both utility and warranty, we look at their support from a more holistic approach and use what is referred to as the “Application Management Lifecycle”. It sequences through six stages or steps which are: Requirements, Design, Build, Deploy, Operate and Optimize.

Requirements: Requirements for new applications are garnered, based on business/customer needs and takes place primarily during services design. There are six types of requirements for any application

Functional requirements
Manageability requirements
Usability requirements
Architectural requirements
Interface requirements
Service Level requirements

Design: At this point the requirements get transformed into specifications. In the case of in-house developed applications this will include design of the software itself, the environment the application has to run on. Here architectural considerations are critical. If the software is being purchased, we will likely not have input into the design, but must be able to have feedback on functionality, manageability and performance of the package.

Build: If building the software, the application components are coded, integrated and tested. Testing is done both in the build and deploy stages. In the build stage the focus is on the ability of the application to meet functionality and manageability requirements. If software is being purchased this will be when this takes place. Any additional/supporting software or hardware will also be purchased at this time.

Deploy: At this stage the application will be deployed along with the operational model (release package). Testing again takes place but here the focus is ensuring the deployment process and mechanisms operate appropriately. We also test the application in the live environment to ensure that it is meeting its intended functionality (early life support).

Operate: Services (applications are just one of the components) are being delivered as part of normal operations. Performance is being continually monitored and measured to enable effective management of the service delivery and ensure key business drivers are being met.

Optimize: Measurements are being analyzed and CSI is being acted upon. Because of this and the circular nature of the Application Management life cycle, this same application can have multiple iterations at different stages at the same time.

In a mature ITSM organization, and given various business and ITSM requirements, operational staff can play many of the key roles in some or all of the stages.

For more information on this subject please follow this link: http://www.itsmacademy.com/itil-osa/

Four Service Characteristics

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

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

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

What Is A Service Offering?

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

Search