Saturday, August 15, 2009
Friday, August 14, 2009
Dysfunction Junction
I have worked in, around and for IT organizations for most of my career, and it still amazes me how poorly these groups communicate. Why do IT departments believe they aren’t accountable? Why won’t they communicate and form real partnerships (not pretend relationships). Why doesn’t IT management realize that in regards to IT tools and services many times perception is reality? Look at just about any survey, most IT tools and services are rated poorly by those that pay for them. Why? My answer is poor project management practices delivered through a dysfunctional organization.
What Does Dysfunction Look Like?
When you go to meetings, pretend to listen then walk away and criticize those you just met with, that is dysfunction
When you pretend to trust others, but look for ways to poke holes in their beliefs, that is dysfunction
When you reward mediocrity…dysfunction
When you create something that has questionable value yet hold it up as something awesome….hyper-dysfunction
When you support and encourage weak "leaders" that cause upheaval and mayhem …you have dysfunction
When enterprise standards and processes are ignored…you guessed it…dysfunction
When commitments are made than ignored…yep…more dysfunction
When the people in ivory towers refuse to sit down with the commoners... dysfunction
When you reward your team for winning the silent “us vs. them” war… dysfunction is the winner (guess who is the loser)
When you allow a rogue manager to steamroll others inside and outside your department…you have dysfunction
When you treat your staff like mushrooms (in the dark)…you again have dysfunction
In closing…be real, be relevant, be a team player, and most of all be trustworthy. Nobody respects a talking head. You have to be visible, engaged and respected to be effective and relevant.
Remember, if you aren't visibile you aren't relevant and if you aren't relevant you aren't needed.
Monday, August 10, 2009
No Democracy for America!
In America we don't live in a Democracy, we live in a Republic!
Good Video explaining the difference.
Good Video explaining the difference.
Sunday, August 09, 2009
Thoughts on Talking
"Small minds talk about people, moderate minds talk about events and great minds talk about ideas" - Author Unknown. I could do a better job at this. It is very true statement.
Saturday, August 08, 2009
Weekend Break - Monolith on Mars!
THIS mysterious monument could be proof there was once life on Mars.
The rectangular structure — measuring five metres across — was photographed by a super high resolution camera on the Mars Reconnaissance Orbiter. The giant monolith juts out of the planet’s surface casting a huge shadow below. Its emergence on website Lunar Explorer Italia has got space buffs speculating if it could have been constructed by creatures once living on the red planet. The monument resembles the black monolith seen in Stanley Kubrick film 2001: A Space Odyssey.
In the movie the structure is believed to be a key to man’s evolution. And astonishingly Buzz Aldrin, the second man to walk on the Moon, revealed a similar monolith was detected on Mars’ moon Phobos. Speaking last week, he insisted: “We should visit the moons of Mars. “There’s a monolith there – a very unusual structure on this little potato shaped object that goes around Mars once every seven hours.
“When people find out about that they are going to say, ‘Who put that there? Who put that there?’”
Tuesday, August 04, 2009
Bad Project Theater
In earlier posts I have written about project failure and poor project management practices. In the IT world we all know that just because a project is seen as a failure doesn't mean that parts (or all) of that project aren't implemented. Many times egos in IT won't admit to project (product) failure, and end-users are stuck with crap systems that don't deliver anything approaching value. Sometimes these systems linger for years. Yikes, Help!
Project value can’t be dictated; it must be planned, agreed upon, and is easily recognized. We can't be told something has value. We must be shown and form our own opinions.
I have been a project manager in an IT/Telecomm environment for over twenty years. Failed IT projects aren't unique to any one industry or business segment. They are often a result of a mentality that says we know best, and we believe we are smarter than everybody else.
We can sum up this type of behavior in one word...Arrogance -
As taken from the Inner Frontier
ARROGANCE - "Those to whom much has been given sometimes suffer from arrogance; or rather the people around them suffer. Arrogance is doubly a pity, because the talents of the arrogant serve primarily themselves. The arrogant assumes his views and opinions are The Truth. In arrogance, natural confidence goes sadly awry. Rather than the self-assurance born of knowing his own strengths and limitations, arrogance admits no limits. The arrogant brooks no weakness in himself and may even secretly rejoice to find flaws in others. But imperfections are inherent in being human, so the arrogant, like everyone else, always has feet of clay, however well hidden they may be. Fearing exposure, haughtiness forms a hard shell masking inner emptiness."
Professional project managers are always honest, open, and ethical. They realize that project success is in large part determinded by the stakeholders and sponsor, not the project manager.
My advice is to (hopefully not arrogant) leave the drama, back door deals, and shady practices to others and be a valuable asset to your customers and sponsor.
Project value can’t be dictated; it must be planned, agreed upon, and is easily recognized. We can't be told something has value. We must be shown and form our own opinions.
I have been a project manager in an IT/Telecomm environment for over twenty years. Failed IT projects aren't unique to any one industry or business segment. They are often a result of a mentality that says we know best, and we believe we are smarter than everybody else.
We can sum up this type of behavior in one word...Arrogance -
As taken from the Inner Frontier
ARROGANCE - "Those to whom much has been given sometimes suffer from arrogance; or rather the people around them suffer. Arrogance is doubly a pity, because the talents of the arrogant serve primarily themselves. The arrogant assumes his views and opinions are The Truth. In arrogance, natural confidence goes sadly awry. Rather than the self-assurance born of knowing his own strengths and limitations, arrogance admits no limits. The arrogant brooks no weakness in himself and may even secretly rejoice to find flaws in others. But imperfections are inherent in being human, so the arrogant, like everyone else, always has feet of clay, however well hidden they may be. Fearing exposure, haughtiness forms a hard shell masking inner emptiness."
Professional project managers are always honest, open, and ethical. They realize that project success is in large part determinded by the stakeholders and sponsor, not the project manager.
My advice is to (hopefully not arrogant) leave the drama, back door deals, and shady practices to others and be a valuable asset to your customers and sponsor.
Thursday, July 30, 2009
I'm Worse for Having Known Them
I have recently been reminded that arrogance mixed with a little power can be destructive and divisive to an organization.
A good project manager must always rise above the this type of petty political partisanship and keeps fighting for what is right and best for the organization.
*** WARNING - FREE ADVICE BELOW ***
Never use fabrications, slander, and distortions to sell the value of your project/product
Never tear down another organization ( or person) to build yours (yourself) up
If you aren't visible you aren't relevant. If you aren't relevant you aren't needed
Never pretend to be something that you are not. You can only fool another fool
Never be so cocky as to believe you have nothing to learn from others
If you haven’t learned from the mistakes of the past you are probably already repeating them
If you are not honest, ethical, and trustworthy you can’t be effective at anything except politics
Taking others people's ideas and repackaging them as your own is pathetic, dishonest, and just plain sad
The value of your project’s product can only be judged by end-users, not you
Your reputation is determined by others, not you
Product bells and whistles rarely add value. They usually end up in a product because the designer was lazy and without imagination.
Surround and marginalize your critics. Don't let them define who you are.
Beware of Project Snakes and Sharks. They can wear pants or skirts.
Tuesday, July 28, 2009
Ambiguous Project Goals
Conflict and problems on projects often arise because of ambiguous project goals. You can’t achieve the goals on your project if they are not clear, agreed-upon, and communicated to all stakeholders. Ambiguous goals result in confusion and conflict.
Make sure that your project's goals are SMART (Specific, Measurable, Attainable, Relevant, Time constrained)
Make sure that your project's goals are SMART (Specific, Measurable, Attainable, Relevant, Time constrained)
Saturday, July 25, 2009
Friday, July 24, 2009
Tuesday, July 21, 2009
Successful Projects Bring No Recognition
When projects are successful, often nobody notices. Possibly the best measure of project success is that the project manager implements without fanfare or notoriety.
Success is the reward for lots of practice
Click Photo to Enlarge
Success is the reward for lots of practice
Click Photo to Enlarge
Thursday, July 16, 2009
Apollo 11 Lauch Video - I was there!
40 years ago today, as a member of my local Boy Scout troop, I was at Cape Kennedy (Canaveral) in Florida to witness the launch of Apollo 11.
What a project that must have been to work on!
What a project that must have been to work on!
Tuesday, July 14, 2009
Collaborate = Conflict?
When people collaborate there will sometimes be disagreement. Disagreement doesn't have to be a bad thing, and in many instances constructive disagreement can lead to a better solution. With that in mind, it is important for all participants in the conversation to recoginize when productive disagreement becomes destructive. When collaborating with others, a project manager has to be an expert negotiator to ensure that project communications are kept open, civil, and productive. While comprimising isn't the right answer when collaboarting, sometimes it is the only answer when consensus can't be reached.
Don't allow your project communications to deteriorate into pitty bickering and fighting. As the project manager it is up to you to keep project communications civil and productive. Be respectful of others and demand respect in return.
When managing conflict remember to:
Understand when a conflict is out of hand
Help to defuse emotions
Focus on questions that ask why, how, and what
Search for solutions together
Evalutate solutions that make sense and are agreeable
Don't allow your project communications to deteriorate into pitty bickering and fighting. As the project manager it is up to you to keep project communications civil and productive. Be respectful of others and demand respect in return.
When managing conflict remember to:
Understand when a conflict is out of hand
Help to defuse emotions
Focus on questions that ask why, how, and what
Search for solutions together
Evalutate solutions that make sense and are agreeable
Friday, July 10, 2009
Monday, July 06, 2009
Saturday, June 27, 2009
Thursday, June 25, 2009
My Project is Late Again!
Is is late because of...
Design Changes – Design changes during project execution almost always cause delays and impacts to your budget. Once the Scope document has been signed, any changes to the design need to go through your Scope Change Request Process.
Skill Sets – When planning, assumptions are made regarding people's skills. Sometimes these assumptions turn out to be wrong. Also, you will usually have people on your team who are new or are less experienced. These new or lower skilled workers won't be as productive or effective as higher skilled workers. Make sure your project plan has accounted for skill levels.
Unplanned Work or Workarounds – Many times changes must be made to the sequence of planned work. These changes can impact time, cost, budget, and quality. Think about these risks up front and discuss what if any workarounds will be used.
Rework – Rework happens; it is part of project management. Ensure your project plan accounts for rework.
Team Morale – Turnover, project conflict, sick time, vacations all can wreak havoc with your schedule and budget; plan for these things. A happy team is a productive team. Ensure your team is working towards a common goal and not working against each other. Remove disruptive team members from your project if their behavior can't be changed.
Schedules – Trying to do too much in too little time will result in delays. Once you get behind it is very difficult to catch up. Your project will have delays. You need to have contingency plans to get back on track quickly.
Work Environment – Ensure that your team has a proper workspace. Cramming people into poorly designed work spaces will lower productivity.
Tools – Ensure your team has the right tools to do the job. Having the right tool, but not getting into the teams hands at the right time will cause delays in your schedule.
Project Manager Overload – Too many people on a project team without the proper management oversight can cause major problems for the project manager.
Overtime – Adding hours to people's schedules in order to make a deadline will usually do nothing but increase your budget. Adding overtime rarely results in getting a late project back on track.
Executive – Executive apathy can kill your project. People are usually not going to make your project a priority if their boss isn't willing to tell them it is important. Deadbeat executives kill team morale and project momentum.
Plan for the above "risks" and you will start to bring your projects in faster, cheaper, and with higher quality.
Design Changes – Design changes during project execution almost always cause delays and impacts to your budget. Once the Scope document has been signed, any changes to the design need to go through your Scope Change Request Process.
Skill Sets – When planning, assumptions are made regarding people's skills. Sometimes these assumptions turn out to be wrong. Also, you will usually have people on your team who are new or are less experienced. These new or lower skilled workers won't be as productive or effective as higher skilled workers. Make sure your project plan has accounted for skill levels.
Unplanned Work or Workarounds – Many times changes must be made to the sequence of planned work. These changes can impact time, cost, budget, and quality. Think about these risks up front and discuss what if any workarounds will be used.
Rework – Rework happens; it is part of project management. Ensure your project plan accounts for rework.
Team Morale – Turnover, project conflict, sick time, vacations all can wreak havoc with your schedule and budget; plan for these things. A happy team is a productive team. Ensure your team is working towards a common goal and not working against each other. Remove disruptive team members from your project if their behavior can't be changed.
Schedules – Trying to do too much in too little time will result in delays. Once you get behind it is very difficult to catch up. Your project will have delays. You need to have contingency plans to get back on track quickly.
Work Environment – Ensure that your team has a proper workspace. Cramming people into poorly designed work spaces will lower productivity.
Tools – Ensure your team has the right tools to do the job. Having the right tool, but not getting into the teams hands at the right time will cause delays in your schedule.
Project Manager Overload – Too many people on a project team without the proper management oversight can cause major problems for the project manager.
Overtime – Adding hours to people's schedules in order to make a deadline will usually do nothing but increase your budget. Adding overtime rarely results in getting a late project back on track.
Executive – Executive apathy can kill your project. People are usually not going to make your project a priority if their boss isn't willing to tell them it is important. Deadbeat executives kill team morale and project momentum.
Plan for the above "risks" and you will start to bring your projects in faster, cheaper, and with higher quality.
Tuesday, June 23, 2009
What Is Not in Writing Has Not Been Said
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.
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.
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!