The whole approach in this stage is to clearly state what is needed for your CMDB.
In earlier step, you gathered data through phases that put up to a business case that was accepted by the PEB and project stakeholder. In this phase, you will team up with crucial stakeholders to document and get authorization on their precise subset of requirements for each step. These users include process and functional owners that will influence the CMDB, as well as those accountable for compliance and organizational asset management.
You will also document CI-level requirements that require what CI associations will be sustained, including associations for CIs that constitute the IT service model.
Each stage comprises of definite goals that you should accomplish before moving forward. You may want to use the subsequent points as a checklist.
Classify and Analyze Governance Requirements
Objective: A CMDB can support a range of compliance activities in organization. Pinpoint organizational and IT governance standards and regulatory compliance processes that you want to advance with the CMDB project, and present the CMDB requirements.
Analyze and Select Supporting Best Practices
Objective: Begin with the IT practices that you have targeted for enhancement, by using the benefits of the CMDB and find best practices that these IT processes can use. You can speed up the accomplishment of the probable benefits associated with the process improvements by referencing industry best practices.
Classify Requirements to Support Potential Problems
Objective: Classify problems faced on previous CMDB projects and refer to the experience gained into project requirements. Many possible operation and support oriented issues can be avoided with a little work at this phase.
Classify Inventory and Asset Requirements
Objective: Summarize how inventory and asset management requirements will have impact on the CMDB project. Asset, inventory, and configuration management are related, but dissimilar enough to call out precise requirements.
Describe Service Catalog Requirements
Objective: Classify requirements that stipulate how the service catalog will support the associations between services and the basic CIs. Knowing which CIs align to a specific service allows you to better meet SLAs and enables you to calculate service-based costing.
Describe CMDB Requirements to Enable Other Processes
Objective: Convert IT process key points along with other IT tasks into precise requirements. The requirements must reveal how other groups will work together with the CMDB and any prioritized requirements these groups have.
Describe Configuration Item Level and IT Service Model
Objective: Describe the optimal level for CIs — both service CIs and infrastructure CIs — in your CMDB. This step helps regulate the overall scope and penetration of the structure of your CMDB data model.
Develop IT Service Model Proposal
Objective: Create the IT service model plan using the requirements you have recognized for the service catalog, the IT industry processes, and the IT service model plan. Present to the PEB for consent.
Using facts, you will describe the exact CI attributes that will be warehoused in the CMDB. You will then compile all the various accepted requirements into a complete requirements document that you will put forward to the PEB for final consent.
To end with, you will interpret the requirements into an associated IT service model plan which you will put forward to the PEB for consent.
Author : Arunavo Banerjee
27 FEB 2019RACI Matrix: How does it help Project Managers?