As Matt ("GreenMatt") noted, one of the resources is the Agile CMMI blog.
I am the author of this blog, and I am also a CMMI evaluator , so I can provide you with first-hand information on achieving CMMI levels, as well as implementing agile practices.
Rob's answer is somewhat true, but may also be erroneous. Your processes should be known to you, which is more important (and different) from "documentation". You need to plan your processes so that you can manage them at the maturity level 2. In addition, your processes must be conducted in such a way that they can achieve the specific goals listed in CMMI.
For Maturity Level 2 and Scrum, it’s important that you really follow Scrum and don’t leave out such hard parts as: calculating speed and using speed to set the sprint lag, set sprint goals and not break the sprint in the middle, etc. .
As Rob pointed out correctly, CMMI does not contain processes. CMMI has only the practice of improving your processes. This means that you need to know your process first, or CMMI only confuses the questions.
Matt is right, it’s not CMMI that complicates the situation, it is just that poor use of CMMI complicates the job. And he will also correct that ML2 has little to do with actual development and is much more involved with project management and area management. The bottom line is that CMMI and Scrum in ML2 are very easy to integrate if you clearly understand how you use both.
Here are some of the tips that I can easily provide on a forum like this. Feel free to look for me and get in touch for a more detailed conversation.
Hillel
source share