As Matt ("GreenMatt") noted, one of the resources is the Agile CMMI blog.
I am the author of that blog, and I'm also a CMMI appraiser, so, I can provide you with first-hand information on achieving CMMI levels while also incorporating agile practices.
Rob's response is correct, to a degree, but can also be taken the wrong way. Your processes must be known to you, which is more important (and different) from being "documented". You need to plan your processes so that you can manage them at maturity level 2. Also, your processes would need to be conducted in such a way that they are able to achieve certain goals that are listed in CMMI.
For Maturity Level 2 and Scrum, what's important is that you are truly following Scrum and are not leaving out the hard parts like: calculating velocity & using velocity to set sprint backlogs, setting sprint goals, and not disrupting the sprint in the middle, etc.
As Rob correctly pointed out, CMMI contains no processes. What CMMI does have are only practices to improve your processes. That means you do need to know your process in the first place or CMMI will only confuse matters.
Matt is right, it's not the CMMI makes things hard, it's just that poor uses of CMMI makes things hard. And, he's also correct that ML2 has little to do with the actual development and much more to do with running the project and managing scope. The bottom line is that CMMI and Scrum at ML2 is very easy together, as long as you are clear about how you're using both.
These are some of the tips I can easily provide in a forum like this. Feel free to look me up and get in touch for a more detailed conversation.
[soapbox] After being through CMMI certification at a few places, I'm not a fan. That said, neither am I one of those who say it is evil; I just think it is poorly applied or mis-applied more often than not. However, for some types of work it is required, even if it is not providing anything useful ... [/soapbox]
Anyway, none of the places I've worked have done Scrum and CMMI, so I can't tell of first hand experiences. (As Rob Goodwin submitted while I was typing my answer) CMMI doesn't tell you what to do, other than documenting your procedures and then following what your documentation says ... and documenting that! Fortunately, you can modify your procedure documents when necessary.
CMMI L2 deals mostly with project and configuration management; it doesn't have that much to do with the actual software development process (and in fact can be applied to non-software development work). Thus, as long as your documentation is kept in order and details what you are going to do with Scrum techniques (and you keep it up-to-date) you should be fine.
A couple resources I've seen during my CMMI experiences about blending Agile and CMMI are the Agile CMMI blog and Broadsword Solutions agileCMMI product. Not being well versed in either CMMI or Agile (we just sort of wing it where I am!), I don't know how good they are.
发布评论
评论（4）
正如 Matt（“GreenMatt”）指出的，资源之一是敏捷 CMMI 博客。
我是该博客的作者，也是一名 CMMI 评估师，所以，我可以为您提供有关实现 CMMI 级别同时融入敏捷实践的第一手信息。
罗布的回答在某种程度上是正确的，但也可能被错误地理解。您必须了解您的流程，这比“记录”更重要（并且不同）。您需要规划您的流程，以便能够在成熟度级别 2 管理它们。此外，您的流程需要以能够实现以下目标的方式进行： CMMI 中列出的某些目标。
对于成熟度级别 2 和 Scrum，重要的是您真正遵循 Scrum，并且不会遗漏诸如计算速度和速度之类的困难部分。使用速度来设置 sprint 待办事项、设置 sprint 目标以及不中断中间的 sprint 等。
正如 Rob 正确指出的那样，CMMI 不包含任何流程。 CMMI 所做的只是改进流程的实践。这意味着您确实需要首先了解您的流程，否则 CMMI 只会让事情变得混乱。
Matt 是对的，并不是 CMMI 使事情变得困难，而是 CMMI 的使用不当使事情变得困难。而且，他也认为 ML2 与实际开发关系不大，而与运行项目和管理范围关系更大，这一点也是正确的。最重要的是，只要您清楚如何使用两者，ML2 中的 CMMI 和 Scrum 就可以非常轻松地结合使用。
这些是我可以在这样的论坛中轻松提供的一些技巧。请随时查找我并与我联系以进行更详细的对话。
As Matt ("GreenMatt") noted, one of the resources is the Agile CMMI blog.
I am the author of that blog, and I'm also a CMMI appraiser, so, I can provide you with first-hand information on achieving CMMI levels while also incorporating agile practices.
Rob's response is correct, to a degree, but can also be taken the wrong way. Your processes must be known to you, which is more important (and different) from being "documented". You need to plan your processes so that you can manage them at maturity level 2. Also, your processes would need to be conducted in such a way that they are able to achieve certain goals that are listed in CMMI.
For Maturity Level 2 and Scrum, what's important is that you are truly following Scrum and are not leaving out the hard parts like: calculating velocity & using velocity to set sprint backlogs, setting sprint goals, and not disrupting the sprint in the middle, etc.
As Rob correctly pointed out, CMMI contains no processes. What CMMI does have are only practices to improve your processes. That means you do need to know your process in the first place or CMMI will only confuse matters.
Matt is right, it's not the CMMI makes things hard, it's just that poor uses of CMMI makes things hard. And, he's also correct that ML2 has little to do with the actual development and much more to do with running the project and managing scope. The bottom line is that CMMI and Scrum at ML2 is very easy together, as long as you are clear about how you're using both.
These are some of the tips I can easily provide in a forum like this. Feel free to look me up and get in touch for a more detailed conversation.
[soapbox] 在通过了一些地方的 CMMI 认证后，我不再喜欢它了。也就是说，我也不是那些说这是邪恶的人之一；我只是认为它经常被应用不当或错误应用。然而，对于某些类型的工作来说，这是必需的，即使它没有提供任何有用的东西...... [/soapbox]
无论如何，我工作过的地方都没有做过 Scrum 和 CMMI，所以我不能先说手经验。 （正如 Rob Goodwin 在我输入答案时提交的那样）CMMI 不会告诉您要做什么，除了记录您的程序，然后遵循您的文档所说的内容......并记录下来！幸运的是，您可以在必要时修改您的程序文档。
CMMI L2 主要处理项目和配置管理；它与实际的软件开发过程没有太大关系（实际上可以应用于非软件开发工作）。因此，只要您的文档保持有序并详细说明您将使用 Scrum 技术做什么（并且保持最新），您应该没问题。
在我的 CMMI 体验中，我看到了一些关于混合敏捷和 CMMI 的资源，包括 敏捷 CMMI 博客 和 Broadsword 解决方案敏捷CMMI 产品。由于不熟悉 CMMI 或敏捷（我们只是即兴发挥！），我不知道它们有多好。
[soapbox] After being through CMMI certification at a few places, I'm not a fan. That said, neither am I one of those who say it is evil; I just think it is poorly applied or mis-applied more often than not. However, for some types of work it is required, even if it is not providing anything useful ... [/soapbox]
Anyway, none of the places I've worked have done Scrum and CMMI, so I can't tell of first hand experiences. (As Rob Goodwin submitted while I was typing my answer) CMMI doesn't tell you what to do, other than documenting your procedures and then following what your documentation says ... and documenting that! Fortunately, you can modify your procedure documents when necessary.
CMMI L2 deals mostly with project and configuration management; it doesn't have that much to do with the actual software development process (and in fact can be applied to non-software development work). Thus, as long as your documentation is kept in order and details what you are going to do with Scrum techniques (and you keep it up-to-date) you should be fine.
A couple resources I've seen during my CMMI experiences about blending Agile and CMMI are the Agile CMMI blog and Broadsword Solutions agileCMMI product. Not being well versed in either CMMI or Agile (we just sort of wing it where I am!), I don't know how good they are.
CMMI 并不规定您的流程是什么，只是您有一些流程，它们被记录下来，并且您遵循它们。
CMMI does not dictate what your processes are, just that you have some, they are documented, and that you follow them.
这是一个 Scrum 工具：
http://www.firescrum.org/
Here's a tool for Scrum:
http://www.firescrum.org/