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

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 the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…