Do I need to meet an exact level when assessing a process using COBITs maturity models, and does this differ from the original CMM approach?
The main purpose of the COBIT maturity models is to give management a tool to help them better understand the current capability of IT management processes, do benchmarking, gap analysis and improvement planning. With COBIT’s maturity models, unlike the original SEI CMM approach, there is no intention to measure levels precisely or try to certify that a level has exactly been met. It is also not strictly true in COBIT that a lower level must be fully complied with before higher levels of maturity can be reached, as in CMM. A COBIT maturity assessment is likely to result in a profile where conditions relevant to several maturity levels will be met, as shown in figure 1. This is because when assessing maturity is often the case that some implementation is in place at different levels even if it is not complete or sufficient. These strengths can be built on to further improve maturity. For example, some parts of the process can be well defined and, even if the process is incomplete, it wo
Related Questions
- Do I need to meet an exact level when assessing a process using COBITs maturity models, and does this differ from the original CMM approach?
- How would use of the predictive models differ from the current way of assessing swimming safety?
- How does the level of software process maturity affect Project Management?
