@bill_tribble Does it work?

Depends on the team. This probably won't prevent a good team from delivering product. Yet, this probably won't change a bad team to suddenly start performing.

But in all cases, this will allow some software development consultants and trainers to make their boat payments while allowing executives to feel involved with their engineering teams.

@grumble209 @bill_tribble And first of all it's about Teams of Teams working on the same thing.

It doesn't change that much on Team-Level, apart from additional meetings and perhaps 'normalzed' 🤦story points.

I've never seen it work, though.

@bbak @bill_tribble I've been in a couple of different software companies that decided CMMI certification was needed. As far as I can tell, the work we did rolling out the changes didn't make the low-performing teams perform any better; nor did the high-performing teams get any worse (or any better).

I'm left with:
- a shelf of CMMI books,
- the feeling that CMMI is mostly about keeping large companies from being challenged by smaller companies for DoD contracts, while allowing trainers and certifiers to make a living without actually writing code or managing projects,
- and the strong conviction that more time and money should be spent finding, hiring, growing, and keeping good people - strong process won't make up for weak people.

That said, I never read anything in the CMMI books that I objected to. It's all good information that wise developers and PMs should know and apply when needed.