Project Evaluation and Selection for the Formation of the Optimal Portfolio

From apppm
(Difference between revisions)
Jump to: navigation, search
(Development history)
Line 1: Line 1:
The increasing intensity of competition and fast technology changes make firms look for the  
+
The increasing intensity of competition and fast technology changes have pushed firms firms to look for the  
 
development of more innovative products. In order to keep up with market trends and to stand  
 
development of more innovative products. In order to keep up with market trends and to stand  
 
out from competitors, most of the companies in technological fields turn to the development of  
 
out from competitors, most of the companies in technological fields turn to the development of  

Revision as of 14:37, 16 November 2014

The increasing intensity of competition and fast technology changes have pushed firms firms to look for the development of more innovative products. In order to keep up with market trends and to stand out from competitors, most of the companies in technological fields turn to the development of R&D projects. Generally, these are risky due to the uncertainty surrounding its technological feasibility and its future commercial success, which make their evaluation and selection difficult to achieve. Nevertheless, the survival of an organization is highly correlated with correct project selection and management (Ashrafi, 2012). A wide diversity of approaches have been developed and used throughout recent years in order to cope with this problem, each of them with its own advantages and disadvantages. The most common are quantitative methods, qualitative methods and hybrids methods (Ashrafi, 2012). Nonetheless, most of the times not only one method is used during the evaluation process.

Even if the projects are correctly evaluated separately, this does not guarantee that the best portfolio can be formed. The best portfolio is the one that maximizes the probabilities of achieving the goals set by the company (Chien, 2002). Its formation is not just about evaluating independent projects; it is about evaluating the whole portfolio itself. Choosing the best projects based on financial or any other criteria may not result in the best portfolio due to dependencies or interrelations that may exist between the projects. The most common of them are related to cost, resources, financial return and technical factors (Blau, 2004), as well as outcome and impact dependencies. The problem of evaluating and selecting projects and scheduling them is complicated further by their presence. These dependencies add complexity to the decision that needs to be taken, since the decision-making process becomes less straightforward. A good example is the impossibility of using some quantitative methods, like linear programming. A good example of this situation is given when investing an additional monetary unit, since it may have impact in more than one project, since the additive restriction does no longer exists under this perspective. In consequence, a difference between measuring the preference for the portfolio as a whole and measuring the preferences for projects in the portfolio (Chien, 2002), and it may be also the case where the objectives that are considered when evaluating portfolios are different than those used when selecting individual projects.

If a company decides to evaluate a portfolio as it would evaluate projects, the amount of time required would be unmanageable. With only a set of 10 projects, the decision-maker would need to evaluate 1024 portfolios (Ghapanchi, 2012), which would be impossible for most of the companies (the possible combinations of projects equals 2 to the x power). In consequence, newer methods have been developed to assist with choosing the best portfolio within a shorter time. This article focuses on describing and analyzing these methods.


Contents

Background

Application context

Every organization has a specific business strategy that will facilitate reaching its long-term goals. In consequence, ideas and concepts are developed, and products and services are designed, produced, manufactured and sold. However, companies need to take decisions along this path, since they do not have unlimited resources for pursuing every single idea. Furthermore, every one of them has a benefit accompanied by a certain degree of risk. Nevertheless, frequently, both benefits and risks are difficult to measure, since perfect information is not always (almost never) available.

Selecting the best projects (according to different criteria, like expected benefits, risk, investment, return, among others) is a common practice among many enterprises, no matter the industry they belong to. At the same time, projects can be of very different origin. Some of the most discussed in the literature are R&D projects, New Product Development, marketing campaigns, among others internal activities. However, selecting the best project in order to form the optimal portfolio is not an easy task.

According to the Project Management Institute, a portfolio is "a collection of projects and/or programs and other work that are grouped together to facilitate the effective management of that work to meet strategic business objectives. The components of a portfolio are quantifiable; that is, they can be measured, ranked, and prioritized" (PMI, 2006). In that way, the optimal portfolio would be the one that, given a determined array of components, gives the maximum benefits and is the one that best meets the company's objectives.

Development history

Few project selection models are being utilized as aids to decision making. The number of selection models, along with user interest in applying them, grew exponentially in the 1950's and 1960's; however, this trend has reversed since the mid-1970's (Chien).

