Implement It Change and Conf 318869
Implement It Change and Conf 318869
Key Challenges
■ Infrastructure and operations leaders often find that the steps required to deliver a successful
configuration management database are neither obvious nor standardized. This can cause high
failure rates for CMDB projects.
■ Establishing a change and configuration process framework before implementing a CMDB
project is a critical success factor that is often skipped by I&O leaders who fail in their CMDB
initiatives.
■ More than half of CMDB efforts become unmanageable, due to a lack of business alignment,
inappropriate scope or inadequate process rigor.
■ The cross-functional nature of CMDB projects and the varying levels of process maturity in IT
organizations cause conflicts of priority and approach that can cause delays in CMDB
implementation programs, due to differing stakeholder needs.
Recommendations
I&O leaders optimizing IT operations to drive business value should:
■ Choose high-quality configuration tools and data sources by identifying candidate resources,
selecting the most valuable sources and implementing basic controls.
■ Develop a roadmap for IT change and configuration management process improvements by
analyzing organizational goals, existing capabilities and process challenges.
■ Sequence improvement activities by assessing organizational maturity and by focusing on
efforts that most directly contribute to the vision and business value.
Introduction
Infrastructure and operations (I&O) leaders focused on optimizing IT operations to drive business
1
value are increasingly looking for help when planning an IT service view configuration management
2
database (CMDB) implementation. Processes and tools can be implemented individually; however,
dependencies emerge as cross-organizational use expands. These dependencies span people,
process, technology and information enterprisewide, making IT service view CMDB
3
implementations challenging.
I&O leaders need to use a structured approach to optimize the timing of activities (see Figure 1).
They can execute some of the projects on the road to an IT service view CMDB simultaneously,
such as discovery tool implementations and process automation. Other projects require IT change
and configuration management activities as a prerequisite to ensure success. This includes the
CMDB tool itself (see "Achieve the Integrated I&O Vision by Focusing on Information Exchanges").
Analysis
Choose High-Quality Configuration Tools and Data Sources
When starting an IT service view CMDB project, choose high-quality configuration tools and data
sources, and then augment them with targeted tool investments. These tools and data sources
create a starting point for planning, as recommended by industry process improvement and project
management frameworks. Meet this objective using a structured approach (see Figure 2).
Identify Candidates
Begin by benchmarking your configuration tools across all IT domains. Identify the types of data
and information that are included, then assess the accuracy and integrity. Scrutinize older data
sources, because they often contain older terminology and stale data. Exclude data sources with
poor data quality until the system owner corrects accuracy and integrity issues. Ensure that
effective discovery and federation techniques (such as automated discovery and defined data
models) are in place to confirm that the data from all sources is valid.
Select Sources
Identify the data sources that the IT service view CMDB will reference. Start with a subset of the
infrastructure that supports one or two critical IT services or applications. Focus on configuration
data sources that gather and log information relative to those IT services or applications. Conduct
inspections or use other data sources to verify all included data. Implement additional tools and
data sources only when information gaps cannot be addressed by your current capabilities.
Implement Controls
Implement a formal process and use automation to ensure consistent and repeatable configuration
changes to production. Define metrics for accuracy and completeness of the data, including
thresholds for removing data sources from the IT service view CMDB. Schedule regular reviews of
performance indicators to identify and correct issues quickly.
Determine which of the foundational processes to improve first by their alignment with business
goals. Implement IT change management improvements first to strengthen governance over change
requests and risk. Lead with configuration management improvements to enhance attribute data
quality. Ultimately, both processes are required, and I&O leaders must ensure that they are tightly
integrated to derive value from their IT service view CMDB investments (see Table 1).
Goal Reduce procedural errors Reduce IT system variation from approved states
Objective Standardize change prioritization and assessment Increase accuracy of IT component information
Challenge Limited visibility to true risk and impact Differing standards by technology issues
Automate change management activities to accelerate the request for change (RFC) life cycle,
including impact analysis, risk assessment, authorization, scheduling and the completion of
postimplementation reviews (PIRs). ITSSM tools provide most IT change management capabilities
and integrate with incident and problem management, as well as the IT service view CMDB (see
"Magic Quadrant for IT Service Support Management Tools"). Newer ITSSM tools also provide
functionality such as workflow, RFC documentation, analysis, scheduling and reporting.
If you have solid configuration data, use fact-based evaluations to obtain better results, compared
with using individual knowledge (see "Speed and Complexity Are Driving the Need for Effective
Configuration Management"). For example, comparing a server build to an image from an official
repository ensures that vital patches and updates are included. Without IT change management,
configuration drift will be extremely likely. This is due to changes to the production infrastructure
Increase the consistency of configuration management across functions and technologies. Identify
technologies and functions that have low visibility, and install policies, tools and scripting that can
provide a configuration baseline. Implement an initiative to unify separate configuration activities
under a single process that can establish relationships among systems. This will accelerate some
functions that have not focused on configuration and help other functions work more uniformly. This
also applies to the actual data used to describe configuration items (see "Four Steps to Optimize
Configuration Management Process and Tools").
Supplement this information with effective change management to provide a more-complete view
via approvals, schedule checks and risk assessments. Document each step of the process and
identify the roles and responsibilities required to create and leverage efficiencies across IT domains.
Establish a vision, maturity baseline and metrics prior to starting an IT service view CMDB project.
I&O leaders must define the vision for how the use of the CMDB will deliver business value. They
must then govern IT change and configuration management improvements to resolve cross-domain
process and architecture work efforts in service to this vision. This is particularly important for
configuration management before implementing a CMDB, due to the level of detail that can distract
stakeholders from business objectives.
Be patient with maturity improvement efforts. Gartner ITScore for I&O (ITSIO) research shows that it
takes considerable time (often more than a year in larger environments) to move from ad hoc
processes to a formalized framework (such as ITIL) for IT change and configuration management.
This includes staff training, process development and tool investments. (Consult "ITScore for I&O
"Speed and Complexity Are Driving the Need for Effective Configuration Management"
"Seven Steps to Select Configuration Item Data and Develop a CMDB Project That Delivers
Business Value"
"ITScore for I&O Analysis: Take Action Now to Improve Your Organization's Maturity"
"Well-Defined Duties of the Process Owner and Process Manager Are Critical Success Factors for
Service Improvement Programs"
Evidence
1 From2015 to 2016, there has been a 13% increase in Gartner client inquiries related to CMDBs,
change management and configuration management.
2 ITservice view CMDB tools maintain a near-real-time view of hierarchical relationships among their
configuration items. Four attributes define an IT service view CMDB: integration and federation,
reconciliation, IT service modeling and visualization, and synchronization.
3 Thisis the consensus of more than 30 Gartner client Peer Connect conversations with more than
170 comments and 9,000 views related to the topic of CMDBs. An example conversation can be
found here. All conversations were retrieved from Peer Connect on 16 December 2016.
4 Thisis based on more than 2,000 client CMDB inquiries that took place between August 2012 and
August 2014, in which fewer than 20% of all CMDB initiatives discussed with Gartner clients had
established metrics to determine the effectiveness of their CMDB data as it relates to project goals
(specific business benefits). A statistical evaluation of project success ratios for CMDBs with and
without these goals shows that CMDB projects with them are 130% more likely to be successful.
Corporate Headquarters
56 Top Gallant Road
Stamford, CT 06902-7700
USA
+1 203 964 0096
Regional Headquarters
AUSTRALIA
BRAZIL
JAPAN
UNITED KINGDOM
© 2017 Gartner, Inc. and/or its affiliates. All rights reserved. Gartner is a registered trademark of Gartner, Inc. or its affiliates. This
publication may not be reproduced or distributed in any form without Gartner’s prior written permission. If you are authorized to access
this publication, your use of it is subject to the Usage Guidelines for Gartner Services posted on gartner.com. The information contained
in this publication has been obtained from sources believed to be reliable. Gartner disclaims all warranties as to the accuracy,
completeness or adequacy of such information and shall have no liability for errors, omissions or inadequacies in such information. This
publication consists of the opinions of Gartner’s research organization and should not be construed as statements of fact. The opinions
expressed herein are subject to change without notice. Although Gartner research may include a discussion of related legal issues,
Gartner does not provide legal advice or services and its research should not be construed or used as such. Gartner is a public company,
and its shareholders may include firms and funds that have financial interests in entities covered in Gartner research. Gartner’s Board of
Directors may include senior managers of these firms or funds. Gartner research is produced independently by its research organization
without input or influence from these firms, funds or their managers. For further information on the independence and integrity of Gartner
research, see “Guiding Principles on Independence and Objectivity.”