Page 294 - Untitled-1
P. 294

THE TRADITIONAL ORGANIZATION                                     273

issues of project termination. But what about project and portfolio assessment? Is
a project a static item or a dynamic system?

   If a project is dynamic in nature (that is, the project scope, timing, and cost are
subject to change), then what effect does this have on the project portfolio? The
typical project has a range of possible outcomes and costs. There is the base case
and potential upside and downside. If the project was selected on the basis of a
set of assumptions (stated in the base case), does that project still belong in the
portfolio when its attributes change? We need to periodically review the project
to test assumptions, update givens, and monitor progress. We need to periodically
examine alternatives (without alternatives, there is no Project Portfolio Manage-
ment) and consider remodeling the portfolio.

Trap These three potential weaknesses can obstruct the im-
plementation of Project Portfolio Management:

1. The firm’s objectives and goals, as supported by the project
    portfolio, are not communicated to the people responsible
    for project performance.

2. The project performance, as monitored by the project man-
    agers, is not communicated to the portfolio managers,
    strategic planners, and senior managers.

3. The gap that exists between these two groups, both in
    communication and in available information, prevents ac-
    tive management of the portfolio, based on the current,
    changing status of the component projects.

   What is so obviously needed is a basis for addressing project selection issues,
deciding on project termination, facilitating reallocation of resources, changing of
priorities, and evaluation of alternatives. And without this capability, there is no
Project Portfolio Management.

   It is my objective, in this book, to address issues associated with effective proj-
ect management, independent of any of the support tools offered by any particu-
lar vendor. However, occasionally a project management software developer
comes out with something worthy of special note. In this case, I cannot complete
this discussion of bridging the gap between Operations Management and Project
Management without mentioning a special set of tools that have been developed
to address these needs. In 1999, as I was preparing a series of articles on this sub-
ject, Scitor Corporation was also addressing the issues associated with Project
   289   290   291   292   293   294   295   296   297   298   299