I read a similar NASA case-study a few years back when my employer jumped on the CMM band-wagon.

The folks that where pushing CMM emphasized the benefits including higher quality, lower costs, less reliance on key people, and so forth.

I read the CMM book published by Carnegie Mellon. The book didn't really speak much to the commoditization of "key people" but instead referenced a NASA case study

The NASA case study included many of the best practices used to produce the quality of software required by NASA. The case study discussed the costs required to achieve this level (CMM level 5) of quality. I don't have the book on hand, but there was a passage stating that NASA had spent a large amount of money assuring a level of quality in the code but was statistically certain that defects still existed in the code. However, finding and removing these defects would be cost prohibitive (a 100% increase in costs!).

I considered the NASA case study to be a fair, consistent piece of literature and far more realistic than most of the dogmatic slogans that I associate with CMM.

In conclusion, folks pushing 'process' up the management chain should provide all the information to the execs, not just the rhetoric.

In reply to Re: IT decisions are driven by business needs by beamsack
in thread IT decisions are driven by business needs by dragonchild

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.