Content deleted Content added
HeyElliott (talk | contribs) m Fixed citation |
HMSLavender (talk | contribs) m Reverted edits by 119.235.51.216 (talk) (AV) |
||
| (11 intermediate revisions by 9 users not shown) | |||
Line 3:
{{Use dmy dates|date=December 2019}}
{{Software development process}}
'''Capability Maturity Model Integration''' ('''CMMI''') is a process level improvement training and appraisal program. Administered by the '''CMMI Institute''', a [[subsidiary]] of [[ISACA]], it was developed at [[Carnegie Mellon University]] (CMU). It is required by many U.S. Government contracts, especially in [[software development]]. CMU claims CMMI can be used to guide process improvement across a project, division, or an entire organization.
CMMI defines the following five maturity levels (1 to 5) for processes: Initial, Managed, Defined, Quantitatively Managed, and Optimizing. CMMI Version 3.0 was published in 2023;<ref>{{cite web |title=CMMI Content Changes. Release: V3.0, 6 April 2023. |url=https://cmmiinstitute.com/getattachment/47a7c84e-472c-4f7f-a473-ddc21c6ae045/attachment.aspx |publisher=CMMI Institute}}</ref> Version 2.0 was published in 2018; ==Overview==
Line 29 ⟶ 31:
In March 2016, the CMMI Institute was acquired by [[ISACA]].
In April 2023, the CMMI V3.0 was released.
==Topics==
===Representation===
In version 1.3 CMMI existed in two representations: continuous and staged.<ref name=Go08/> The continuous representation is designed to allow the user to focus on the specific processes that are considered important for the organization's immediate business objectives, or those to which the organization assigns a high degree of risks. The staged representation is designed to provide a standard sequence of improvements, and can serve as a basis for comparing the maturity of different projects and organizations. The staged representation also provides for an easy migration from the SW-CMM to CMMI.<ref name=Go08 />
In version 2.0 the above representation separation was cancelled and there is now only one cohesive model.<ref>{{Cite web |url=https://www.cmmiinstitute.com/cmmi/model-viewer/appendices/a |title=CMMI Institute - Core Practice Areas, Categories, and Capability Areas |access-date=15 December 2018 |archive-date=16 December 2018 |archive-url=https://web.archive.org/web/20181216031208/https://www.cmmiinstitute.com/cmmi/model-viewer/appendices/a |url-status=dead }}</ref>
===Model framework (v1.3)===
<!-- (NB: this section moved from CMM, where it was irrelevant. It requires checking for relevance here in CMMI.) -->
{{
Depending on the areas of interest (acquisition, services, development) used, the [[process area]]s it contains will vary.<ref>{{Cite web|url=https://www.benlinders.com/tools/cmmi-v1-3-process-areas/|title=CMMI V1.3 Process Areas|website=Ben Linders|date=18 September 2023 }}</ref> [[Process area (CMMI)|Process areas]] are the areas that will be covered by the organization's processes. The table below lists the seventeen CMMI core process areas that are present for all CMMI areas of interest in version 1.3.
{| class="wikitable sortable"
Line 164 ⟶ 166:
</ref> These statistics indicate that, since 1987, the median times to move from Level 1 to Level 2 is 23 months, and from Level 2 to Level 3 is an additional 20 months. Since the release of the CMMI, the median times to move from Level 1 to Level 2 is 5 months, with median movement to Level 3 another 21 months. These statistics are updated and published every six months in a maturity profile.{{citation needed|date=November 2013}}
The Software Engineering Institute's (SEI) team software process methodology and the use of CMMI models can be used to raise the maturity level. A new product called Accelerated Improvement Method<ref>{{Cite web|url=https://resources.sei.cmu.edu/library/|title=SEI Digital Library|website=resources.sei.cmu.edu|date=9 February 2024 }}</ref> (AIM) combines the use of CMMI and the TSP.<ref>{{Cite web|url=https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=72816|title=TSP Overview|website=resources.sei.cmu.edu|date=13 September 2010 }}</ref>
=== Security ===
Line 183 ⟶ 185:
</ref> The median increase in performance varied between 14% (customer satisfaction) and 62% (productivity). However, the CMMI model mostly deals with ''what'' processes should be implemented, and not so much with ''how'' they can be implemented. These results do not guarantee that applying CMMI will increase performance in every organization. A small company with few resources may be less likely to benefit from CMMI; this view is supported by the process maturity profile (page 10). Of the small organizations (<25 employees), 70.5% are assessed at level 2: Managed, while 52.8% of the organizations with 1,001–2,000 employees are rated at the highest level (5: Optimizing).
Turner & Jain (2002) argue that although it is obvious there are large differences between CMMI and [[agile software development]], both approaches have much in common. They believe neither way is the 'right' way to develop software, but that there are phases in a project where one of the two is better suited. They suggest one should combine the different fragments of the methods into a new hybrid method. Sutherland et al. (2007) assert that a combination of [[Scrum (software development)|Scrum]] and CMMI brings more adaptability and predictability than either one alone.<ref>{{Cite web |
CMMI Roadmaps,<ref>{{Cite web|url=https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=8581|title=CMMI Roadmaps|website=resources.sei.cmu.edu|date=31 October 2008 }}</ref> which are a goal-driven approach to selecting and deploying relevant process areas from the CMMI-DEV model, can provide guidance and focus for effective CMMI adoption. There are several CMMI roadmaps for the continuous representation, each with a specific set of improvement goals. Examples are the CMMI Project Roadmap,<ref>{{Cite web|url=https://www.benlinders.com/2010/cmmi-v1-3-the-cmmi-project-roadmap/|title=CMMI V1.3: The CMMI Project roadmap|date=7 December 2010|website=Ben Linders}}</ref> CMMI Product and Product Integration Roadmaps<ref>{{Cite web|url=https://www.benlinders.com/2010/cmmi-v1-3-the-cmmi-product-and-product-integration-roadmaps/|title=CMMI V1.3: The CMMI Product and Product Integration roadmaps|date=14 December 2010|website=Ben Linders}}</ref> and the CMMI Process and Measurements Roadmaps.<ref>{{Cite web|url=https://www.benlinders.com/2010/cmmi-v1-3-the-cmmi-process-and-measurement-roadmaps/|title=CMMI V1.3: The CMMI Process and Measurement roadmaps|date=28 December 2010|website=Ben Linders}}</ref> These roadmaps combine the strengths of both the staged and the continuous representations.
The combination of the project management technique [[earned value management]] (EVM) with CMMI has been described.<ref>{{Cite web |title=Using CMMI to Improve Earned Value Management |url=https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=5957 |access-date=2022-06-30 |website=resources.sei.cmu.edu | date=30 September 2002 |language=en}}</ref> To conclude with a similar use of CMMI, Extreme Programming ([[Extreme Programming|XP]]), a software engineering method, has been evaluated with CMM/CMMI (Nawrocki et al., 2002). For example, the XP requirements management approach, which relies on oral communication, was evaluated as not compliant with CMMI.
CMMI can be appraised using two different approaches: staged and continuous. The staged approach yields appraisal results as one of five ''maturity levels.'' The continuous approach yields one of four ''capability levels.'' The differences in these approaches are felt only in the appraisal; the best practices are equivalent resulting in equivalent process improvement results.
Line 195 ⟶ 197:
* [[Capability Maturity Model]]
* [[Enterprise Architecture Assessment Framework]]
* [[People Capability Maturity Model]]
* [[Software Engineering Process Group]]
Line 205 ⟶ 206:
{{Commons category|Capability Maturity Model Integration}}
* {{official website|http://cmmiinstitute.com/}}
{{Carnegie Mellon}}
{{Software engineering}}
{{Authority control}}
[[Category:Maturity models]]
| |||