...for software project management. I heard these on a recent episode of .NET Rocks titled "Pat Hynds On Why Projects Fail" (skip to around the 13:00 minute mark - are the intros long enough on this show or what??).
- Status - if you're not paranoid earlier, you're going to be unhappy later.
- Never Assume - always make sure requirements are clear between you and the customer.
- Don't Be Wishful
- a project is not done until after the coding is done and lots of
other things happen. When asked if a project is done, you should be
able to definitively say "Yes" or "No" (without any "Yes... but...."
responses). You must confirm with the customer that the project is done.
- No Spec, No Estimate - many people want a fixed-bid price when they give a time and materials spec. Make sure that a detailed spec is given by the client. Include what will not be done.