Decision Tree

From apppm
Revision as of 11:04, 2 October 2017 by S162469 (Talk | contribs)

Jump to: navigation, search

Decision Tree

Contents

Introduction

Background

Some introductory terms such as Decision Making and Risk are explained:

Decision Making

Decision making in project management is a problem-solving process. The project manager makes decisions to face and solve the problems and challenges. The logic of this process is quite simple. After the identification of the problem, a decision needs to be made only if there are different alternatives or different solutions. If there is also one solution, the project manager tries to consider all the implications that will occur from this solution. If there are more than one different alternatives, the project managers try to make the decision that will lead the project and the company into prosperity. Moreover, these decisions must be made in timely fashion.

Risk/Expected Value

Risk or Expected Value can be defined as the expected consequences derived from a given activity. Usually, the term risk is referred to the expected costs, while the term expected value is used for the expected gains from an activity in an organization. However, the calculation procedure is exactly the same for both of these terms.

Considering an activity with only one event with potential consencequences C the risk or expected value EV is the multiplication of the probability that this event will take place P and the consquences which arise from the occurence of the event:

 EV = P * C

If n events with concequences/costs  C_i and probabilities  P_i , respectively, may result from an action, the total expected value associated with this action is equal to the sum of the risks of the individual possible events;

 EV = \sum_{i=1}^{n} P_i\ C_i

Decision Tree

Purpose

Decision Tree is a graphical method for illustrating the flow of decisions faced on a project depending on the possibility of each decision. A decision on a project cannot be considered as a single, isolated occurrence, but instead as an outcome of several interrelated decisions. Decision Tree is a mathematical modelling technique, used as a Risk Analysis and Management Tool. Through it, the project managers can observe options, which can be used for decision making and management of the project. The Decision Tree can assist them with probabilistic cost estimation of a project, incorporating risks of uncertain events, which may happen, and supply of alternative options and scenarios. Despite, some limitations and challenges faced by its application, decision tree analysis displays a powerful quantitative technique for different future alternatives, taking into account not only probability, but also choice.

Structure

Decision trees are quantitative diagrams with nodes and branches representing different possible decision paths and chance events. [1] The decision tree is read from left to right. More specifically, a decision tree consists of the following elements

  • Root node: It is the leftmost node of the decision tree
  • Decision node: It is represented by a small square.
  • Decision tree branches: These branches which emanate from the right side of the decision nodes, compose the set of alternative decisions – solutions, which can be pursued. The project manager can select and put into application, one and only of these branches.
  • Chance node: Chance nodes are represented by small circles in the decision tree, indicate that a chance event is expected at that point. The number, which can be seen on the branch of each of these nodes, presents the probability of the decision on each branch to occur in the chance node.
  • Endpoint: The right end of each path of the decision tree is named as endpoint. Every endpoint in the decision tree shows the final outcome of following this particular path from the root node to this particular point.

Advantages of decision trees

Transparency

Preciseness
Simple In Application
Flexibility

Construction of decision tree

For an accurate construction of a decision tree, a project manager needs to conduct the following steps

  • Construction of a logic tree, usually from left to right, including the decision and chance nodes
  • Addition of the probabilities of the different states on the branches of the tree. The logic tree is, therefore, transformed into a probability tree. Caluclation of the probabilities in the endpoints. The sum in the probabilities in the endpoints must be equal to one.
  • Addition of the conditional outcomes. The construction of decision tree is completed.

Decision Tree Analysis

Figure 1: Decision Tree Analysis

Example

A decision has to be taken whether the company should fund project X or project Y, as it can be seen from the Figure X. Each project has two possible outcomes. Project X has a 75 percent chance of yielding 100000 monetary value, but also a 25 per cent chance of only yielding 20000. Project Y has a 50 per cent chance of yielding 200000 and 50 per cent of chance that profit will be zero. Figure X illustrates the current decision problem.

The company in this case tries to maximize its expected value (or in the opposite condition to minimize its expected costs). The final decision is made through the sum of the expected values of the yields of each branch.

For project X

 Expexted\ Value_X = P_X1 * C_X1 + P_X2 * C_X2 = (0.75 * 100000) + (0.25*20000) = 80000

For Project Y

 Expected\ Value_Y = P_Y1 * C_Y1 + P_Y2*C_Y2 = (0.5 * 200000) + (0.5 * 0) = 100000

  Expexted\ Value_X < Expected\ Value_Y

As the decision maker wants to maximize the yield, which is represented by the expected value, project Y should be pursued.

Different types of Decision Tree Analysis

According ot the state on available information at the time, when the decision analysis is conducted, three different analysis types are distinguished: Prior analysis, posterior analysis and pre-posterior analysis. Due to their importance in practical applications in decision analysis, their logic and possible outcomes are briefly discussed in the next sections.

