RESPECT – How NOT to be the Rodney Dangerfield of Project Management

Do you go around saying “I get no respect!”?  Project managers who say they are not getting respect usually mean that their comments, warnings, suggestions, and requests do not change the behavior of those they work with and for. Perhaps that is true. However, it is also possible that the power distribution scheme in your company is not setup to recognize or utilize the contributions of project management.  

Sixty or seventy years ago, when your parents or grandparents began working for corporations, the internal organization—and power structure—was setup around product groups and profit centers. Each group had a manager responsible for all activities and personnel necessary to get a product out the door and to make a profit. Product managers were respected.

Then in the 1980’s and early 1990’s, large corporations started merging into giant corporations. Lockheed, Martin, and Loral became one company; Boeing and McDonnell Douglas were married, Citi merged or acquired Traveler’s Insurance, Smith Barney, Salomon Brothers, The Associates and many more. To ensure that the mergers made financial sense, these mega-organizations looked for ways to cut costs. Within the product-oriented organizational structure, they found (OH NO!) duplication of functions. To the rescue came the “matrix organization” (You can read a description of this in chapter 2 of the 4th Edition PMI PMBok Guide).

In a matrix organization, groups are put together based on functions or skills. This organization style means that project managers are often in reality project facilitators with only informal control over personnel. They must rely upon the functional managers for project resources.

To receive respect in a matrix organization and to achieve the goals of your project, you need to utilize some of the same behaviors and attitudes discussed in previous posts such as Working with Support Organizations and The Accidental Project Manager Part 2. However, there is more to gaining respect than getting along. You must:

  1. Know where the power lies. Managers within the functional organizations wield the power to assign resources and establish priorities. To gain their respect takes research, insight into motivation, and time. One useful strategy is to figure out how to help them by offering advice and information they can use to do their jobs.
  2. Know your job and back up your requests and assertions with data. Give trust, but more important BE TRUSTWORTHY.
  3.  Keep your relationships “adult-to-adult” within the matrix. Adults negotiate; strive for consensus, resolve conflicts, and respect each other’s opinions according to Paula K. Martin, CEO of Martin Training Associates.
  4. Don’t play childish games. Here are a few games—interactions with ulterior motives—from Eric Berne’s classic transactional analysis book, Games People Play that you should avoid:
    • “Why don’t you…yes, but”
    • “Ain’t it awful”
    • “I’m only trying to help you”
    • “If it weren’t for you”
    • “Look what you’ve done to me”
  5. Ask for help. People, including the managers within a matrix organization, are more likely to respect the person who asks for their help in getting a job done than they are to respect someone who acts as if they have all the answers.  The trick to making this strategy work and increase the respect you receive is to be sincere.

    I am not suggesting you learn to fake sincerity. I am saying you really have to want to know how to get Group A to do what you need done for your project. If you have failed in the past to gain respect or support, start your discussion with an admission about the past, followed by the request to learn how to do it better.

  6. Be professional.  Even when you are being treated with no respect and others are playing games, you should be professional and respectful in your actions and attitude.  While this may not seem to work in the short term, it has huge long-term benefits. 

I am sure readers of Fear-No-Project would appreciate your experiences in successfully gaining respect for you and your project within a matrix organization. Please share via comments.

Good Project Plan Schedules

I had a great conversation this week about one of my earlier posts on creating effective and predictive project schedules.  It appears this subject is one of the common topics used in the maturity models being utilized these days.  So I thought I would give another perspective on creating a good project schedule.

Project schedules are essential tools to manage a project effectively – and when constructed correctly they also provide a predictive view of that schedule. Creating a schedule requires the PM to breakdown tasks into manageable parts, establish relationships among tasks, ensure that deadlines can be met, and assign sufficient resources to tasks. Here are some guidelines about project plan schedules from authoritative project management sources.

According to the Project Management Institute (PMI) in the accepted Body of Knowledge for Project management (PMBOK)

Project plan development uses the outputs of the other planning processes, including strategic planning, to create a consistent, coherent document that can be used to guide both project execution and project control. This process is almost always iterated several times. (PMBOK 4.1.3, pg. 44)

The PMBOK further states:

The project plan is a document or collection of documents that should be expected to change over time as more information becomes available about the project. (IBID)


Also, according to the Software Engineering Institute’s (SEI) Capability Maturity Model® Integration (CMMI), Version 1.1, Project Management is a key part of the maturity process and has two key areas for project plans considered areas for achieving the higher levels of maturity: 

  • Project Planning – Goal 1: Establishing Estimates, Goal 2: Developing a project plan.
  • Project Monitoring and Control – Goal 1: Monitoring the Project against Plan

To create a Project Plan schedule that meets all of the standards of a mature project schedule, both as defined in the PMBOK, the CMMI v1.1, and as widely accepted by Professional, certified project managers, should contain at a minimum these 10 items:

  1. Sufficient level of detail (Work breakdown and task sizes)
  2. Defined resources (Named)
  3. A complete network of dependencies (Adequate hard logic)
  4. Specific assignments (Resources against tasks)
  5. Sufficient use of milestones (Includes all Deliverables)
  6. Plan baselines (A static copy of the “plan” against which measures can be taken)
  7. Few constraints on tasks (Constraints are fixed and not predictive – like “Must finish on”)
  8. Actual work being recorded in the plans ( Actual work done on a period by period basis)
  9. Accurate metrics being calculated (Earned Value)
  10. Integration of all project schedules to provide a dynamic forecast and predictive outcome of impacts (“Workplans” or tasks for each team which form the complete schedule)

SEI summarized the use of project plans as:
“A project’s documented plan is the basis for monitoring activities, communicating status, and taking corrective action. Progress is primarily determined by comparing actual work product and task attributes, effort, cost, and schedule to the plan at prescribed milestones or control levels within the project schedule or work breakdown structure. Appropriate visibility enables timely corrective action to be taken when performance deviates significantly from the plan. A deviation is significant if, when left unresolved, it precludes the project from meeting its objectives.”  (CMMI V1.1, pg 219)

One other bit of advice about schedules based on my observations and experience:

A dangerous time in the life of a project is in the middle of the schedule. After the excitement of beginning the project and before the end of project—everything has to be done by when?there is the sometimes abandoned middle. In the middle of a complex project execution, it is easy to assume that “there is plenty of time left”. One forgets the logic and experience used to build the original schedule.  Remember that a project schedule is not a “wall chart” to be placed on the wall and admired!

Bad idea! Bad practice!

Project managers need the discipline to monitor schedule and plan compliance every week. During project execution, project schedules should be monitored by actual work recorded against the plan.  This means tracking time against tasks.  This allows metrics to be used in the project processes necessary on large projects.  Using staff estimates of percentage complete rather than actual work performed and estimates to complete, is not an accurate method of monitoring progress on a large, multi-project program.  Additionally, without documented, supportable statistics, managers have no credible evidence to support resource demands during the execution of the project.

Following these basic principles gives you a better than average chance that your project schedule is a useful, predictive schedule and not just a static wall chart.