I think a distinction needs to be made between the director and the manager. The director is in charge of things like the budget and justifying that budget to the CEO. The director receives that justification from the manager. The manager is in charge of making sure projects are planned, requirements are gathered, and projects proceed apace. The manager receives the funding for that from the director. Beneath the manager should be the project manager (time coordination), development leads, etc ... and they report to the manager.

The director doesn't need any technical knowledge. It's good if the manager has knowledge of at least the development process.

If you're lucky, you can get someone who can be both director and manager. My experience has usually been that some poor schlob ends up having to be both, but is really only qualified for one. My best experiences, though, have been where the two hats were on different heads.

------
We are the carpenters and bricklayers of the Information Age.

Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose

I shouldn't have to say this, but any code, unless otherwise stated, is untested

In reply to Re: Making the Business Case for Developer-Run Development by dragonchild
in thread Making the Business Case for Developer-Run Development by etcshadow

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.