Search This Blog

Monday, September 24, 2007

Don't Be a Victim of Politics

Politics and projects go hand in hand. Team conflict, competing agendas, stakeholder dysfunction, resource constraints, and a myriad of other challenges exist and will send your project careening out of control if not managed properly.

What is a project manager to do? Here is a list of things to keep in mind when managing projects in a highly politicized environment:

Learn to negotiate from a position of strength

Do everything you can to educate those around you about Project Management. Stress the benefits and overcome the objections by pointing to your successes.

Master the art of influence.

Understand that masterful politicians are sometimes helpful to you and your project, but can also be detriment to your project's success.

An effective executive sponsor can help minimize political time wasting events that slow project progress and increase project budgets.

Recognize that conflict on your project is inevitable and necessary. How you respond to conflict will determine how successful you are.

Mastering the art of negotiation is a critical skill for project managers.

Negotiate up front how much power you will have as project manager, how and where it can be used, and when it applies to securing needed resources for your project.

Realize that for the most part internal politics wastes time and is usually not something that people enjoy.

Team commitment and loyalty will help to minimize project politics.

Don't fight a political system you don't understand and can't influence. Leave that to the experts. (Hint: get these experts to support your project if possible).

A good communications plan will help to lessen the politics on your project.

Every project usually has at least one "politician" in the organization that is out to either sabotage it, or will try to ensure that it isn't fully implemented.

Recognize that change (which is what projects are all about) scares some people and your project's deliverables can lead to a loss of power or influence for certain individuals or departments. Anticipate this and have a plan to deal with the behaviors that will surface.

Successful project managers need to learn to "swim with the sharks" and not get bitten. They need to be determined, focused, and act professionally and ethically. Project managers must know how to relate to people and manage relationships by being effective leaders and by applying the right balance of negotiating skills, motivational techniques, team building, and optimized communications.

Tuesday, September 11, 2007

Would You Like Cheese with that Whine?

Project teams are dynamic and interpersonal relationships amongst team members are always in a state of flux. Some teams are high performing and function at a high level over a long period of time. Other teams can't seem to come together and function at all.

An effective, experienced project team leader is an important part of any successful team, however, all team members must be personally accountable for their actions and be supportive of other team members if the team and project are to be successful.

Individual team member behaviors can contribute to team success in many ways. Emotional maturity and willingness to compromise are two important team member traits that help make a good team dynamic and lead to a successful project outcome.

Here are some negative team member behaviors I have personally observed. These behaviors detract from team synergy and place an unfair burden on other team members.

Projects fail or take longer than they should when team members:

Leave problems for others to solve rather than solving the problems themselves

Routinely blame others (stakeholders and/or other team members) or circumstances for not getting their tasks complete on time

Aren't personally accountable for their project task outcomes and timelines

Are unwilling to hold stakeholders accountable for their responsibilities

Aren't properly documenting their findings and defining a scope of work or adhering to an agreed-upon project scope

Aren't documenting Scope Change Requests

Aren't bringing issues and concerns to the team for discussion

Are constantly complaining, whining, and finger-pointing

Are unwilling to reach consensus with their team members

Are unwilling to let go of past negative circumstances and relationships

Are unwilling to admit past and current mistakes and learn from them

Play the victim and exhibit passive-aggressive behavior

Have a recurring theme in their dealings with others that everybody else is wrong and they are right

Continually demanding that things be done their way when it is contrary to the stated direction of the team

Team members who exhibit some or all of the above behaviors above should be placed on a performance improvement plan as their behavior is disruptive to the team and the project.

Project teams can't afford to have team members that aren't willing to compromise, are emotionally immature, and are a constant distraction to the team. In addition to being placed on a performance improvement plan, these team members should be released from the team as soon as possible as they are detriment to team cohesiveness and productivity.

Tuesday, September 04, 2007

The Good Project Manager

These are obvious, but you can never get enough good advice, right?

Show appreciation - thanking people for their assistance is not only the right thing to do it is expected.

Listen effectively - think before speaking. Listen attentively. Make the person feel like they are the only thing you are focusing on.

Give credit to others - always give credit where credit is due.

Don't be negative - negative people can kill team creativity. Eliminate them from your team if possible.

Have a work/life balance - don't forget that all work and no play makes for a dull life.

Don't have hidden agendas - they are only hidden for a while, and most people realize what you are doing.

Be willing to publicly admit your failures - there is nothing more pathetic than the person that never admits a mistake.

Talk about the problem not the person - don't personalize problems and make them about a person or group. Be willing to focus on only on the problem.

If you lie down with dogs you will get fleas - be careful of your relationships in the workplace. Trust, but verify.

Don't gossip - gossip can hurt careers and projects. Don't participate in gossip and don't allow it on your team.

Use Empathy not Sympathy when dealing with delicate issues - Empathic listening is listening with intent to understand. Sympathetic listening is a form of agreement and judgement.

Diagnose before your prescribe - if people don't have confidence in your diagnosis, they won't have confidence in your prescription

Keep your commitments and promises - enough said.

Remember while you are free to choose your actions, you aren't free to choose the consequence of those actions.

Monday, August 27, 2007

PMO Best Practices Checklist

Does your organization have a PMO? How is it going? If you are just starting a PMO review the checklist below and see if it makes sense for your group.

Identify the participants and their roles
Identify potential project team members as well as the major players in the user community that will test and except the final product or service. Ensure the Sponsor is engaged and has signed the Project Charter

Assign the project manager early
The Project Manager will make or break a project. Be sure the individual has the expertise to manage the project and they work well with others. Do not hesitate to look at outside sources if there is no one on staff that qualifies.

Assess the qualifications and experience of the planned project team members
Along with the project manager, assess carefully the qualifications and experience of each team member as they pertain to the specifics of this project. Keep in mind the importance of team players, and the ability to get along with others.

Conduct a project kickoff meeting
Officially start the project with a meeting of all parties involved. The project team should be introduced, the milestones reviewed with estimated completion dates, and expectations as to the level of participation, should be outlined.

Complete a detailed work plan
A preliminary work plan with major milestones should have been completed while developing the Requirements Document or Statement of Work. Now is the time to work with the project manager in identifying the tasks involved for each milestone. The work plan should list the tasks for each milestone with the estimated hours, start and stop dates, costs and responsible parties. Sample work plans and templates are available through the PMO upon request.

Establish an issues control tracking system
Establish a method by which, all issues pertaining to the project are recorded and can be reviewed regularly and tracked by the project team. All issues should eventually have a documented resolution.

Establish a regular project team review meeting schedule
Regularly scheduled project review meetings should be incorporated into the work plan. These meetings are to review the current progress of the project including the percentage of completeness of work plan tasks.

Establish a participant update meeting schedule
Periodic participant update meetings should be incorporated into the work plan. These meetings are to present the current progress of the project to upper management and major participants in the user community.

Follow your Work Plan, create and maintain an issues list, and
Track, Manage, and Obtain Approval for
ALL Scope Change
I didn't create the above checklist and don't know the original author.

Tuesday, August 14, 2007

Tom Peters and the Dozen Truths

I have posted before about Tom Peters before, and he is someone I really admire. In reviewing some of his materials I came across the "Dozen Business Truths" below. Mr. Peters isn't about doing things the way that have always been done. I like his approach to business and it fits right in with cutting edge project management practices.

Successful Businesses' Dozen Truths: Tom Peter's 30-Year Perspective

1. Insanely Great & Quirky Talent


2. Disrespect for Tradition

3. Totally Passionate (to the Point of Irrationality) Belief in What We Are Here to Do

4. Utter Disbelief at the BS that Marks "Normal Industry Behavior"

5. A Maniacal Bias for Execution and Utter Contempt for Those Who Don't "Get It"

6. Speed Demons

7. Up or Out. (Meritocracy Is Thy Name. Sycophancy Is Thy Scourge)

8. Passionate Hatred of Bureaucracy

9. Willingness to Lead the Customer... and Take the Heat Associated Therewith. (Mantra: Satan Invented Focus Groups to Derail True Believers)

10. "Reward Excellent Failures. Punish Mediocre Successes"

11. Courage to Stand Alone on One's Record of Accomplishment Against All the Forces of Conventional Wisdom

12. A Crystal Clear Understanding of Story (Brand) Power

Tuesday, July 31, 2007

Business Process Improvement and the Project Manager

Project managers need to ensure that customer's are satisfied with a project's deliverables.  Part of this process is ensuring that the customer's business processes are optimized.  You can't provide the best possible project results if your customer's processes aren't efficient.  Improving processes is about improving quality while reducing costs and waste. 

Processes need measures.  If you don't have measures then your processes aren't worth the paper they are printed on.  Processes have to meet the needs of the organization, business unit that executes them, and the customer's requirements.  Measures also help to identify and solve process problems, and help to ensure they are meeting the customer's requirements. 

When it comes to process improvement, a good project manager understands:

How to develop team skills

How to break down work into processes

How to solve problems and to find the root cause of  the problems

How to recommend solutions to problems that are acceptable to the majority

How to lead a team and when to let the team lead

Measure the effectiveness of a process by:

Looking at the cycle times between process steps

Identifying bottlenecks that cause unnecessary delays

Identify problems that cause defects to occur

In order to help develop good business processes, a project manager must have the knowledge, skills, and experience to ensure that the right people are doing the right things at the right time, using the right tools and delivering the results that are expected.

Thursday, July 26, 2007

Project Management Professional Responsibility Questions Part 2

As mentioned last week, a few years ago Frank Saladis and Al Zeitoun compiled a list of Project Management Professional Responsibility Questions. These questions are an example of what might appear on the the Project Management Institute's (PMI) Project Management Professional (PMP) exam. I posted the first fifteen questions last week, and the remainder are listed below.

Here is the second set of questions.  Comments are welcome. 

16. In order for the project manager to fully and effectively understand a stake holder's personal concerns or grievances it may necessary to:

  1. Ask for a written description of the problem and submit it through the project office
  2. Schedule a project review session with the entire project team
  3. Attempt to empathize with the stakeholder
  4. Involve the project sponsor as an arbitrator

