Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things
 
PerlMonks  

Comment on

( #3333=superdoc: print w/ replies, xml ) Need Help??

This is always a difficult part of software development to pin down, and it's certainly not anything they taught in school when I was there. You might as well ask a team of a dozen writers to write a novel. Yeah -- think of the odd looks you'd get -- but it's true, a piece of software is a lot like a novel, with characters, plots, background, themes, and so forth.

As you've pointed out, managers seem to think software projects are just like plowing a field -- more people means the job gets done faster. But writing software is not like that at all -- it's creative work, and certain architecture rules need to be followed.

Rather than an inverse curve, the people/throughput curve is probably U-shaped, with a sweet spot at 6-12 developers. Any more than that, and a project should be split into sub-projects. Formal meetings should be held only when absolutely necessary, and ideally they'd be stand up affairs. No speeches. Discuss, deliberate, decide, then move on. To quote Boone Pickens, ".. Don't fall victim to what I call the ready-aim-aim-aim-aim syndrome. You must be willing to fire."

I believe the key to success in a software development project is communication -- with good communication, the project moves forward on the right track, with development and testing working in paralell. Without it, there are endless meetings, long memos, stagnant development, and eventually, angry customers. The best developers in the world cannot overcome poor communications.

Alex / talexb / Toronto

"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds


In reply to Re: OT: The mythical man month - have we learned nothing? by talexb
in thread OT: The mythical man month - have we learned nothing? by EdwardG

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!
  • 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, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • Outside of code tags, you may need to use entities for some characters:
            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.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others scrutinizing the Monastery: (13)
    As of 2014-12-22 20:56 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      Is guessing a good strategy for surviving in the IT business?





      Results (130 votes), past polls