Executive support is way at the top of the list. Along with that - having a good manager that will keep your projects in the minds of the executives and who can run interference is very important.

Next, change management (and I don't mean CVS) is critical if your project brings about a change. Remember all change is bad an everyone fears change. I'm involved in a project to consolidate web development. Talk about a jolt to the system. Change management for me includes talking to the stakeholders constantly to make them a part of the process - to hear their concerns and account for them in the project plan.

And then there is scope. Make sure everyone has a clear notion of the project's scope. Even if everyone hears the scope and all nod in agreement, there could be many different interpretations of what that scope was, so be as clear about the details and definitions as possible.

To have better control over a project, a good communications plan helps. I also like to have a single point of contact with the client. "All requests shall flow from Joe Client and no one else". You can't have 12 people all sending you different information and making independent requests.

In reply to Re: Non-Technical Factors by delegatrix
in thread Non-Technical Factors by artist

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.