From: "Randy Pulsifer" <[EMAIL PROTECTED]> > I whole heartedly concur with Chris. You haven't a prayer. Any project is > won or lost according to the scope of work document that is agreed upon > before you start. > As an aside on this point, there's a good book called something like "Death March" (Edward Yourdon, Prentice Hall, ISBN 0137483104) on managing projects and the first two chapters are 'Politics' and 'Negotiation'. It's a pity that these stages are where most projects fail, and yet they're the areas many programmers refuse to get into (or don't see as part of their jobs). Good negotiation skills will help your projects succeed with as much certainty as good programming skills, possibly more. This is often truer for permanent staff than contractors because you're often not provided with an opportunity to negotiate the project terms. It's therefore more important that you take the project back to the 'negotiation of terms' stage before accepting it.
Which is the other rule programmers are often not taught - your career success depends more on the projects you refuse than the ones you accept. And you always have the right to refuse a project, even if that refusal means walking out the door. We now return you to your scheduled programme. Chris Tutty -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
