proomt

Search

Search posts, papers, and topics

All posts

CodeshipErik Francis6 min readintermediate

Is CMMI Dead Yet? If Not, Can It Be?

Read on cloudbees.com

Summary

This article argues that CMMI (Capability Maturity Model Integration) is an outdated and ineffective methodology for software development. It contends that CMMI's focus on institutionalized process devalues individual talent, stifles innovation, and has failed to prove its worth in the broader technology space.

  • CMMI aims to institutionalize process to reduce reliance on individual talent, but this often leads to mediocrity.
  • Imposing process uniformity across teams stifles high-performing teams and can deter top talent.
  • The model devalues individual skill and talent, treating developers as fungible laborers rather than skilled professionals.
  • CMMI has not been chosen by the market over decades, with Agile frameworks dominating the modern software landscape.

Software engineering leaders and practitioners should understand why highly prescriptive process models like CMMI are often detrimental to innovation, team autonomy, and talent retention in modern development environments.

6/10
careermanagementsoftware developmentopinionagileprocess

Related reading

  1. Why Releasing Software as an Application Beats Deploying Components

    This article argues that independent microservice deployments, while seemingly fast, often lead to complex and fragile releases due to environment drift and implicit dependencies. It advocates for "application-level releasing," where a consistent, validated snapshot of interdependent components is promoted together across environments to restore predictability and stability.

    Codeshipcloudbees.com5 min

  2. Should you read the code, is RAG dead, and did Skills kill MCP?

    The article debunks five common AI‑tool hot takes, arguing you still must read AI‑generated code, AI fluency matters in hiring, MCP and Skills serve different purposes, RAG remains useful, and needing fine‑tuning signals a messy codebase. It offers concrete rules for reviewing generated code and integrating AI components responsibly.

    GitHub Oldgithub.blog5 minHN3

  3. Presentation: Complexity and Creativity in Software Engineering

    Phillip Mortimer argues that AI‑generated code makes all software effectively "write‑only" due to volume, and proposes managing this by treating tests as the sole specification, automating code reviews with LLMs, and decoupling intent from implementation.

    InfoQinfoq.com28 mintalk

  5. A New Framework for Open Source AI

    Mozilla and partners published a paper proposing a layered, gradient openness framework for foundation models, defining openness for data, code, weights, docs, and deployment. The framework gives developers, regulators, and civil society a common language to evaluate openness and safety beyond a binary label.

    Mozilla Automation Teammozilla.org3 min