17. As the leader of a project team, the project manager may be required to assess the competencies of his or her team members. Occasionally, some weaknesses or areas for improvement will be identified. The project manager should:

  1. Remove any team members who have demonstrated weaknesses in critical knowledge areas
  2. Communicate those weaknesses and establish a performance improvement program
  3. Hire additional resources to compensate for weak areas
  4. Wait for the team members to fail in an assignment to justify termination.

18. You have just changed jobs and discovered that your new employer routinely violates OSHA/EPA and affirmative action requirements on projects. You should:

  1. Do nothing; it's not your problem
  2. Start by asking management if they are aware that regulations are being violated
  3. Talk to the corporate legal department
  4. Inform the appropriate government agencies about the violations

19. The project manager must be an effective communicator to ensure that project stakeholders receive and understand project related information and status. Prior to delivering information to the stakeholders the project manager should attempt to:

  1. Research and understand the region of experience of the stakeholder before transmitting information
  2. Identify only those stakeholders that have a the same background experience as the project manager
  3. Filter the information to remove any details
  4. Restrict information to specific technical details

20. As part of your project plan you must develop an effective method of communication for your multinational team of stakeholders. You have several choices of media available. The appropriate action to take in the development of the communication plans would be to:

  1. Discuss the available options with the stakeholders and obtain their input
  2. Use the standard media that has been in effect for your previous projects
  3. Use multiple forms of media to ensure that everyone receives the information
  4. Obtain additional funding from the project sponsor and develop a project specific communications infrastructure.

21. One of your employees is up for promotion. If the promotion is granted, the employee will be reassigned elsewhere causing a problem for you on your project. You can delay the promotion until your project is completed. You should:

  1. Support the promotion but work with the employee and the employee's new management to develop a good transition plan
  2. Ask the employee to refuse the promotion until your project is completed.
  3. Arrange to delay the promotion until the project is completed
  4. Tell the employee that it is his responsibility to find a suitable replacement so that the project will not suffer.

22. The integrity of the project manager is often challenged by stakeholders who attempt to use personal power or influence to change the scope of an agreed upon deliverable. In these situations the project manager's most appropriate response would be:

  1. Refer the stakeholder to the process for change documented in the approved contract.
  2. Agree to the change because customer satisfaction is the goal regardless of cost.
  3. Contact the legal department and suspend all further project work
  4. Determine the risks and rewards for implementing the change before taking any action.

23. During project implementation the client interprets a clause in the contract to mean the he is entitled to a substantial refund for work recently completed. You review the clause and disagree with the client's conclusion. As the project manager which of the following actions should be taken

  1. Disregard the customer's conclusion and continue to process invoices
  2. Document the dispute and refer to the provisions of the contract that address interpretations and disputes
  3. Advise the customer that ambiguous information in contracts is always interpreted in favor of the contractor
  4. Immediately correct the clause to remove any possible misinterpretation by the customer

24. Your executives, in appreciation for the success of your project, have given you a $10,000 bonus to be disbursed among your five-team members. One of the five, who is a substandard worker and accomplished very little on your project, is in your car pool. You should:

  1. Provide everyone with an equal share
  2. Provide everyone a share based upon their performance
  3. Ask the workers to decide among themselves how the bonus should be subdivided
  4. Ask the sponsor to make the decision

25. Before reporting a perceived violation of an established rule or policy the project manager should

  1. Determine the risks associated with the violation
  2. Ensure there is a reasonably clear and factual basis for reporting the violation
  3. Ignore the violation until it actually affects the project results
  4. Convene a committee to review the violation and determine the appropriate response

26. Project Managers can contribute to their organization's knowledge base and to the profession of project management most effectively by:

  1. Developing and implementing a project review and lessons learned process
  2. Establishing strict guidelines for protecting intellectual property
  3. Promote the use of ad hoc project management
  4. Ensuring that all project plans are developed before the project team is formed

27. You have been assigned two concurrent projects. Because of the nature of the projects, you have a conflict of interest. You should:

  1. Do the best you can and tell no one
  2. Ask to be removed from one of the projects
  3. Ask to be removed from both of the projects
  4. Inform your sponsor and ask for his advice

28. You receive a contract to perform testing for an external client. After contract award, the customer provides you with the test matrix to use for your 16 tests. The vice president for engineering says that the customer's test matrix is wrong, and she will use a different test matrix, which should give better results. This is a violation to the SOW. You should:

  1. Use the customer's test matrix
  2. Use the engineering test matrix without telling the customer
  3. Use the engineering test matrix and discuss the reasons with the customer
  4. Ask your sponsor for clarification, assuming that the vice president is not your sponsor

29. An effective method for improving an organization's project management knowledge base is through:

  1. Coaching and mentoring
  2. Referent power
  3. A weak Matrix organizational structure
  4. Fast Tracking 
  5. Answer Key

    1=c    8=b    15=d  22=a

    2=d    9=b    16=c   23=b

    3=a    10=a   17=b  24=c

    4=a    11=c   18=b   25=b

    5=c    12=b   19=a   26=a

    6=b    13=b    20=a  27=d

    7=c    14=d    21=a  28=d