|
Pmi Versus ITIL
In the early 1990s the UK set up a scheme where onsultants were hired, processes evaluated, and the result was the creation of the Information Technology Infrastructure Library (ITIL), which was later made available to the public. The fundamental purpose of Configuration Management is to establish and maintain the integrity and control of software and hardware products (e.g. servers, source code, patches, documents, CPU’s etc) throughout a project’s life cycle. ITIL is often considered alongside other best practice frameworks such as the Information Services Procurement Library (ISPL), the Application Services Library (ASL), Dynamic Systems Development Method (DSDM), the Capability Maturity Model (CMM/CMMI), and is often linked with IT governance through Control Objectives for Information and related Technology (COBIT).
It is essential that organisations are consistent in ensuring that appropriate IT Service Continuity plans have been made to support the business and its continuity requirements. This guarantees that all software meets the demands of the business processes. Dependencies - Dependencies is concerned with the system, infrastructure, service, facility, or interface dependencies in order of importance. Invocation - Invocation details everyone who has the authority to invoke the recovery plan.
Ishikawa diagrams can be defined in a meta-model. A `problem' is an unknown underlying cause of one or more incidents, and a `known error' is a problem that is successfully diagnosed and for which either a work-around or a permanent resolution has been identified.
ITSM is generally concerned with the "back office" or operational concerns of information technology management (sometimes known as operations architecture), and not with technology development. COBIT (or the lighter COBIT Quickstart) is comprehensive and widely embraced. There are a variety of proprietary approaches available from IT service providers, consultants, and research firms.
|