Prior Decision Analysis

A prior analysis is the basis for the comparison between different activities.

Figure 2: Decision Tree for prior and posterior Analysis

Posterior Analysis

A posterior analysis is used to evaluate the effect of activities, which factually they have performed. More specifically, in posterior analysis, additional information is available. Consequently, the probabilities that are used for the prior decision analysis can be updated, leading eventually to more accurate estimations and, therefore, more accurate decision-making.

Figure 3: Decision Tree for pre-posterior Analysis

Pre-posterior Analysis

With the use of pre-posterior analysis, optimal decisions can be identified, concerning activities that may be performed in the future. A project manager-decision maker often has the possibility to find and buy additional information through an experiment, before a choice is made. If the cost of this information is small, compared to the potential value of the information, the decision-maker should buy this information.

Limitations of Desicion Tree Analysis

Decision Tree Analysis has some inherent limitations in its application, as

  • Inadequacy in applying regression and predicting continuous values
  • Possibility of false relationships

Considerations and Challenges

Complexity

For more sophisticated problems the process of constructing a decision tree can be complicated. Although decision trees are an easy tool for decision making in comparison with other tools, constructing a decision tree with many branches can be a complex and time-consuming task. Scores and hundreds of branches and so many potential outcomes may be involved in a complex decision tree. The major difficulty on this lies on the accurate calculation of the probabilities on the many different branches. In these cases, the decision maker should have enough expertise and experience to successfully. (impact hub)

The Human Factor

Project managers – decision makers are often faced with having to explain why one course of action is better than the other in the face of uncertainty. Even if the project manager has made an accurate representation of a decision tree, it is necessary that the managers of other departments of a company will understand its concept and its results. Moreover, some managers are more interested in the effect of a decision on their department, than in the effect that has in the whole organization. It is clear that even in quantitative analysis methods in project management science, in the end, the human factor has a vital role.

Representation of data

This technique also demands that all factors have to be represented quantitatively – cost and consequences are usually expressed in financial terms, and probability must be estimated for all chances. In some cases, it is rather difficult to have a precise estimation for the probabilities and the expected values. Taking also into consideration the complexity of decision trees, a miscalculation in a probability in a branch, may result in completely misleading outcomes and, eventually, to the wrong decision and action.

Risk Averse and Risk Neutral Organizations

In decision tree analysis, it is assumed that the organization and the project managers will select the decision according to the analysis. This means that a decision will be chosen based on the possible maximization of the expected value or on the possible cost minimization. This behavior is called ‘risk-neutral’ and is characteristic of an organization which takes into consideration long-term revenues, by applying the decision with the maximum expected value. However, many times, there is a slight probability that this decision may also result in huge losses. In the real world, many organization, if not the most, are unwilling to be dealt with situations, where there are vulnerable to large losses, if even there is a small chance of that. The small possibility of failure overcomes the large possibility of great gains. This behavior of the organization is called ‘risk averse’. This organizations tend to maximize their expected utility than their expected value. This utility function may give a significant negative weight to the possibility of large losses, resulting in a different optimal decision form the analysis. Nowadays, it is possible with decision tree software to design a utility function that reflects the organization aversion to large negative consequences.

References

  1. Kerzner, H., Ph.D., (2006), ""Project Management: A systems approach to planning, scheduling and controlling"". Ninth edition

Annotated bibliography

1. Winch, G. M. (2010), "Managing Construction projects". Second edition
Summary: The book presents a holistic approach of construction management. The basic principles of construction project management are presented along with different tools and techniques that aims to enhance construction performance and provide innovative techniques. The use of information and communication technologies is also a point of interest in the book.
2. Kerzner, H., Ph.D., (2006), "Project Management: A systems approach to planning, scheduling and controlling". Ninth edition
Summary: The book illustrates the basic principles of project management. The book is targeting for enhancing the project skills of not only students, but also executives, pointing out that project management can be related to every profession apart from engineeering, including information systems and business.
3. Maylor, H. (2010), "Project Management". Fourth Edition
Summary: This book cover all the topics of project management, focusing in the theory, as well as in the application and usage of the ideas discussed in it. The book points great emphasis into the 4D-model of the project.
4. Flyvbjerg, B. (2008) "Curbing Optimism Bias and Strategic Misrepresentation in Planning": Reference Class Forecasting in Practice, European Planning Studies Vol. 16, No. 1
Summary: This paper presents the method and illustrates the first instance of reference class forecasting. The paper targets in the inaccuracy of the financial appraisal in planning in construction, explains them in terms of optimism bias and strategic representation and present a method of eliminating this inaccuracy.
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox