Tag: IT processes

  • 01-3 Define and explain the concept of a service (SS 2.1.1)

    ITILFND01 Service Management as a Practice 01-3 Define and explain the concept of a service (SS 2.1.1) There are a multitude of definitions for the term service. ITIL provides an excellent definition that covers much ground but truly understanding the concept of service management and running IT like a business requires more than just this […]

  • How to present value in business terms in the real world

    A few years ago, I found myself in a two day meeting with a sales person, a technical presales person, and a client’s IT executive team. The company I worked for sold IT Service Management software and the client was a rather important client. The client as it turns out had attempted to purchase four […]

  • IT support sucks but we made our metrics

    SLAs should only include those items that can be effectively monitored and measured at a commonly agreed point. Inclusion of items that can’t be effectively monitored almost always results in disputes and eventual loss of faith in the SLM process. It is essential that monitoring matches the customer’s true perception of the service. A service […]

  • The End-user’s Perception is Your Reality

    In order for processes and services to be managed and optimized, there must be a feedback loop that provides management information regarding the functioning of the processor service. This requires monitoring the process or service in appropriate ways to ensure that it is meeting the stated goal in the most effective and efficient manner. From […]

  • Configuration Management Database Introduction

    The configuration management database is a virtual concept and is made up of many physical databases and physical stores of information. It becomes a CMDB, when the information is brought together with a common interface that makes the information accessible and relevant for decision makers; most importantly, the CIs are related (linked) to one another. […]

  • Operations and Development Tear Down That Wall

    Many IT organizations suffer from less than optimal communication between development and operations groups. This happens so often that a special term has been created to describe what happens during the transition process. IT people say that developed software is “thrown over the wall” from development to operations. The result is that in house development […]

  • Definitive Stores Reduce Costs

    What happens in a typical organization when there is catastrophic damage to a hardware component that requires rebuilding form scratch? In many organizations the existing production configuration would not be definitively known and the exact version of software that was installed is often unknown and not locatable. This results in a rebuilt component that differs […]

  • Great Release Management Requires Project Management

    Release management impacts every process area in the production environment. In addition its effectiveness and professionalism contributes significantly to the general perception of the development group. The most finely developed product ever is considered useless by the business if it can not be effectively deployed. As such it is critical that release management

  • Define Your Roles for Best Communication Flows

    Effective communication flows are important for any organization. They become increasingly important as organizations grow in size or are required to operate in a more rapid fashion. Communication flows are also one of the most difficult aspects of an organization to manage. Much of the difficulty involves the lack of a good model with which […]

  • Create a Loop to Measure Change Management

    How do you know if an individual change or the change process as a whole was successful? This question can be answered by creating a feedback loop. The components of this loop are incident records, problem records, and RFCs (change records). By linking these three components together, we can begin to

  • One Change Management for all of IT

    Many IT organizations have change processes that are specific to different parts of the organization. For instance, development may have its own change process, and each operational technical silo may have a change process of its own. While this may have worked in the past, the current state of technology interdependence makes this type of […]

  • The CAB is NOT the Change Authority

    The change advisory board is an important concept in change management. It is a group of key stakeholders of changes and they serve to advise and assist the change manager in assessing and prioritizing changes. It is an advisory body that does not have responsibility for final approval of changes. That responsibility lies with the […]

  • The Clash of Incident and Problem Management

    The critical distinction between Incident Management and Problem Management can be defined by their contradictory goals. Incident Management is concerned with restoring service as quickly as possible and maintaining SLA targets, while Problem Management is concerned with finding root causes and eliminating errors from the infrastructure. Root cause investigation often requires extended periods of unplanned […]

  • Incident Problem and Known-Error Relationships

    An error in the infrastructure causes a disruption in service. This disruption causes an end-user to call the Service Desk and create an incident record. If the incident can not be resolved, or if it indicates an underlying problem that needs to be addressed, then a problem record is opened and associated with the incident. […]

  • What is a Service

    Service is an integrated composite that consists of a number of components, such as management processes, hardware, software, facilities and people that provides a capability to satisfy a stated management need or objective. IT services can be divided into customer/end-user facing IT services as well as services or sub-services that support customer facing IT services. […]

  • Key Considerations for Service Desk

    These are some of the key considerations to keep in mind, when implementing the Service Desk function. Information collected here is used in many of the other process areas, so it is important to record as much information as may be required to support the activities of those processes. Service Desk will normally be the […]

  • Goals for Service Desk

    Goals for Service Desk

    For every need that an end-user has of IT, there should be an acceptable response from the service desk. For every IT activity that affects an end-user’s ability to work, there should be proactive communication from the Service Desk, explaining what to expect. Service Desk should act as the single point of contact for end-user […]

  • IT is Dead, Long Live IT

    Fundamental progress has to do with the reinterpretation of basic ideas. – Alfred North Whitehead IT is a mere infant in the business world, having existed no more than a few decades. By contrast, professions such as accounting, production, economics, and marketing have been practiced for thousands of years, with at least three hundred years […]