I have read your SCRUM articles with great interest. I myself was once trained in eXtreme Programming but more recently every company has to SCRUM (another silver bullet?). So I Enjoyed your articles very much and it got me thinking as well:) However, what you wrote in you post is, IMHO, wrong.

Let me give an example. We developed a prototype to elicit and validate the requirements. Now that we know what we want we throw it away and redevelop it properly. We are happy to throw it away, although it sort of works and the look-and-feel is OK, the quality of the SW is very poor. Management on the other hand does not appreciate this, why throw something away that works? In fact if we would not throw it away, let's assume we were forced to keep it, we would have areal problem. It's basically exactly as moritz++ describes in his post: "The things that really devastate a project are things that should wind up in the scrap bin, but don't."

I don't think the "scrap rate" metric is very useful, maybe for some specific types of projects. If you do a lot of refactoring the scrap rate will probably be high and that's perfectly OK for many projects.

Cheers

Harry

In reply to Re: "Bah! Scrumbug!" (Lessons from the scrap-bin) by dHarry
in thread "Bah! Scrumbug!" (Lessons from the scrap-bin) by locked_user sundialsvc4

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.