Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery

Re^3: Nobody Expects the Agile Imposition (Part V): Meetings

by sundialsvc4 (Abbot)
on Dec 14, 2010 at 15:16 UTC ( #877099=note: print w/replies, xml ) Need Help??

in reply to Re^2: Nobody Expects the Agile Imposition (Part V): Meetings
in thread Nobody Expects the Agile Imposition (Part V): Meetings


If you have actually succeeded in “breaking the work down into small tasks,” it doesn’t really matter “who does what.”   The real issue, neatly avoided by all this quasi-sports talk, comes down to exactly two things:

  1. Are you correct in your breakdown of the tasks?
  2. Will the target ever change position, or otherwise change in any way at all?

Imagine, if you will, the task of shooting arrows at a target in a tornado.   Most of the arrows that you shoot are going to fly off course:   it doesn’t matter at all if, or how, you “track” those arrows.   Either the arrows were mis-aimed, or the target moved, or you somehow just wound-up with an arrow in your butt (but don’t quite know just how it got there...), or some combination of the three.

Or maybe you have a “magic arrow” that will zip this way and that, gradually “homing in” on that moving-target.   But, how long was the course taken by that arrow, and how many trees and other obstacles did it have to blast its way through on its magical, determined effort to “finally hit the target?”

An experienced marksman would wait for the tornado to pass.   She would size up the situation carefully, place herself at the position she had chosen, and fire one shot.   Only one.   And she would not walk up to the target to see if her arrow had done its job.

I say (and not without experience to back me up...) that, when you are actually ready to write software code, writing the code is easy.   After all, “the code” is simply an expression of the design ... the most-rigid and inflexible expression, but comprehensible to a digital computer.   This should be the last incarnation that your completed design will take, and you should delay putting it into that form as long as possible.

But of course, people who are paying a dreadful amount of money for something want to see “progress.”   And people who are working on that something, want to “progress.”   Building meticulous blueprints doesn’t feel like “building a house.”   And, Home Depot didn’t get to be a big, fat company by selling materials to people who draw blueprints.

(I don’t say this to be persnickety.   I say this as someone who has written more than three quarters of a million lines of source-code in about twenty programming languages... while silver-bullets came and went, and were in their turn discarded.)

  • Comment on Re^3: Nobody Expects the Agile Imposition (Part V): Meetings

Log In?

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

How do I use this? | Other CB clients
Other Users?
Others avoiding work at the Monastery: (4)
As of 2020-11-30 20:43 GMT
Find Nodes?
    Voting Booth?

    No recent polls found