CM1-16 Maturity model and capability assessment (Capability Maturity Model Integration, CMMI)
Rates processes against staged levels, producing a maturity level or capability profile that shows where an organisation stands and what to improve.
What it does
Rates processes against staged levels to show where an organisation stands and what to improve. Artefact: a maturity level or capability profile.
When to use it
Use when a user asks how mature an organisation processes are against a reference model, or what the next level would require.
When it does not fit
Processes are not repeatable or not comparable to the reference model, or the organisation is small or agile.
Result format
The result is a table of processes with the staged level assigned to each and the reason for that level, followed by a maturity level or capability profile for the organisation as a whole. It names the processes to improve first.
Requirements on the material
| Property | Requirement type | Requirement |
|---|---|---|
| Content type | Always applies | requires=text |
| Unit of analysis | Always applies | requires=topic |
| Appraises source credibility | Applies in some cases | no |
Not restricted on: Structure, Variable types, Time structure, How the sample was chosen, Level of detail available, Number of sources, Whether sources can be joined, Amount of material, Known data problems, Producer interest, Source dependence, Origin, Document genre, Language, Personal information, Security classification, Licence.
| Minimum material | Evidence on each process named in the reference model, normally documents and interviews in a formal appraisal. Public evidence supports only a provisional rating. |
|---|---|
| Additional sources needed | reference structure |
| Not for (rules) | none |
| Not for (text) | Wrong choice when processes are not repeatable or not comparable to the reference model, or when the organisation is small or works in an agile way. The model says what processes should exist, not how to implement them. |
Choosing and ordering
| Kind of technique | Primary technique, runs in step 5.3 |
|---|---|
| Phase tag | analyse |
| Other phase tags | none |
| Kind of finding | gap; difference |
| Question answered | what |
| Strongest statement it supports | describe |
| Needs as input |
|
| Makes as output |
|
| Must exist first | None |
| Loop target | return to frame |
Library checks by stakes
Each stakes level includes the checks of the level below it. Checks that need a person apply at high stakes only, so the process leaves them out at lower stakes (decision 38). Repeatability: judgement dependent.
| Stakes | Check | Person involved | Counts as a different method |
|---|---|---|---|
| exploratory | assumption and limitation statement | none | no |
| decision-informing | assumption and limitation statement | none | no |
| decision-informing | source-span citation | none | no |
| decision-informing | spot check | optional | no |
| high-stakes | assumption and limitation statement | none | no |
| high-stakes | source-span citation | none | no |
| high-stakes | spot check | optional | no |
| high-stakes | expert review | needed | no |
| high-stakes | independent review | needed | no |
Failure modes and limits
| Model suitability | human judgement required |
|---|---|
| Typical model failure | Assigns a level from policy statements and marketing about processes instead of evidence of practice, and applies a software model to a non-software process. |
| Error sources | input data; source selection; coder or rater judgement; expert opinion |
| Certainty limits | Certainty drops when the rating rests on public documents only (indirectness), when practice was not observed (risk of bias), and when the reference model does not fit the organisation. |
Related techniques
- pairs with CM1-15 Gap analysis: the gap to the next level can be listed and prioritised
- should follow HE1-18 Document and policy analysis: documents are read systematically for stated practice before a level is assigned
Evidence and tag basis
Documented. The model says what processes should exist, not how to implement them, and results do not guarantee gains in every organisation. Generic non-software frameworks were not researched. (Wikipedia, Capability Maturity Model Integration)
Tag basis: input profile inference; selection inference; sequencing inference; robustness inference. All tag values are inference unless a source is named.