Project vs. Program vs. Portfolio Management


I mentioned in the last post the shift from project management to program management as one of the many important shifts in business-IT maturity that typically take place around the middle of Level 2 (in a simplified 3-level model).  I want to explore that in greater detail in this post, and connect it to Portfolio Management which I see as a key discipline in getting to Level 3, and to extracting high, visible business value from IT investments.

A recent post, Programs are More than Just Big Projects, by colleague and friend Roy Yougman in his blog http://www.ryoungman.net/ inspried me to discuss Program Management as a critical link between Project and Portfolio Management.  In a simplified sense, project management deals with a single project (be it small or large) with a focus on producing agreed deliverables, to an agreed schedule and budget.  Program management deals with multiple projects that collectively produce an agreed business outcome – i.e., they have inter-dependencies (e.g., impact the same group of stakeholders, each contribute to achieving a business outcome, and depend upon each other to do so).  It is the management of these inter-dependencies against the delivery of the agreed outcomes that distinguishes program from project management.  I have to acknowledge that the terminology here, though well defined in the project management literature and sources such as Wikipedia, is not universal or used consistently.  In the aerospace/defense industry, for example, programs have a different connotation more related to funding.

If projects can be thought of as the bottom of a hierarchy, programs sit above them in the middle of the hierarchy and address a related set of projects, then things get to be most interesting at the top of the hierarchy – the portfolio management level.

My favorite source on IT Portfolio Management are Prof. Peter Weill and his co-author, Marianne Broadbent.  Their first book that addressed this topic was Leveraging the New Infrastructure: How Market Leaders Capitalize on Information Technology.  There are various IT portfolio models around – the reasons I like Weill’s are:

1. It differentiates the IT investment in common, shared infrastructure (broadly defined).

2. Weill has years of benchmark data showing how portfolio allocation varies by industry, and how it reflects business performance.

As I get personally closer to retirement, like many boomers, I give increasing attention to my (meagre!) personal investment portfolio, which makes personal investments and portfolio theory a great analogy for IT investments.  My portfolio goals have changed over time as my circumstances have changed (e.g., putting a kid through college, getting closer to retirement).  Whatever those circumstances, I’ve had the discipline (thanks to an investment advisor) to annually re-think my portfolio strategy, to be explicit about it, and to monitor the performance of my portfolio against that strategy, and adjust periodically.

In the IT portfolio domain, the same is necessary.  How much of our IT spend should be leveraged across the firm?  (By the way, a common challenge is the funding mechanisms for common infrastructure are often weak – another Level 2 trap is that funding in Level 1 and early Level 2 tends to be by the project, and for given business units – nobody likes to fund cross-business unit initiatives!)  How much should we be spending on “risky” but potentially high value initiatives?  How much on informational (business analytics/decision support)? 

Another Level 2 trap is that a firm’s earliest entree into IT portfolio management is typically limited to new spend.  However, the reality for most enterprises is that new IT spend represents less than 30% of total spend, so there is bigger value in applying IT portfolio management to the steady state services (bringing us back to Service Management mentioned in an earlier post)

My key points through all this are to get through Level 2 to Level 3:

1. You need great project management as a fundamental discipline.

2. You need great program management as a bridge to portfolio management.  You can’t easily go from project to portfolio – there are just too many projects, and projects are focused on deliverables, whereas program focus on business outcomes – which is what portfolio management needs to focus on.

3.  The biggest impact in terms of advanced IT practices comes from portfolio management (the IT investment strategy), and if you are weak in project or program management, you will never get the full potential of portfolio management.

About these ads

23 thoughts on “Project vs. Program vs. Portfolio Management

  1. Pingback: The Business Case as a Value Realization Tool « IT Organization Circa 2017

  2. Pingback: How Sustainable is Your IT Portfolio? « IT Organization Circa 2017

  3. Pingback: IT Service Management vs. IT Product Management « IT Organization Circa 2017

  4. Pingback: The “Unwritten Rules” of Project, Program and Portfolio Management « IT Organization Circa 2017

  5. I’m doing a reaserch on how do organizations group their projects into programs, please tell me how do they go about doing that. e-mail me as soon as possibel

    Reply
  6. Siyasanga, thanks for your question. It is an important question, but I won’t answer it by email – I think other readers of this blog may benefit from this discussion, so I will write a new post on this topic.

    Reply
  7. Hi, im student form UJ and i would like to know about how your organasation group its projects into progarm and i also need to know how do you go on creating your project portfolio.thank you!

    Reply
  8. Pingback: Portfolio Management: So Much More Than a Collection of Projects! « IT Organization Circa 2017

  9. Pingback: Onur DURUSÖZ, PMP » Blog Arşivi » Bir PMP’nin Sık Kullanılanları :)

  10. Pingback: A Review of this Blog in 2010 « IT Organization Circa 2017

  11. “I have to acknowledge that the terminology here, though well defined in the project management literature and sources such as Wikipedia, is not universal or used consistently.”

    I particularly agree with this statement. As the lines between project, program, and portfolio vary so greatly from company to company and are so blurred between industries, it is hard to exactly define them. I’ve also had a difficult time looking through the many software solutions claiming to be specific to the type of management it handles. They say things like, “For all your portfolio needs,” or “Manage your tasks with ease,” or “See how successful your programs can be.” (Rhyme not intended.) Because of all this confusion, I think that is why work management is beginning to be chosen over the strict process and definitions of project management and all its related components and disciplines. Work management encompasses all of it in a more dynamic way. It doesn’t dwell on defining the hierarchical structures of work, and just lets people get to the point. I am not saying that everything about project management is debunked. In fact, all of its processes are still applicable, but they function in a more adaptable way.

    Reply
    • You raise a great point re: “work management” Robert. On the one hand, this makes sense given the lack of consistency around the definitions. On the other hand, it is, as they say, a “cop out” and risks further reinforcing a lack of clarity. There are good reasons why scientists are so obsessive about hierarchical structures – atom, electron, nucleus, etc. Rigid hierarchies and the precision they imply are the underpinnings of good science, and good science is the underpinning of good exploration and understanding. If we give those things up in the world of IT we put ourselves at great risk, IMHO.

      Reply
      • Well said. Too often, it does become a “cop out” (and a sometimes arrogant) way of disregarding those skills and methodologies that have been researched and refined for decades (or centuries arguably). The successful project manager comes somewhere in between, where he or she can adapt to what needs to be adaptable and stay strict to those places where the project requires it.

  12. Excellent post, Vaughan! I find there is often confusion over the differences between the three – some people don’t even realise that there are any differences. You’ve set it all out very clearly.

    Reply
  13. Pingback: Portfelli-, programmi- ja projektijuhtimine « Jan Urva

  14. Pingback: Projects, Programs and Portfolios – 3 Common Traps « IT Organization Circa 2017

  15. Thanks for your personal marvelous posting! I quite enjoyed reading it, you
    could be a great author. I will make certain to bookmark
    your blog and will come back down the road. I want to encourage one to continue
    your great posts, have a nice afternoon!

    Reply
  16. Very great post. I simply stumbled upon your blog and wanted to say that I’ve truly loved browsiong your weboog posts.
    In any case I will bee subscribing for your feed and I’m hoping
    you write again soon!

    Reply

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s