Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask

Re: A Cautionary Rant

by stephen (Priest)
on Apr 10, 2001 at 07:04 UTC ( #71243=note: print w/replies, xml ) Need Help??

in reply to A Cautionary Rant

You might be interested in the book Anti-Patterns: Refactoring Software, Architectures, and Projects in Crisis. It's an excellent guide to the sort of debacles you describe.

(In what follows, I'm describing mostly what I've sworn to do after a bunch of experiences like yours. Customer results may vary.)

The only advice I have to offer on that kind of thing sounds cynical, but it's the best I can do: COVER YOURSELF. If someone fails to deliver something for you, send them an e-mail-- and CC your boss. Keep copious notes of every meeting, and if anything is agreed on in the meeting, send e-mails to all persons affected stating what was agreed upon, even if they were sitting right next to you when the agreement was made. Documentation can be your friend in performance reviews.

Also, it's best to figure out-- and keep notes on, in a safe place-- what each participant has to gain and lose by the project getting done on time. For example, the Server Administrator's career is not going to be helped if your project is a raging success, nor will it be hindered if it fails. People who aren't directly affected by the outcome of the project generally can't be depended upon to help it. The only thing to do is to MAKE their lives affected by the outcome.

Anyway, it was a very valuable rant. Wish I could ++ it twice.


Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://71243]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others romping around the Monastery: (5)
As of 2018-04-27 07:04 GMT
Find Nodes?
    Voting Booth?