At the same time, the Project Management Institute (PMI) was founded in 1969 in the United States. This organism is in charge of publishing, by different means, the most common best practices in project and portfolio management.

Acceptance and use

Portfolio Management Process - High Level Illustration

According to the Project Management Institute (PMI, 2006) the portfolio management processes are a series of interrelated processes, from identifying and authorizing portfolio components to reviewing the progress of each individual component (project), as well as that of the entire portfolio. This article focuses mainly on the Evaluation, Selection, Prioritization and Portfolio Balancing phases. The processes and tasks described in this sections has been recognized as good practices in the discipline of portfolio management. The PMI defines the Evaluation phase as the process for gathering all pertinent information to evaluate components, with the purpose of comparing them in order to facilitate the selection process. The Institute recommends beginning with information gathering, both qualitative and quantitative, until reaching the required level accuracy (if possible). Also, graph, charts, documents and recommendations are produced to support the selection process. The recommended key activities for this process are:

  • Evaluate components with a scoring model with weighted criteria. The criteria may be related, but no limited, to business, financial benefits, risk, legal/regulatory compliance, Human Resources, marketing and technical criteria. (See The Standard for Portfolio Management for a complete list of criteria).
  • Produce graphical representations (comparison grids, histograms, pie charts, line charts, and bubble charts) to facilitate decision-making.
  • Make recommendations for a project, a category or the entire portfolio based on the value of each component or a group of them. Expert judgement may be used for this activity.

Once the Evaluation phase has been completed, it is necessary to move to the Selection phase. During this process, a short list of components (projects) based on the evaluation recommendations and the organization's selection criteria is produced. There are two main outputs for this phase:

  • A list of categorized, evaluated and selected components, which can be compared by category or for the entire portfolio.
  • Recommendations: can include prioritization, acceptance, or rejection of a component.

The most popular tools and techniques to ensure that the most desirable components are selected include, among others, Human, Financial and Asset Capacity Analysis, which aim is to understand the capacity of the organization in term of these resources in order to execute the selected projects. Also, Expert Judgement is used to asses the inputs needed to select the components.

The objective of the prioritization phase is to generate a list of prioritized components within each strategic category with its relevant information. The most used tools are single and multiple weighted ranking, scoring techniques and expert judgement.

Finally, the Portfolio Balancing phase aims to develop the portfolio component mix with the greatest potential, to both support the company's strategic initiatives and achieve strategic objectives. The selection of the mix of components should also take into account similarities and synergies that exist between projects (dependencies). The most used tools, methods and techniques include, among others, cost benefit, quantitative, scenario, and probability analysis, as well as graphical analytical methods and expert judgement.

From Project Selection to the Optimal Portfolio

Methods for Project Evaluation & Selection

Methods

Three schools of thoughts have been identified (Ashraki) on how to classify the approaches for project portfolio evaluation and selection:

  • Quantitative Methods: these approaches, both for project selection and resource allocation, have been greatly developed since the early 1990's, but some of them have been around for more decades. However, they have been often criticized because their focus on numerical information, even though tacit knowledge and qualitative information have also been regarded as relevant. Generally, they can be classified in six dimensions (Iamratanakul,2008):
    • Benefit measurement methods: Comparative models, scoring models and analytic hierarchy process. Here, five measures are particularly popular (Thamhain, 2014): Net Present Value, Return on Investment, Cost-Benefit, Pay-Back Period and Pacifico and Sobelman Project Ratings.
    • Mathematical programming approaches: linear programming, non-linear programming, integer programming, goal seek, dynamic programming, stochastic programming and fuzzy mathematical models.
    • Simulation and heuristic models: Monte Carlo simulation, heuristic modeling and system dynamics simulations.
    • Cognitive emulation approaches: decision-tree, game-theoretical approaches, statistical approaches and decision process analysis.
    • Real options: approach that incorporates both uncertainty and the active decision making required for a strategy to succeed.
    • Ad hoc models: unstructured models built for specific purposes.
  • Qualitative Methods: their focus is to take into account those factors that quantitative methods cannot. For project evaluations involving complex sets of business criteria, narrowly focuses quantitative methods are often supplemented with broader qualitative methods. Some of the most used are bubble diagrams, sensitivity analysis, benchmarking, check-lists, user centered design, group decision techniques and expert systems (Delphi, nominal group technology, focus groups). However, all of them can be used by themselves to determine the best, most successful or most valuable project.
  • Hybrid (Mixed) Methods: they are the most common methods for evaluating and selecting projects nowadays (Thamhain, 2014). To qualify as a hybrid approach, the project evaluation and selection process has to contain a fairly balanced array of both classes of analytical and judgmental tools and techniques. Some good examples are graphical methods, conjoint analysis, data envelopment analysis and scenario planning.

