CMMI Controversies

Stefan Coetzeecreated 2026-05-12updated 2026-06-081 min readcross-cutting
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.

Bureaucratic reputation

CMM heritage produces bureaucratic-implementation perception:

  • "CMMI Level 3" often documentation-heavy.
  • Process discipline can become process ceremony.
  • DevOps / agile practitioners often skeptical.

Implementation cost

Levels 3+ require substantial investment:

  • Process documentation.
  • Training.
  • Internal audit infrastructure.
  • Appraisal fees.
  • Ongoing maintenance.

Smaller orgs disproportionately burdened.

Procurement signal narrow

US DoD-adjacent strong; broader procurement weak:

  • EU procurement rarely references CMMI.
  • Tech-native orgs typically don't ask.
  • Indian / offshore services-export-driven.

Agile / DevOps tension

Historical CMMI predates agile:

  • v3.0 addresses but tension remains.
  • Pure-agile orgs find CMMI rigid.
  • Hybrid implementations sometimes awkward.

ISACA acquisition trajectory

Since 2017 ISACA ownership:

  • Direction depends on ISACA priorities.
  • Some practitioners concerned about commercialization.
  • Cost dynamics changing.

Counterpoint

  • Genuine process maturity framework.
  • Defense and aerospace recognition real.
  • v3.0 modernizations material.
  • Capability-level approach (vs maturity) flexible.

See also