The 10 Project Rules
- No major project is ever installed on time, within budget and with all the same staff. (Yours will not be the first!!!)
- Projects progress rapidly until they reach 90% completion. They remain at this stage forever.
- Fuzzy project objectives let you avoid the embarrassment of estimating corresponding costs.
- When things are going well, something will go wrong.
- When things cannot get any worse, they will.
- When things are going better, you have overlooked something.
- If project content changes too freely, the rate of change will exceed the rate of progress.
- No system is ever bug free. Attempting a bug free system introduces new ones even harder to find.
- Project teams hate progress reports because it vividly shows their lack of progress.
- A carelessly planned project will take 3 times longer to complete. (A carefully planned project will only take twice as long!)
Now find out the Ten Ways To Spot A Project in Trouble! Should you be worried?
Ten Ways To Spot A Project in Trouble!
- Your project team only gives you good news at every status meeting.
- The go live date is only a few weeks away but you, the programme manager, have never seen a hands-on demonstration of the applications or systems.
- Most of the e-mails your project team sends to you complain about the lack of skills in the other team members.
- Team members continue to play the fine act of protecting themselves at every opportunity.
- Team members are resigning at every opportunity.
- Team members are either frustrated or constantly on edge or, conversely, feel no pressure to get the job done.
- The project has already missed several deadlines and is well over budget.
- There has been no detailed walk-through of the project solution by independent reviewers.
- When you think of your project, there is no thought of team, but only separate individuals.
- The “user community” is not even aware of the existence of the project.