As for me, I don't like it. I abide by it at work and it's generally a huge bottleneck for all projects. Many of the ideas the SEI proposes are good practice, and I have a feeling a lot of developers already follow them without knowing that they're part of any "process".
A bad implementation of CMMI at an organization only makes things worse. For example, the latest version of CMMI encourages us to engage in rapid feedback cycles with customers, which is great. But the system we're supposed to track when and how we did that is clunky and consumes time, to the point that you don't want to go talk to customers for fear of having to do more writing and documenation.
As for me, I don't like it. I abide by it at work and it's generally a huge bottleneck for all projects. Many of the ideas the SEI proposes are good practice, and I have a feeling a lot of developers already follow them without knowing that they're part of any "process".
A bad implementation of CMMI at an organization only makes things worse. For example, the latest version of CMMI encourages us to engage in rapid feedback cycles with customers, which is great. But the system we're supposed to track when and how we did that is clunky and consumes time, to the point that you don't want to go talk to customers for fear of having to do more writing and documenation.