<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Foundation Series: CMMI Levels Explained</title>
	<atom:link href="http://tynerblain.com/blog/2006/03/10/foundation-series-cmmi-levels-explained/feed/" rel="self" type="application/rss+xml" />
	<link>http://tynerblain.com/blog/2006/03/10/foundation-series-cmmi-levels-explained/</link>
	<description>Software product success.</description>
	<lastBuildDate>Thu, 18 Mar 2010 20:39:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2006/03/10/foundation-series-cmmi-levels-explained/comment-page-1/#comment-534739</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Wed, 04 Nov 2009 01:51:59 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/10/foundation-series-cmmi-levels-explained/#comment-534739</guid>
		<description>Funny!</description>
		<content:encoded><![CDATA[<p>Funny!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger L. Cauvin</title>
		<link>http://tynerblain.com/blog/2006/03/10/foundation-series-cmmi-levels-explained/comment-page-1/#comment-534242</link>
		<dc:creator>Roger L. Cauvin</dc:creator>
		<pubDate>Sun, 01 Nov 2009 17:03:32 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/10/foundation-series-cmmi-levels-explained/#comment-534242</guid>
		<description>I remembered this blog entry when I saw Jerry Weinberg post the following tweet:

&quot;Maturity Models Have It Backwards http://amplify.com/u/qy0&quot;</description>
		<content:encoded><![CDATA[<p>I remembered this blog entry when I saw Jerry Weinberg post the following tweet:</p>
<p>&#8220;Maturity Models Have It Backwards <a href="http://amplify.com/u/qy0" rel="nofollow">http://amplify.com/u/qy0</a>&#8220;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2006/03/10/foundation-series-cmmi-levels-explained/comment-page-1/#comment-374452</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Tue, 20 May 2008 21:51:39 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/10/foundation-series-cmmi-levels-explained/#comment-374452</guid>
		<description>Hey Justin,  thanks for commenting, and welcome to Tyner Blain!

I&#039;m not quite sure how you connect the superstars who make things happen with the wounded princes who feel threatened by change.  Regardless, thanks for the link to the article.  I love it when someone (in any context) appreciates that people trump process (and mergers)!</description>
		<content:encoded><![CDATA[<p>Hey Justin,  thanks for commenting, and welcome to Tyner Blain!</p>
<p>I&#8217;m not quite sure how you connect the superstars who make things happen with the wounded princes who feel threatened by change.  Regardless, thanks for the link to the article.  I love it when someone (in any context) appreciates that people trump process (and mergers)!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Burrows</title>
		<link>http://tynerblain.com/blog/2006/03/10/foundation-series-cmmi-levels-explained/comment-page-1/#comment-373074</link>
		<dc:creator>Justin Burrows</dc:creator>
		<pubDate>Sat, 17 May 2008 15:55:10 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/10/foundation-series-cmmi-levels-explained/#comment-373074</guid>
		<description>Nice point about the Superstars in Level 1. It reminded me of an article on forming alliances that referred to these &quot;Superstars&quot; as &quot;&lt;a href=&quot;http://findarticles.com/p/articles/mi_qa6206/is_199807/ai_n24336249&quot; rel=&quot;nofollow&quot;&gt;wounded princes&lt;/a&gt; (which meet an unwholesome end). That put a different take on it for me.</description>
		<content:encoded><![CDATA[<p>Nice point about the Superstars in Level 1. It reminded me of an article on forming alliances that referred to these &#8220;Superstars&#8221; as &#8220;<a href="http://findarticles.com/p/articles/mi_qa6206/is_199807/ai_n24336249" rel="nofollow">wounded princes</a> (which meet an unwholesome end). That put a different take on it for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Francis Ip</title>
		<link>http://tynerblain.com/blog/2006/03/10/foundation-series-cmmi-levels-explained/comment-page-1/#comment-92249</link>
		<dc:creator>Francis Ip</dc:creator>
		<pubDate>Sat, 28 Apr 2007 21:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/10/foundation-series-cmmi-levels-explained/#comment-92249</guid>
		<description>CMMI is not just for software engineering or IT, it also includes systems engineering. There was a SW-CMM, but it was retired and replaced by CMMI.

CMMI is compatible to ISO9000-2000. ISO9000-2000 is the certification for meeting international standard in quality management by an enterprise. CMMI defines the best practices, at each level, for enterprise processes. When a company is certified at level 5 of CMMI, many large organizations (e.g. US Department of Defence - the largest purchaser of technologies, services, and products in the world) accept the bids from that company immediately, without reference check, if the prices are right.

By the way, Systems Engineering is the discipline that oversees all activities carrying out by other professional disciplines (IT and Software Engineering included) over the product life cycle of every product from inception to disposal. US Air Force was the original sponsor of CMM and CMMI. The Defence and Aerospace industries are now also active stakeholders of CMMI, but US DoD remains the key stakeholder. A representative from US DoD signs every release of CMMI. The prime reason for having CMM and CMMI is that many products and systems are software intensive. US DoD wants its suppliers not only ISO9000-2000 certified but also at least CMMI Level 3 and EVMS certified! EVMS (Earned Value Management System), an international project management standard for reporting and measuring project progress, is one of the quantitative managed processes in Project Management. There is a signed agreement between US, UK, Canada, Australia, and New Zealand on EVMS standard. When a company gets EVMS certified in one country, other countries recognize the certification.

The attempt in matching the levels in CMMI against RMM is an interesting academic exercise, but it compares apples and oranges. Moreover, Requirements Management is one set of processes within CMMI!</description>
		<content:encoded><![CDATA[<p>CMMI is not just for software engineering or IT, it also includes systems engineering. There was a SW-CMM, but it was retired and replaced by CMMI.</p>
<p>CMMI is compatible to ISO9000-2000. ISO9000-2000 is the certification for meeting international standard in quality management by an enterprise. CMMI defines the best practices, at each level, for enterprise processes. When a company is certified at level 5 of CMMI, many large organizations (e.g. US Department of Defence &#8211; the largest purchaser of technologies, services, and products in the world) accept the bids from that company immediately, without reference check, if the prices are right.</p>
<p>By the way, Systems Engineering is the discipline that oversees all activities carrying out by other professional disciplines (IT and Software Engineering included) over the product life cycle of every product from inception to disposal. US Air Force was the original sponsor of CMM and CMMI. The Defence and Aerospace industries are now also active stakeholders of CMMI, but US DoD remains the key stakeholder. A representative from US DoD signs every release of CMMI. The prime reason for having CMM and CMMI is that many products and systems are software intensive. US DoD wants its suppliers not only ISO9000-2000 certified but also at least CMMI Level 3 and EVMS certified! EVMS (Earned Value Management System), an international project management standard for reporting and measuring project progress, is one of the quantitative managed processes in Project Management. There is a signed agreement between US, UK, Canada, Australia, and New Zealand on EVMS standard. When a company gets EVMS certified in one country, other countries recognize the certification.</p>
<p>The attempt in matching the levels in CMMI against RMM is an interesting academic exercise, but it compares apples and oranges. Moreover, Requirements Management is one set of processes within CMMI!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2006/03/10/foundation-series-cmmi-levels-explained/comment-page-1/#comment-352</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Sun, 12 Mar 2006 15:54:41 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/10/foundation-series-cmmi-levels-explained/#comment-352</guid>
		<description>Thanks Roger - I haven&#039;t read that piece yet.  They do raise a great point - that it&#039;s easy to lose sight of the goal.  I think of the wide receiver who focuses too much on running and avoiding tackles and fails to catch the ball.

Doing the job is most important, getting better at doing it is secondary.

Most of the people I&#039;ve worked with are either overly focused on tactical execution, and fail to catch the ball, or they are rabidly intent on catching the ball, and then they get tackled immediately.  The first group never scores, the second group scores less frequently.

CMMI can be used most effectively as a means to provide benchmarking of internal improvements, it shouldn&#039;t be the driver of change.  Achieving a particular CMMI level is not valuable.  Having a process that would be measured at a CMMI level is valuable.

Thanks!</description>
		<content:encoded><![CDATA[<p>Thanks Roger &#8211; I haven&#8217;t read that piece yet.  They do raise a great point &#8211; that it&#8217;s easy to lose sight of the goal.  I think of the wide receiver who focuses too much on running and avoiding tackles and fails to catch the ball.</p>
<p>Doing the job is most important, getting better at doing it is secondary.</p>
<p>Most of the people I&#8217;ve worked with are either overly focused on tactical execution, and fail to catch the ball, or they are rabidly intent on catching the ball, and then they get tackled immediately.  The first group never scores, the second group scores less frequently.</p>
<p>CMMI can be used most effectively as a means to provide benchmarking of internal improvements, it shouldn&#8217;t be the driver of change.  Achieving a particular CMMI level is not valuable.  Having a process that would be measured at a CMMI level is valuable.</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger L. Cauvin</title>
		<link>http://tynerblain.com/blog/2006/03/10/foundation-series-cmmi-levels-explained/comment-page-1/#comment-351</link>
		<dc:creator>Roger L. Cauvin</dc:creator>
		<pubDate>Sun, 12 Mar 2006 13:35:17 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/03/10/foundation-series-cmmi-levels-explained/#comment-351</guid>
		<description>I like what Demarco and Lister have to say about CMM in &lt;i&gt;Peopleware: Productive Projects and Teams&lt;/i&gt;.  Some quotes:

&quot;The paradox of the CMM is that process improvement is good, but process improvement programs aren&#039;t, or at least they often aren&#039;t.&quot;

&quot;When process improvement (as in &#039;Level 3 by the end of the year!&#039;) becomes the goal, the scary projects get put onto the back burner.  It&#039;s those scary projects, unfortunately, that are probably the ones most worth doing.&quot;

&quot;Organizations become more and more averse to risk as they &#039;mature&#039;.  An organization under the gun to demonstrate increased CMM level is not going to go looking for a real challenge.&quot;

&quot;The projects most worth doing are the ones that will move you DOWN one full level on your process scale.&quot;

And finally:

&quot;Identifying an ideal practice, or at least a &lt;i&gt;candidate&lt;/i&gt; ideal practice, is a useful endeavor.  But the programs that mandate such a practice are something else entirely.&quot;</description>
		<content:encoded><![CDATA[<p>I like what Demarco and Lister have to say about CMM in <i>Peopleware: Productive Projects and Teams</i>.  Some quotes:</p>
<p>&#8220;The paradox of the CMM is that process improvement is good, but process improvement programs aren&#8217;t, or at least they often aren&#8217;t.&#8221;</p>
<p>&#8220;When process improvement (as in &#8216;Level 3 by the end of the year!&#8217;) becomes the goal, the scary projects get put onto the back burner.  It&#8217;s those scary projects, unfortunately, that are probably the ones most worth doing.&#8221;</p>
<p>&#8220;Organizations become more and more averse to risk as they &#8216;mature&#8217;.  An organization under the gun to demonstrate increased CMM level is not going to go looking for a real challenge.&#8221;</p>
<p>&#8220;The projects most worth doing are the ones that will move you DOWN one full level on your process scale.&#8221;</p>
<p>And finally:</p>
<p>&#8220;Identifying an ideal practice, or at least a <i>candidate</i> ideal practice, is a useful endeavor.  But the programs that mandate such a practice are something else entirely.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
