Skip to main content

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/

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