Sharing tools and ideas for Portfolio, Program, and Project Managers

Archive for the month “June, 2012”

Project Management Synthesis (or PMS for the PM)

AN·A·LYZE verb (used with object), -lyzed, -lyz·ing.  (from

1. to separate (a material or abstract entity) into constituent parts or elements; determine the elements or essential features of; e.g. to analyze an argument.
2. to examine critically, so as to bring out the essential elements or give the essence of: to analyze a poem.
3. to examine carefully and in detail so as to identify causes, key factors, possible results, etc.

One who analyzes is an:

AN·A·LYST noun   (from

1.a person who analyzes or who is skilled in analysis.
There are many types of analysts:
BA Business Analyst
CSBA Certified Software Business Analyst
AFA Accredited Financial Analyst
CRA Chartered Certified Risk Analyst
CAPA Certified Asset Protection Analyst
CITA Certified International Tax Analyst
And so on…
There are no Project Management Analyst (PMA) jobs, titles, or positions that I’ve ever run across. (If you see one let me know. I’d be very interested in see what’s in that job description.)  While there are no formal job descriptions for this portion of your project manager position it is a key activity to your success that will contribute to your being an outstanding Project Manager.  A PMA must understand all the INPUTs to their projects that will have an influence on the OUTPUTs of their project (or deliverables). Recall that you must analyze, to examine critically, so as to bring out the essential elements, all inputs necessary to determine which ones are important enough that they will have a material affect on the outputs or deliverables of your project. What does this mean?  This is a Six Sigma approach applied to project management.  Things like risks, assumptions, constraints, and stakeholder identification are all INPUTs to your project plan.  In Six Sigma process development these are refered to as KPIVs or Key Process Input Variables.  These and other input variables have a bearing on the final OUTPUTS of cost, quality/scope, and timing of your project.  The quality side of these inputs are called CTQs, Critical To Quality.  They are the independent variables that directly affect your OUTPUT or desired deliverables.
Yet, being a PMA is only a portion of the key activities required to becoming an above average project manager. To deliver your schedule within the triple constraints you must bring all the elements together into a cohesive whole or synthesize your KPIVs to be able to tell a story on how to get from your  key inputs to your desired outputs. You must become a Project Management synthesist (PMS).
SYN·THE·SIZE  verb   (from form (a material or abstract entity) by combining parts or elements
Every team will create a different project plan and schedule, given the same inputs, based on the team’s skills, training, and experience. It is your job as the PM to synthesize and create the vision, plan, and schedule that is achievable.  Let me repeat-It is your job as the PM to synthesize and create the vision, plan, and schedule that is achievable.  While this may seem to be stating the obvious I’ve seen PMs put together project plans that were not realistic from the get go.  When queried, the response I got was “Manufacturing wanted it this way!” (???)  This PM did not create and synthesize a plan into a cohesive whole. What they planned for was eventual chaos and failure.  In other words outputs  didn’t match the stated inputs.  Even before project execution began you could review this plan and read the words “Defeat” across it.
As PMs our roles are to create and describe a vision of how to get from A to B, create a plan and schedule in a reasonable level of detail, and communicate this vision and plan to all core team, extended team and management.  With a core team of 15, extended team members of 30+, support functions, suppliers, and management you will have easily over 100 people in which you will have to communicate your vision.  I once had a boss that accused me of being “repetitive.”  While he meant that negatively I took it as a complement because it is my job to make sure everyone understands project goals, plans, and how you get from A to B.  You can give a message 100 times to a group.  Some get the message the first time, others don’t or won’t get it after the 100th.
Make sure you understand all the KPIVs for your project then synthesize those elements into a cohesive whole.  Bring it all together  to create the vision and paint the picture.  When a project fails it can be traced back to either one or more KPIVs were not properly identified therefore its affect on project outcome was not controlled or one of the KPIVs changed  and as an independent variable had a material affect on the outcome.  Outputs are driven by KPIVs make sure as a PMA/PMS you understand both.

Basic Portfolio Management or “Doing the right projects.”

Basic Portfolio Management or “Doing the right projects.”

I’ve worked in organizations where everyone sets their own priorities.  That’s great as long as they are the only one in the entire organization.  Since that was not the case there were lost opportunities in maximizing outcomes.  This blog is an introduction into the idea, not a new one, in which you should understand all the projects and programs you have ongoing (the portfolio) and determine in some manner those that are of most value to the organization, value not necessarily meaning money.

Here’s the definition of Portfolio and Portfolio Management from PMI’s The Standard For Portfolio Management 2nd Edition:

Portfolio– A collection of projects or programs and other work that are grouped together to facilitate effective management of that work to meet strategic business objectives.  The project or programs of the portfolio may not necessarily be interdependent or directly related.

Portfolio Management– The centralized management of one or more portfolios, which includes identifying, prioritizing, authorizing, managing, and controlling projects, programs and other related work, to achieve specific strategic business objectives.

Figure 1 Project Portfolio Flowchart

Figure 1 shows a basic process that describes a generic portfolio management method to prioritize a portfolio of projects.   Inputs and Outputs shown are lists or documents or information that is written down and agreed upon by those involved in the process.

Most businesses do portfolio management at some level even if they don’t call it that.  They go through a mental exercise of; Project A takes 2 years to complete, costs $500,000, and pays back $3 million. Project B takes 4 years to complete, costs $2 million, and pays back $4 million.  Most business would choose project A.  The key point is that they have identified three evaluation criteria in which to make their decision- Completion time, Cost, and Payback.  The trouble is that there are typically many evaluation criteria not a few.

Figure 2 Project Priority Categories

Figure 2 is a basic list of high level criteria that may be used to determine where the value lies in a project.  There are only nine categories in this example with some various values to give you an idea of what can be done. Some portfolios may use a system with dozens and I’ve heard of portfolios that have a couple of hundred or more evaluation criteria.  Typical use is to assign a value to a project for each category/line on the list and score the project based on its assigned values.  Since there are nine categories with five points being the highest value in each the highest project score would be 5 points x 9 categories = 45 total points.  I’ve also added a weighing column to give you an idea of other options.  Do this for each project.  High scores should be top priorities.  Now do a reality check.  If your highest priority project isn’t on the top of the list determine why! Are there additional criteria you’re mentally using that aren’t accounted for using the scoring method?  Is the high priority project a pet project sucking up valuable resources regardless of its value to the company?  This is not uncommon.  Use this information to make an informed and data driven decision!

Basic steps required to prioritize (per Figure 1):

  1. Determine the strategy for your organization.  Should be written strategy, goals, and objectives.
  2. Determine who will be involved in this process, president, VPs, director level?
  3. Determine the list of portfolio components (projects) with some minimal level of detail, e.g. How many components? How much will each cost?, How long to completion?, How many man-hours will this take?  What do we get in return (dollars, market share, mindshare) and how much?
  4. Assign values and rank each component.
  5. Balance components. Are you doing all new product introductions or manufacturing cost reductions or a combination of both?
  6. Approve your portfolio.
  7. Assign resources.  This means assigning resources be they people, equipment, or dollars to each portfolio component from the top portfolio priority until you run out of one of the resources because resources never precisely match your portfolio.  You can either use the leftover resources to work on projects farther down the list knowing these projects will be slow moving due to a shortage of required resources or you can use leftover resources and apply them to the projects higher up the list and previously resourced to expedite where possible.
  8. Execute.

It’s imperative that those portfolio components that are assigned full resources are monitored and controlled to effectively execute each of the project plans.  If you cannot execute your fully resourced high priority projects there will be a need for discovery as to why and how it fell short.  There should be some adjustment somewhere in your process.

Small companies and big companies do portfolio management.  Small companies and big companies don’t do portfolio management.  You can tell which one does or doesn’t after working there for a brief period. Companies that do portfolio management typically have higher worker moral and are more productive. Companies that don’t typically have lower moral and are less productive. This is because personnel are yanked from project to project fighting the latest fires that erupt requiring a refocusing onto the new high priority project resulting in lost time due to changeovers and the new learning curve required of new projects.

I urge any organization that has more than a few projects to use this simple outline.  Outcomes are higher moral, higher productivity, and better strategic implementation and performance.

Post Navigation