As you complete this roadmap you will be defining your target state for configuration management. This will help ensure that your eventual CMDB implementation is right-sized to match your organization's capabilities and objectives. You will document the following in order to develop a roadmap:

  • Business drivers that impact IT.
  • IT drivers for investing in a CMDB.
  • Processes that will be supported by your CMDB.
  • A technology target state appropriate for your organization.
  • A roadmap of initiatives that will be executed to achieve your CMDB target state.
  • A cost and benefit breakdown of each initiative on your roadmap.
  • Success metrics that will be used to track and measure the success of your CMDB after it is implemented.

Also In

Create a Configuration Management Roadmap

A CMDB is only as valuable as the processes it supports.

Related Content

Hide Details

Search Code: 76428
Published: November 13, 2014
Last Revised: November 13, 2014


  • Missing comment
    Andres Calderon | 10-09-2018

    Configuration Management is defined as the management of baselines, this content is not Configuration is related to the CMDB which is the Configuration Management Database...a very different thing according to all frameworks out there (ITIL, COBIT, NIST, etc.)

    • 432c05244a845caaca3b276adb15a11e comment
      Info-Tech Research Group | 10-16-2018

      Thank you for your comment. The Configuration Management Roadmap on our site refers to IT Service Management-based configuration management capability, which supports a number of processes and outcomes within the Service Management space. There is an upcoming revision to the blueprint that will cover it in more detail.

      This is described within ITIL (in Service Transition – maintaining information about Configuration items used to deliver an IT services including their relationships) and COBIT (as a strategic capability in BAI10 – Manage Configuration). NIST, while identifying the establishment of baselines as an aspect of configuration management, also confirms its use for controlling, tracking, and managing aspects of business development and operations (which from an ITSM perspective would include services, products, technology, and associated processes).

      The type of configuration management you are referencing is much more closely aligned to software configuration management, which has a definite focus on maintaining baseline, but does not extend that to identifying relationships and dependencies.


Get Access

Get Instant Access
To unlock the full content, please fill out our simple form and receive instant access.
Visit our COVID-19 Resource Center and our Cost Management Center
Over 100 analysts waiting to take your call right now: 1-519-432-3550 x2019