comment on

... rework when the system is not yet deployed is always scrap...

I question that because:

... keep room for fixing bugs...

... and:

In a project you really need to do the "big design up-front", otherwise you'll have too much scrap, and nobody wants to pay that.

"Just plan harder so you don't write bugs" is hardly realistic.

(If you define "scrap" as "stuff you have to throw away because it has provided no value", then you have a circular definition you can only break by redefining "value". You get to pick what you rework: is it the BDUF spec several months later or is it code minutes to days later?)

Even if you want to embrace agile methodologies, you need to understand that the first release must be managed as a project, with a start, an end and a specific product to deliver.

Every reputable agile method of which I am aware suggests this explicitly.

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

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


No such thing as a small change
	PerlMonks