<?xml version="1.0"?><rss version="2.0">
<channel>
<title>AnthillPro Blog - Continuous Integration Maturity Model</title>
<link>http://www.anthillpro.com/blogs/anthillpro-blog/2009/05/05/continuous_integration_maturity_model.html</link>
<description>One of the great sessions of CITCON (Continuous Integration and Testing Conference) NA 2009, was a group effort to design a CI maturity model or road map. The session designed a maturity model for continuous integration server implementations.</description>
<language>en</language>
<managingEditor>Eric Minick</managingEditor>
<lastBuildDate>Fri, 11 Sep 2009 20:15:04 GMT</lastBuildDate>
  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  <item>
    <title>Enterprise CI Cultural Maturity</title>
    <link>http://www.anthillpro.com/blogs/anthillpro-blog/2009/05/05/continuous_integration_maturity_model.html#trackback1252700104544</link>
    <description>
      Today we offer a guest blog entry from Paul Julius. Paul extends the Enterprise Continuous Integration Maturity Model that Eric and I developed by bringing in an important missing element: Culture. As I started to use this model more and more, I realized ...</description>
    <author>AnthillPro Blog</author>
    <comments>http://www.anthillpro.com/blogs/anthillpro-blog/2009/05/05/continuous_integration_maturity_model.html#comments</comments>
    <guid isPermaLink="true">http://www.anthillpro.com/blogs/anthillpro-blog/2009/05/05/continuous_integration_maturity_model.html#trackback1252700104544</guid>
    <pubDate>Fri, 11 Sep 2009 20:15:04 GMT</pubDate>
  </item>
  <item>
    <title>Re: Continuous Integration Maturity Model</title>
    <link>http://www.anthillpro.com/blogs/anthillpro-blog/2009/05/05/continuous_integration_maturity_model.html#comment1248095967130</link>
    <description>
      And we followed up the webcast with a&lt;a href=&#034;http://www.anthillpro.com/html/resources/white-papers/view.html?id=1195436&#034;&gt;white paper&lt;/a&gt;.</description>
    <author>Eric Minick</author>
    <comments>http://www.anthillpro.com/blogs/anthillpro-blog/2009/05/05/continuous_integration_maturity_model.html#comments</comments>
    <guid isPermaLink="true">http://www.anthillpro.com/blogs/anthillpro-blog/2009/05/05/continuous_integration_maturity_model.html#comment1248095967130</guid>
    <pubDate>Mon, 20 Jul 2009 13:19:27 GMT</pubDate>
  </item>
  <item>
    <title>Indentify?</title>
    <link>http://www.anthillpro.com/blogs/anthillpro-blog/2009/05/05/continuous_integration_maturity_model.html#comment1246845826534</link>
    <description>
      Indentify sounds like a cool way to identify problem source code by adding a //TODO: comment and indenting the suspected problem code.

Probably, it&#039;s just a typo though.</description>
    <author>Dave Cameron</author>
    <comments>http://www.anthillpro.com/blogs/anthillpro-blog/2009/05/05/continuous_integration_maturity_model.html#comments</comments>
    <guid isPermaLink="true">http://www.anthillpro.com/blogs/anthillpro-blog/2009/05/05/continuous_integration_maturity_model.html#comment1246845826534</guid>
    <pubDate>Mon, 06 Jul 2009 02:03:46 GMT</pubDate>
  </item>
  </channel>
</rss>
