Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling

Re^5: "Bah! Scrumbug!" (Lessons from the scrap-bin)

by JavaFan (Canon)
on Dec 16, 2010 at 20:30 UTC ( #877545=note: print w/replies, xml ) Need Help??

in reply to Re^4: "Bah! Scrumbug!" (Lessons from the scrap-bin)
in thread "Bah! Scrumbug!" (Lessons from the scrap-bin)

It may happen more often in agile teams, but then there's less to "throw away", as they make small steps, and detect they're wrong earlier. If you first spend 6 months designing, then 6 months implementing, and it turns there's a flaw in the design and it's back to the drawing boards. It may have taken you a year to get to a case that needs scrapping, but there's a huge cost for that one time.

But still, it's not the same as scrapping metal. If you have a production line producing expensive, complicated cuts, doing the last cut wrong is expensive. The metal has to be scrapped, and the time spend so far is completely wasted. But coding isn't the same - there's no "scrap" in the sense of a complete wasted effort. As Thomas Edison said "I have not failed. I have found 10000 ways that do not work". Taking a decision (whether it's in the design phase, or in the coding phase) that turns out to not work, does have value. You now know what doesn't work.

One may argue that a baby that keeps falling over is wasting effort: it should spend a few months studying how people walk, then walk on its first try. But babies don't. They try. They fail. They learn from failure. In the end, they walk.

  • Comment on Re^5: "Bah! Scrumbug!" (Lessons from the scrap-bin)

Replies are listed 'Best First'.
Re^6: "Bah! Scrumbug!" (Lessons from the scrap-bin)
by ruoso (Curate) on Dec 17, 2010 at 10:01 UTC

    Except you are not considering the baby a "walk consultant" and you are not paying the baby to deliver a "walk method".

    Again, the problem is not in the bugs, is not on the risks, but on the neglected requirement analisys of what the first release should be. I've seen too many so-called agile teams work the first release in "sprints" and have each of those sprints point to different directions because the initial requirement analisys for the first release was neglected, since it wouldn't fit the "two months"/"two weeks"/"whatever"

Re^6: "Bah! Scrumbug!" (Lessons from the scrap-bin)
by sundialsvc4 (Abbot) on Dec 20, 2010 at 01:53 UTC

    (Blink!)   Did you actually hear yourself?   “Six months designing...” (Then...)   “Six months implementing...”

    Obvious question:   Heavens to Betsy!   Just how many “Six Months” does it take?” . . .

    Inquiring Minds want to Know ...

    Thomas Edison might quite-plausibly be excused;   after all, no one had invented a Light Bulb before.   But, let’s face it... “by now, we are supposed to know what-the-hell we are doing!”

    I mean...   even in the worst possible of conditions, our dear CMC Machine Shop does not have to tell Boeing, “so sorry, Boss, see you next year!”

    “Jimminy Cricket ... we do need to deliver!”   This is Engineering, after all ... isn’t it?

      This is Engineering, after all ... isn’t it?
      No. And programming isn't baking, nursing or farming either. Or piloting. Or dentistry. Or archeology.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://877545]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others exploiting the Monastery: (6)
As of 2021-01-20 03:50 GMT
Find Nodes?
    Voting Booth?