ITSLM Information

ITSLM Menu

Systems Lifecycle Management for IT PDF Print E-mail

Systems Lifecycle Management for IT (SLiM™ IT) is an integrated set of disciplines that are applied to the development, management and retirement of IT systems

SLiM IT is a practical integration of a number of widely recognised standards and frameworks including CMMI, ITIL, and CoBIT. SLim IT is more than a framework, more than good advice, it is also about people and how people interact both as groups and with IT systems. SLiM IT is about coping with the real world, not simply holding out hope of some ideal state or magic bullet. SLiM IT  places emphasis on simplicity, clarity, practicality, and efficiency in both the development and operation of IT systems.

The following diagram summarises my high-level perspective of the main SLiM IT disciplines. This site is committed to explaining in detail how these disciplines interrelate. As you investigate this site you will notice that this diagram shows only one possible view of how these disciplines relate to one another; it is very much a matter of perspective. What works for one organisation will often not work for another. SLiM IT acknowledges this and offers advice on dealing with it.

SLiM IT Disciplines Service Management Problem Management Incident Management Defect Management Release Management Quality Management Build Management Deployment Management Operations Management Configuration Management Change Management Capacity Management Continuity Management Risk Management Project Management Programme Management Asset Management

The overall concern of IT management is the development and maintenance of services. In order to support these services a raft of other disciplines need to be mastered.

For example, when a user perceived a problem with a service they need so be able to report the problem to someone. This is generally the responsibility of the Helpdesk who provide the Incident Management service. In order to analyse and prevent recurrent incidents from sapping resources from the limited pool available to IT the Problem Management function monitors the Incident log, using it to identify root causes to common incidents.

Once the root cause to a series of problems is identified the Problem Management function may raise change requests intended to remove the root cause. Change Management ensures that the change request is analysed and assessed in both the technical and business context so that a recommendation can be made for changes to the IT systems.

An approved change may be dealt with through a business as usual (BAU) process, or may be added to a set of changes scheduled against a project. Either way the change will result in some development and Build activity. Release Management are engaged to ensure that changes are scheduled and Deployed in a controlled manner.

Continuity Management ensure that any proposed changes will not adversely effect the operational system. Continuity Management work with Capacity Management to ensure that the most cost effective IT solutions are in place to support the Services required by the business.

This short scenario illustrates just one of many possible views of the way these disciplines interact.