“The CMDB is my project. I’ll let you know when it’s done.”
This approach takes place far too often in IT organizations, and so do duplicate efforts toward the same goal, especially in larger, highly political organizations. While an approach like this is common for configuration management process development and implementing a CMS or CMDB, it can occur for other processes as well.
At the core, ITIL promotes the concept that IT is there to support the business through services. In order to provide these services, all of IT must work together, to ensure not only that the business needs are being met, but also that other processes and functions within IT are working together to support these business needs. No process or tool should be implemented in isolation — particularly configuration management. Configuration management and the CMS or CMDB are there to support all other processes. Therefore, all other processes must be considered in order to ensure that those process requirements can be met. While this is true for every process, it is particularly true for configuration management.
Related Course
ITIL Foundation
11 Common Mistakes of ITIL Foundation Newbies Series
- ITIL Newbie Mistake #1: Too Much Focus on the Processes
- ITIL Newbie Mistake #2: Certified and Done
- ITIL Newbie Mistake #3: Focusing on Processes First
- ITIL Newbie Mistake #4: Attempting a Project in Isolation
- ITIL Newbie Mistake #5: Developing a Service Catalog without Considering Business Needs