« CMDB data architecture confusion | Main | The fundamental purpose of Enterprise Configuration Management »

A new CMDB critic

Ron Palmer is joining the increasing ranks of CMDB critics and skeptics. He makes a number of good points about CMDB scope creep and lack of requirements, and lack of traceability to business value.

I notice a common theme in too many CMDB writings and that is a seeming lack of exposure to the practices of enterprise architecture, in particular data architecture. Many if not most of the problems being identified by the critics can be resolved by applying the same techniques to understanding the CMDB, that we would apply for any business facing system. You need a detailed and pragmatic process architecture, data architecture, and systems architecture, with traceability between them - stuff that is hard work to do. (Of course, I think that I have completed a credible first cut in my book.)

Until we have a common reference model, we're all just talking past each other.

-Charlie

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d8341bf8f153ef00d83572784e69e2

Listed below are links to weblogs that reference A new CMDB critic:

Comments

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment

Comments are moderated, and will not appear until the author has approved them.