Blog Entry
Search
Shameless Plugs
Most Popular
Who's online
User login
3385
Top 10 Reasons a CMDB Implementation Fails
Published on behalf of Tobin Isenberg
Here are a few of the most common reasons that CMDB implementations fail. They are in no particular order.
- 1. Lack of Management Buy-in
- 2. Owner of CI’s do not have easy access
- 3. Garbage in, garbage out (and/or stale data)
- 4. Lack of third party Integration
- 5. 100% or NOTHING
- 6. Hard to search/find things
- 7. Over designed/engineered Schema
- 8. One Stop Shopping
- 9. Bottom Up = WRONG approach
Okay, for those of you not counting, I only listed 9, in the comments below… give me your 10th one. Don’t be shy, share a 10th one or a funny story about one.
Tobin
What is your view of Configuration Management?
Come read the additional commentary from Tobin:
Business Service Management Hub
Top 10 Reasons a CMDB Implementation Fails - Business Service Management Hub
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.
Related Articles
User Comments
- mhudnall's blog
- Be the first to comment! To leave a comment you need to Login or Register
- 3385 reads
0