Successfully Implementing CMDB Projects | Debunking 7 Myths

Learn what makes a CMDB successful and get ahead of the critics

Introducing a CMDB is a major project. We have designed this white paper for you so that you don't have to make every mistake yourself. In addition to the 7 most common myths about the CDMB in the fact check, you will also receive

convincing arguments for your CMDB project
Important tips for planning your CMDB
Solutions for typical mistakes when setting up a CMDB

In our 25-page guide, you will receive valuable tips on how to set up a functioning CMDB in your company. Clear and entertaining.

Table of content

04	„We want a CMDB!“
04	A way out: the CMDB
05	Experience shows: a CMDB is always feasible
06	Do you have any questions or need help?
06	Myth #1: „Building a CMDB is impossible“
06	People are (mostly) not the reason for CMDB projects failing
07	The CMDB is not a data graveyard
07	The solution: quality over quantity
08	Good practice examples from the i-doit community
09	Identify problems
10	Myth #2: „A CMDB cannot be kept up to date“
11	Inconsistency leads to rejection
11	The solution: The Configuration Management Plan (CMP)
12	What does the CMP say?
13	Myth #3: „Documentation costs time and money“
13	The solution: automation and optimisation
14	Time and money savings through a CMDB
15	Communicate the added value and the CMDB becomes self-sustaining
16	Myth #4: „All available data must be in the CMDB“
17	How do the CMDB and Discovery work together?
18	When hyperlinks and references are not enough: Import strategies
19	Myth #5: „Discovery is sufficient for IT documentation“
19	How do the CMDB and Discovery work together?
20	The lifecycle in the CMDB
21	Myth #6: „It is sufficient when a trainee documents“
22	What skills (or roles) do you need for your CMDB project?
24	Myth #7: „The CMDB project simply runs alongside“
24	High complexity in CMDB projects
25	The internal CMDB project
25	Project plan? Waterfall? Agile?
26	Summary
28	Who we are

7 CMDB myths that you can forget in future

A CMDB? We tried that. It doesn't work!
If the CMDB project is not treated as a project, the CMDB is doomed to failure right from the start. The impression: building a CMDB is impossible. We will show you how to make the benefits for your entire company visible to everyone. New motivation for the project is guaranteed.

A CMDB cannot be kept up to date!
It is always a question of preparation. Create a plan for the right data, priorities and responsibilities with numerous expert tips. You will see: An up-to-date CMDB is not magic.

It only costs time and money
That's right! A CMDB initially means additional effort. Read the e-book to find out why it's still worth it and what potential savings your company can expect.

All data must be in the CMDB!
There are also several options here. Use our suggestions to find your "point of truth" - the right mix of different data sources for your company.

We have a discovery. That's enough for documentation.
That does sound tempting. But it will also lead to big problems. Would you like to know why Discovery does not replace a CMDB? And why Discovery and IT documentation complement each other perfectly. You'll find the answers in the e-book.

Let the trainee document. That's quite enough.
You can probably guess that this is not the best solution. Our e-book provides an overview of the necessary roles and responsibilities in a CMDB project.

Setting up a CMDB? We can do that on the side.
At the latest, once the project has failed, it will be recognized: It doesn't work "on the side". It is a project. A structured approach is important. We explain what you should pay attention to.

The 7 myths of CMDB projects

- How to set up a functioning CMDB

Learn what makes a CMDB successful and get ahead of the critics

Table of content

7 CMDB myths that you can forget in future

Download now