Be Prepared
April 21, 2008 – 5:50 am by Andy Wergedal
We cannot totally predict what will happen during a project but we can be prepared for those eventuallities.
How would you handle the following:
What happens to the project if a Star gets hit by a bus (becomes incapable of work)?
What happens if you lose funding or the company is sold/bought?
What happens if the ”shared” repository/directory is deleted?
What happens if you get replaced?
What happens if the project priorities get changed?
What happens if you realize that you cannot complete the project on time, on budget, with the staff you have?
What happens if everyone (or their kids) gets sick? for a week?
What happens if the project Sponsor quits?
What happens if another project becomes the priority?
What happens if your political rival gets promoted and inherits your project?
What happens if someone offers you a better position with double the pay?
There is no right answer, except that you must prepare a list and have an answer to each of the questions on your list.
How do you know if your IT systems will be successful with real humans? Just ask three questions…
When you arrive at a new project, write down the names of the superstars. There will be 10-20% of the team are the high producers. You can identify them as the motivated participants that everyone talks to and works to gain their approval. Write down these names and watch the progress, growth and enthusiasm of these key stake holders. These are the stars of your project.
Why do projects fail? Management of resources and communication are the keys. When you find yourself in the difficult position of identifying a low performer, your job is to replace them. Hopefully they can better serve the team in a different role, but if not you must replace them. Can you afford the have the project fail because of this person? If this was war and you would all die, would this change your perspective? Give them another role or get them off the project.
Have you ever said, Just assign it to me and I will do it.? This is the classic mistake for a project manager. I like to view a project manager as the captain of a ship. The captain does not set the sails or turn the wheel. Their job is to make sure that the ship, its crew and cargo arrive safely at the destination. When the storm comes everyone turns to the captain for leadership and direction. This is accomplished by requiring the crew (or team) to do their jobs.
Yes and No.
Too many times we (PM’s) over think our tasks. We like to get into list organizing and reporting metrics because we are geeks. We are very comfortable reading our charts and graphs. We seek out the best formulas to use and metrics to show and validate our value. But, does this alone serve our clients? Does it add value to our discipline, or does it detract from the perception of a PMP? I submit that we (PM’s) need to simplify our process and procedures into the most basic terms.

Who is your client? As a contractor I am hired by a recruiting firm, who supplies me to a service integrator, who is delivering a project to their client. Confused? You bet, there are four different entities involved in the transaction.