<?xml version="1.0"?>
<rss version="2.0.">
  <channel>
    <title>Advogato blog for Marooned</title>
    <link>http://www.advogato.org/person/Marooned/</link>
    <description>Advogato blog for Marooned</description>
    <language>en-us</language>
    <generator>mod_virgule</generator>
    <pubDate>Thu, 24 Jul 2008 21:59:09 GMT</pubDate>
    <item>
      <pubDate>Wed, 31 Oct 2001 12:02:36 GMT</pubDate>
      <title>31 Oct 2001</title>
      <link>http://www.advogato.org/person/Marooned/diary.html?start=0</link>
      <guid>http://www.advogato.org/person/Marooned/diary.html?start=0</guid>
      <description>My company just started with the company wide 
implementation of the &lt;a href="http://www.sei.cmu.edu/cmm/cmm.html" &gt; CMM &lt;/a&gt; 
practices. Which means a lot more documentation, more task 
lists, more reports, more forms to be filled, rigid 
templates  and in general more structure to whatever we 
have been doing The thing is supposed to add to the 
profitibilty of the company and bring
in some order. We always had followed the practice of 
writing good documentation and following plans, but working 
to some particular model like CMM, is some sort of working 
in bounds. Have any of the people worked within such 
environments. Would like to know the benefits as well as 
the disadvantages.</description>
    </item>
  </channel>
</rss>
