While the title of this message may seem extreme, there are many times when it is relevant in project management. One example is in the area of requirements. Project requirements are always in written form. In the field of project management there is no such thing as a verbal project requirement.
The following text was taken from Chapter Twenty in the “Field Guide to Project Management”. The authors Francis M Webster, Jr. and Stephen D. Owens state, "the written document provides instructions, restates previous instructions, conveys importance to the message, and helps the project manager to cover their tracks".
The authors also make the point that that "e-mail isn't always enough and can get you in trouble faster and with more people". As we all know from experience, e-mail usually isn't given enough thought before it is sent which can lead to messages being misinterpreted and having unintended consequences.
A project manager that is doing his or her job will formally document all items that are important and relevant to supporting a project's objectives.
Tuesday, June 23, 2009
Wednesday, June 17, 2009
Twenty Good Life Tips
Give people more than they expect and do it cheerfully.
Marry a man/woman you love to talk to. As you get older, their conversational skills will be as important as any other.
Do not believe all you hear, spend all you have or sleep all you want.
When you say, "I love you", mean it.
When you say, "I'm sorry", look the person in the eye.
Be engaged at least six months before you get married.
Believe in love at first sight.
Never laugh at anyone's dreams. People who do not have dreams do not have much.
Love deeply and passionately. You might get hurt but it is the only way to live life completely.
In disagreements, fight fairly. No name-calling.
Do not judge people by their relatives.
Talk slowly but think quickly.
When someone asks you a question you do not want to answer, smile and ask, "Why do you want to know?"
Remember that great love and great achievements involve great risk.
Say, "Bless You" when you hear someone sneeze.
When you lose, do not lose the lesson.
Remember the three R's: Respect for self; Respect for others; Responsibility for all your actions.
Do not let a little dispute injure a great friendship.
When you realize you have made a mistake, take immediate steps to correct it.
Smile when picking up the phone. The caller will hear it in your voice.
Marry a man/woman you love to talk to. As you get older, their conversational skills will be as important as any other.
Do not believe all you hear, spend all you have or sleep all you want.
When you say, "I love you", mean it.
When you say, "I'm sorry", look the person in the eye.
Be engaged at least six months before you get married.
Believe in love at first sight.
Never laugh at anyone's dreams. People who do not have dreams do not have much.
Love deeply and passionately. You might get hurt but it is the only way to live life completely.
In disagreements, fight fairly. No name-calling.
Do not judge people by their relatives.
Talk slowly but think quickly.
When someone asks you a question you do not want to answer, smile and ask, "Why do you want to know?"
Remember that great love and great achievements involve great risk.
Say, "Bless You" when you hear someone sneeze.
When you lose, do not lose the lesson.
Remember the three R's: Respect for self; Respect for others; Responsibility for all your actions.
Do not let a little dispute injure a great friendship.
When you realize you have made a mistake, take immediate steps to correct it.
Smile when picking up the phone. The caller will hear it in your voice.
Wednesday, June 10, 2009
Snakes on a Project
Project managers must manage team dysfunction. Sometimes the dysfunction comes from the top (Sponsor, Steering Committee, Senior Management) and sometimes it comes from the project stakeholders and core team members (or the project manager). The project manager must be a motivator, and additionally must keep the team focused on the project’s objectives. Most importantly, the project manager must do all they can to ensure that negative or destructive elements are kept clear of their projects. Sometimes these negative elements (people) are called “project snakes”.
Project Snake Facts
Project snakes aren’t interested in you, your team, or your project’s success
Project snakes won’t confront you with an issue or problem
Project snakes are interested in feeding (their own needs and ego)
Project snakes operate one way – surprise attack!
Project snakes strike when you least expect it
Project snakes (almost always) operate alone
Project snakes have few if any real friends (except other snakes)
Project snakes wear pants and skirts
When you find out there is a snake present, ensure you expose him or her for what they are. When exposing the snake, make sure you do this in a way that won’t cost you or another person on your team their job.
Snakes are devious, sneaky, and often powerful. Remember, the snake is all about feeding their own appetite (ego). Hopefully, if you and your team continue to do the right things the snake will slither off to feed somewhere else.
Project teams are most productive when they have fun, trust each other, have commitment to the project’s objectives, embrace open communications, and are working in a culture where their opinion is appreciated and they are creating value.
Project snakes don’t care about people, teams, and most of all projects that don’t serve their narrow agenda. Project snakes are sneaky predators that feed on the weak. Beware of the snake!