CMMI position

Stefan Coetzeecreated 2026-05-12updated 2026-05-121 min readposition
Vault note, not reviewed against the source. Written in the knowledge vault on 2026-05-12 by models working with Stefan Coetzee and published as it stands, with private addresses, e-mail addresses and an employer name redacted. Check claims against the primary source before relying on them.

What it does well

  • Process maturity discipline — five levels durable framework.
  • Cybersecurity / sustainability dimensions in 3.0.
  • US DoD procurement signal.
  • Aerospace/defense recognition.

What it does poorly

  • Heavy implementation — full maturity Level 3+ substantial effort.
  • Bureaucratic reputation — CMM heritage.
  • Modern software practices (agile, DevOps) friction.
  • EU adoption limited vs US.
  • Procurement signal niche outside DoD-adjacent contexts.

Evidence

  • Strong adoption in US DoD contractor ecosystem.
  • Indian/offshore software services for export procurement.
  • v3.0 ramping adoption.

Personal calibration

  • For US DoD / aerospace clients: CMMI vocabulary expected.
  • For typical EU work: limited applicability.

See also