Cmme has no direct relationship with PMBOK and is also a model in different fields. However, with the in-depth application of project management in various industries, in particular, the rapid development of project management in the software industry in recent years. therefore, understanding the differences and relationships between CMMI and PMBOK is also necessary to understand these process models and better apply them to software project development and management.
First, let's take a look at the differences between the two in terms of process model development.
Cmme is based on the practice of practice. It is mainly used in the software industry in the form of Capability Maturity level. the purpose is to guide the organizations that apply the model to perform the overall process evaluation (Evaluation & Assessment) and improvement (Improvement) of the entire organization ). maturity level indicates the capability of the process.
PMBOK is based on knowledge points and proposes five process stages of project management from a general perspective. Its purpose is to take project management as a scientific discipline and introduce the knowledge fields of this discipline.
Second, the structure is different
Cmme is composed of two representations (), five maturity levels, five capability levels, 25 process domains, several practices and sub-practices.
PMBOK is described in nine knowledge fields and five process stages.
Third, the coverage scope is different.
Cmme includes Software Capability Maturity Model (SW-CMM)/system engineering capability model (SECM)/Integrated Product Development Capability Maturity Model (IPD-CMM)/supplier sourcing (SS) and so on.
PMBOK is applicable to the project management field and does not include engineering content. Therefore, PMBOK is universal in the industry.
Of course, in terms of project management, some of the PA and PMBOK in cmme are basically the same. The following table gives a clearer description.
PMBOK |
CMMI Pa |
Overall management |
PP Project Plan IPM Integrated Project Management |
PMC project management and monitoring |
Scope Management |
Reqm requirement management requirement Management |
Progress Management |
-> PMC/QPM |
Cost Management |
-> PMC/QPM |
Quality Management |
Ppqa process and product quality assurance Ver Verification Val Validation |
Human Resource Management |
Ot organizational training Training Management and GP 2.5 (generic practice) (not very match) |
Communication Management |
IPM Integrated Project Management (not very match in cmme model, but cmme have enough practice content in almost all PAS for this knowledge. |
Risk Management |
Rskm Risk Management |
Procurement Management |
Sam supplier Contract Management supplier agreement management ISM integrated supplier management |
From the above table, we can see that almost all the knowledge domains in PMBOK have appropriate PA maps in CMMs. Of course, CMMS contains more content, some contents may be described in all the PA of CMMs.