Previous Section   Next Section

8.4. Benefits, costs and possible problems

8.4.1 Benefits

Efficient service management requires an ability to change things in an orderly way, without making errors and taking wrong decisions. Effective Change Management is indispensable to the satisfactory provision of services, and requires an ability to absorb a high level of Change.

Specific benefits of an effective Change Management system include:

8.4.2 Costs

The two principal costs of Change Management are for staff and software tools support.

Staff costs

Staff costs include costs for the Change Management role and team, CAB members, and Change builders, including Configuration and Release Management. These costs should of course be outweighed by the benefits that are, or will be, gained. In practice, most organisations already have a number of people who are spending time on handling Changes.

Although adherence to the guidance in this chapter may appear to increase the amount of management time spent on Changes, in practice you will find that management will spend less time on Changes as the need to handle issues arising from ineffective Change Management is eliminated.

Support tools

The cost of support tools, together with any hardware requirements, needs to be considered. Although tools that integrate support for Change Management, Configuration Management, Problem Management and Service Desks are likely to be more expensive than 'simple' Change Management tools, the additional cost is often justifiable. For larger organisations, management processes can be virtually impossible to implement effectively without adequate support tools.

8.4.3 Possible problems

The Change Management process that you implement should be appropriate to the size of your organisation; an over-bureaucratic process can diminish your effectiveness. Paper-based systems (often found in very small organisations or organisations establishing Change Management for the first time) are difficult to administer and often result in bottlenecks; they are really only practical for very small organisations.

There may be cultural difficulties in getting staff, Customers and Users to accept that a single Change Management system should be used for all aspects of an infrastructure. It may require education to convince everyone that all components of an infrastructure can, and very often do, impact heavily upon each other, and that Changes to individual CIs require coordination. Attempts may be made to implement Changes without reference to the Change Management process. Measures should be introduced to prevent and detect such illicit changes, including:

It may be difficult to ensure that contractors' representatives, such as hardware engineers, adhere to the organisation's Change Management procedures. It is recommended that contracts with suppliers should, where possible, include the need for such compliance. Condition 12 of the standard CCTA CC88 Contract, part 2-C reads:

If the CONTRACTOR proposes to modify any part of the Contractually Maintained Hardware (CMH) the CONTRACTOR shall notify the AUTHORITY and request the AUTHORITY's agreement to the proposed modification, such an agreement not to be unreasonably withheld. If such as agreement is given, then the modification shall be carried out at a mutually convenient time.

The BSI publication A Code of Practice for IT Service Management - PD0005 - also lists points to consider as possible problems. Clearly addressing these points will transform the problems into benefits.

From PD0005: Possible problems with Change Management.

  • the scope of a Change is too wide for the resources available, over-stretching the staff and causing delays
  • ownership of the impacted systems is unclear, resulting in delays and incomplete assessments
  • if Change Management is implemented without Configuration Management, the solution will be much less effective
  • the process is too bureaucratic giving excuses for not following it
  • inaccurate configuration data may result in poor impact assessments leading to the wrong people being consulted about the Change
  • poor synchronisation of upgrades between platforms and across locations makes Changes difficult or impossible to schedule
  • back-out procedures are missing or untested
  • progressing Change requests is manually intensive; it is advisable to start with a simple database or an automate system
  • lack of backing from senior and middle managers will lengthen implementation times, staff will resist the controls that they would prefer to avoid unless they can see the commitment from manager
  • the process frequently fails when emergency Changes should be done

 

Previous Section   Next Section