Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
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.

stephen


In reply to Re: A Cautionary Rant by stephen
in thread A Cautionary Rant by footpad

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

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

How do I use this?Last hourOther CB clients
Other Users?
Others drinking their drinks and smoking their pipes about the Monastery: (5)
As of 2024-03-29 13:58 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found