The five levels
- Initial — work happens. Sometimes well, sometimes not. Success depends on individual heroics.
- Managed — projects follow disciplined processes. Repeatable within a project, not across the org.
- Defined — organization-wide standards. Projects tailor from a defined baseline. Most enterprise IT operates here.
- Quantitatively Managed — process performance measured statistically. Predictable outcomes, not just disciplined ones.
- Optimizing — continuous, data-driven process improvement. Few orgs genuinely operate here.
↳ what CMMI is for
CMMI was designed to help large procurement orgs (originally DoD) tell which contractors could reliably deliver complex software. A "CMMI Level 5" certification was a procurement signal. The model is heavyweight by design — appropriate for large programs, often overkill for small teams.
Critiques
CMMI has fans and detractors. Fans: it created vocabulary for talking about organizational discipline. Detractors: higher levels can mean "more process" rather than "better outcomes," and Agile orgs explicitly reject the heavyweight ceremony of Level 4–5.
When PMs encounter it
Government, defense, healthcare, and large enterprise contracts often require CMMI Level 3+ from contractors. Software startups rarely care. Your career path determines whether CMMI vocabulary is essential (yes for federal contracting) or optional (mostly skippable for tech).