Dependencies

In order to understand why dependencies or interrelations are relevant to this topic, and why the methods discusses above do not lead to an optimal decision, it is important to define what are these interactions. To begin with, it is worth noting that there are two sources of interactions among projects: internal and external factors. The former arises when the resource requirements and/or benefits of one project are significantly affected in magnitude and/or timing by the selection or rejection of one or more of the projects in the set. On the other hand, the external interactions are those that arise over time from social and economic changes which have effects over subsets of the project set (Fox et. al, 1984). Through this article, only the internal interactions are going to be discusses, since those externals are impossible to know/quantify beforehand by the decision-maker.

There are 4 major sources of internal dependencies: Costs dependency, (non-monetary) resources dependency, outcome or technical dependency, and impact or benefit dependency. Some of them may overlap in scope, but are different in essence.

Cost Dependency

Cost Dependency. The sum of the cost of the projects is lower than the total cost of the portfolio.

It is also called resource-utilization dependency. This dependency arrises when the sum of the costs of two or more projects within a portfolio is not the same at the total cost of the entire portfolio. This happens because there is some degree of resource sharing, like labor, utilities, machinery and tooling, among others (Blau, Chien, Fox et. al). A project may require using a new machine, but its capacity is higher than the utilization required by this project, so it is possible to share it with other projects or with ongoing operations. However, if it is not used for something else, then the dependency does not exist. On the other hand, the appropriate portion of the cost of this machine is difficult to estimate, since it would be necessary to have an overview of the rest of the projects, some of whom might come in the future.

Resources Dependency

It is more related to the time that a certain project may require. It differentiates from the cost dependency because its focus is not the money employed, but the available time for its development. Its root cause is the learning curve derived from the employees' experience. A good example is that of the reduction in development times of two similar drug types (probably the second one will require less time because of the experience acquired during the development of the first one).

Outcome or Technical Dependency

This type of interactions occurs when the probability of success of a given project depends on the outcome (success or failure) of one or more of the other projects (Fox et. al and Chien). The problem for the decision-maker arises when trying to translate this situation to numbers or comparable criteria. This could be compared to decision-tree analysis: if an specific project fails, then the next project cannot be developed and vice versa. This type of dependencies are common in software or hardware development. A good example could be the case of a new printer that requires the development of a new technology for printing with twice the speed as the previous model. In this case, the printer cannot be released to market if the printing technology has not been successfully developed.

Impact or Benefit Dependency

An impact or benefit dependency may occur when the impacts of payoffs of the projects are not additive. In this case, projects may be said to be complementary or competitive, e.g. what happens with cannibalism. A good example for this dependency is what happens when a company decides to introduce a new product to a specific market segment, successfully increasing the overall sales. At the same time, another project's objective is to add a special feature that may make more attractive this same product in order to reach a different demographic group, which will also increase sales. If both projects are implemented, then the net total sales may be lower than the expected individual sales figure for each project. Since the product now has a scope for two markets, then some buyers may not consider it attractive anymore. (Fox et. al).

Methods for the Formation of the Optimal Portfolio

From Projects to Portfolios. Due to dependencies or strategy, the best projects does not necessarily result in the best portfolio
  • Dependencies as in taken into account
  • New methods

Related material

Comparable standards / recommendations

Obviously standards

Additional related material

Webpages or books

Discussion

Strengths and weaknesses

There are some limitations in the existing project selection models (Chien) for the further formation of portfolios:

  • Inadequate treatment of multiple, often interrelated, evaluation criteria.
  • Inadequate treatment of dependencies among projects.
  • Inability to handle non-monetary aspects, for example, diversity among projects.
  • No explicit recognition and incorporation of the experience and knowledge of the managers or decision makers.
  • Perceptions by the managers that the models are difficult to understand and use.

Controversial points

Pro's and con's

Integration / relationship to other material

Relationship with resource allocation

Implementation advice

How to use and methods

Choosing the adequate one.

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox