InTechOpen uses cookies to offer you the best online experience. By continuing to use our site, you agree to our Privacy Policy.

Business, Management and Economics » "Risk Management Trends", book edited by Giancarlo Nota, ISBN 978-953-307-314-9, Published: July 28, 2011 under CC BY-NC-SA 3.0 license. © The Author(s).

Chapter 3

Selection of the Desirable Project Roadmap Scheme, Using the Overall Project Risk (OPR) Concept

By Mohammad Ali Hatefi, Mohammad Mehdi Vahhabi and Ghorban Ali Sobhi
DOI: 10.5772/16715

Article top


Process of the proposed technique including six phases
Figure 1. Process of the proposed technique including six phases
Screening mechanism of the proposed model
Figure 2. Screening mechanism of the proposed model
The evaluation process of an individual PRS
Figure 3. The evaluation process of an individual PRS
The labeling algorithm to identify the paths within risks network
Figure 4. The labeling algorithm to identify the paths within risks network
Relationships between child and parent nodes of an arc in risks network
Figure 5. Relationships between child and parent nodes of an arc in risks network
The PRS efficient frontier concept
Figure 6. The PRS efficient frontier concept
A part of the CBS for PRS S4
Figure 7. A part of the CBS for PRS S4
The risks network for PRS S4 (left) and its labels (right)
Figure 8. The risks network for PRS S4 (left) and its labels (right)
The PRS efficient frontier for the typical project
Figure 9. The PRS efficient frontier for the typical project

Selection of the Desirable Project Roadmap Scheme, Using the Overall Project Risk (OPR) Concept

Hatefi Mohammad Ali1, Vahabi Mohammad Mehdi1 and Sobhi Ghorban Ali1

1. Introduction

The findings of researches in the state-of-the art suggest that most errorsare due to poor planning of projectparticularly early in the life of a project. Indeed,project success is positively correlated with the investment in requirements’ definition and development of technical specifications (Dvir et. al., 2003). On the other hand, regarding the current business environment of rapid change, one of the main advantages of applying a proactive strategy in planning of projects is the greater flexibility in the competition conditions.

In the strategic planning phase of a project, the below question is outlined to one of the most significant issues in project management:

Which project roadmap scheme (PRS) is the desirable option to execute the project?

The PRSs will be formed by alternative responses to the questions such as:

Which contractor is the desirable option to engineer a given discipline?

Which machinery is the desirable option to produce a given part?

Which technology is the desirable option to montage a given product?

Which supplier is the desirable option to supply a given material?

Evaluating the feasible PRSs is recognized to be a considerable component of a sound project management. An important approach to evaluate the PRSs is the risk efficiency concept, which was originally developed by Markowitz (2002) for managing portfolios of investment opportunities. According to Chapman & Ward (2003), the PRSs can be viewed in a portfolio analysis framework. In fact, each PRS can be considered as an individual project.

The approaches to the solution of the above question"which PRS is the desirable option to execute the project?" can be classified in six groups:

  1. Profile and checklist methods,

  2. Project scoring methods,

  3. Financial measures,

  4. Mathematical programming models,

  5. Multi Criteria Decision Making (MCDM) models, and

  6. Fuzzy approaches.

Project scoring methods do not necessarily ensure the quality of PRS selection, because they do not explicitly take into account PRS level considerations, such as multiple resource constraints and other project interactions. Too often, financial measures are made based solely on criteria such as Net present Value (NPV) and Internal Rate of Return (IRR). Mathematical programming models often solve an integer linear programming to determine the optimal composition of the options subject to resource and other constraints. MCDM models (Keeney & Raiffa, 1999), on the other hand, consider the multi-criteria project values. For data which cannot be precisely assessed, fuzzy sets (Zadeh, 1965) can be used to denote them. The use of fuzzy set theory allows us to incorporate unquantifiable information, incomplete information, non-obtainable information, and partially ignorant facts into the decision model. The first four approaches offer the ability to rate PRSs with a quantitative monetarily unit. Henriksen & Traynor (1999) found that decisions made by managers and those made by a multi-criteria decision making model differ. These differences reflect that such techniques typically do week in simulation of the reality about the projects. It seems the risky world about the projects is usually neglected during the evaluation. In most of the real-world problems, projects are multidimensional in nature and have risky outcomes and decisions and must consider strategy and multidimensional measures (Meade & Presley, 2002).

It is stressed that most significant risks will be subjected to quantitative risk analysis of their impact on project (Project Management Institute [PMI], 2008; United State Department of Energy [US DOE], 2005). Several quantitative models have been introduced to provide valuable predictions for decision-makers. The most common risk valuation technique is expert elicitation. Using this method, the magnitude of consequences may be determined, through the use of expert's opinions. This could be applied using techniques such as interviewing (PMI, 2008). Risks can be represented by probability distribution functions. According to Kahkonen (1999), probability distributions are not widely used, because they are perceived to unlink the assessment from every-day work of project managers. To avoid direct application of probability distributions, the point-estimates (Kahkonen, 1999) are developed such as the Program Evaluationand Review Technique (PERT). Also, Critical Chain Project Management (CCPM) uses the same statistical basis as PERT, but only uses two estimates for the task duration, which are the most likely and the low risk estimates. Many assessment approaches deal with cost and schedule separately in order to simplify the process. Despite this, approaches such as the proposed method by Molenaar (2005) consider both cost and schedule, although schedule modeling tends to be at the aggregate level. Another method to deal with uncertainty is contingency allowance that is an amount of money used to provide for uncertainties associated with a project. The most common method of allowing for uncertainty is to add a percentage figure to the most likely estimate of the final cost of the known works. The amount added is usually called a contingency (Thompson & Perry, 1994).

The present paper introduces a technique to identify the PRS efficient frontier and choose the desirable scheme. According to the introduced model, in responding the question of "which PRS is the desirable option to execute the project?" the decision maker wishes to simultaneously satisfy two objectives, time and cost, with considering positive and negative risks. Most often, these multi-objectives will be in conflict, resulting in a more complicated decision making task. For this purpose, a new modeling approach is proposed to estimate the expected impacts of project risks quantitatively in terms of the project cost and the project time. This framework incorporates Directed A-cyclic Graph (DAG) into the Overall Project Risk (OPR) concept.

2. The proposed modelling approach

Fig. 1 presents process of the proposed model including six phases. The proposed model is structured based on a screening mechanism including three filters as presented in Fig. 2.


Figure 1.

Process of the proposed technique including six phases


Figure 2.

Screening mechanism of the proposed model

2.1. Designing the alternative PRSs

In the first phase of the process, the project analysts consider different core managerial functions of project and, design the alternative PRSs. Core managerial functions in the field of business and strategic management are (Jaafari, 2007):

  • Customers and markets,

  • Stakeholders,

  • Technology,

  • Facility design and operational requirements,

  • Supply chain system,

  • Learning and innovation,

  • Finance,

  • Project delivery strategy,

  • Risks and due diligence.

Besides, core managerial functions in the field of implementation management are:

  • Governance and leadership,

  • Engineering, detail design and specifications,

  • Procurement, transportation and warehousing,

  • Planning and control,

  • Team performance,

  • Information and communication management,

  • Quality management,

  • Offsite management,

  • Risk management.

2.2. Removing the infeasible PRSs

Some of the designed PRSs may be operationally (technically, conceptually, socially, politically, etc.) inconsistent to implement, so should be removed from the candidate list. The following instances are some inconsistent cases which are experienced in real-world projects:

  • An assumed material and a given processing technology may be technically inconsistent.

  • Due to some political circumstances, two contractors may keep away to incorporate in a common partnership contract.

  • An assumed agent who has not enough experiences should not be assigned for managing a discipline.

  • A special mechanical tool may be infeasible to operate in a moist climate.

2.3. Evaluating the Feasible PRSs

In the third phase of the process, including computational core of the model, all of the feasible PRSs are separately evaluated. For a given PRS, it carried out the following stages as shown in Fig. 3:


Figure 3.

The evaluation process of an individual PRS

Stage 1: Create the project Work Breakdown Structure (WBS): Complex projects can be overwhelming to the project managers. Instinctively, many project analysts break project down into smaller, more manageable parts. These decompositions are called breakdown structures (US DoE, 2005). WBS is a top-down hierarchical chart of tasks and subtasks required to complete project. WBS can focus on a product, a function, or anything describing what needs to be accomplished (PMI, 2008).

Stage 2: Schedule the project and, calculate Scope Duration (SD):A scheduling methodology defines the rules and approachesfor project scheduling. Scheduling is carried out in advance of the project commencing and involves:

  • Identifying the activities that need to be carried out;

  • Defining activities dependencies which its result is the so called preceding or succeeding activity list.

  • Drawing activities network which its result is a graphical portrayed set of activity relationships.

  • Estimating how long the activities will take which its result is the so called activity duration.

  • Allocating resources to the activities;

  • Applying a technique to calculate the earliest/latest start and finish dates of each activity. The present model recommends the better known techniques include Critical Path Method (CPM) or Critical Chain (PMI, 2008).

After scheduling, the project aim on time (SD) will be obtained.

Stage 3: Create the project Cost Breakdown Structure (CBS) and, calculate Scope Cost (SC): The proposed model uses CBS to measure cost elements. Each item in WBS is generally assigned a unique identifier; these identifiers can provide a structure for a hierarchical summation of costs and resources (PMI, 2008). Therefore, CBS represents the hierarchical breakdown of the project costs, so CBSis derived from WBS. After establishing CBS, the target cost of project (SC) will be obtained.

Stage 4: Identify the project risk events: Risk event is an uncertain event or condition that, if it occurs, has a positive or negative effect on at least one project objective: scope, schedule, cost, and quality (PMI, 2008). In the proposed model, risks that have direct or indirect effects on the time and cost of project will be considered. For identifying the risks, the analyzer may benefit from typology of risks mapped in Risk Breakdown Schedule (RBS). For instance, the list below presents a useful typology of common project risks (Mc-Connel, 1996):

  • Schedule creation risks such as "excessive schedule pressure reduces productivity".

  • Organization and management risks such as "project lacks an effective management sponsor".

  • Development environment risks such as "facilities are not available on time".

  • End user risks such as "end user ultimately finds product to be unsatisfactory, requiring redesign and rework";

  • Customer risks such as "customer has expectations for development speed that developers cannot meet ";

  • Contractor risks such as "contractor does not buy into the project and consequently does not provide the level of performance needed";

  • Requirement risks such as "vaguely specified areas of the product are more time-consuming than expected";

  • Product risks such as "operation in an unfamiliar or unproved software environment causes unforeseen problems";

  • External environment risks such as "product depends on government regulations, which change unexpectedly";

  • Personnel risks such as "problem team members are not removed from the team, damaging overall team motivation";

  • Design and implementation risks such as "necessary functionality cannot be implemented using the selected code or class libraries; developers must switch to new libraries or custom-build the necessary functionality";

  • Process risks such as "management-level progress reporting takes more developer time than expected";

Stage 5: Create project risks network and, calculate risks probabilities: Two following criteria are used to characterize risks:

  • Risk probability that is the probability of occurring risk event (Kerzner, 2009).

  • Risk impact that is the impact of occurring risk event (Kerzner, 2009).

In the proposed model, risk impact reflects the magnitude of effects, either negative or positive, on SC and SD if a risk event occurs. For calculating the risk probability and the risk impacts, the model uses risks network that is a DAG with the following considerations:

  1. DAG is a graphG(N,A), where N={E1,E2,,Em} is a finite set of nodes andAN×Na set of arcs. Each nodeEi(i=1,2,3,,m)refers to a risk event and each arc(Ei,Ej)A indicates direct conditional dependencies between two risk eventsEiandEj. If two nodesEiandEjwithin arc(Ei,Ej)are ordered, then the arcs have a direction assigned to them. This is called a directed graph. For a given arc(Ei,Ej)A, the nodeEi is called parent node and the nodeEjis called child node.

  2. A conditional probability ofPijwhich equalsP(Ej|Ei)is placed for each arc(Ei,Ej).Also, for each nodeEia free probabilityPi(i=1,2,3,,m)is dedicated that is the probability of its occurrence due to risk sources outside risks network. We assume that bothPiandPij are point estimates or the mean value of a Probability Density Function (PDF) provided by simulation techniques such as the Monte Carlo analysis (PMI, 2008).

  3. Risks network accepts only the acyclic relationships among the risk events. A cycle within a graph is a path that starts and ends at the same node.

Path is a sub-graph of risks network including series of nodes where each node is connected to another node by an arc and all connecting arcs are unidirectional. Each node can occur in the path once only. Each path starts with a source event and ends with a sink event. A path could be depicted as continuumEi1Ei2Ei3EiK. To simplify this continuum, it could be presented asi1i2i3iK. We also, denote a specific path asPatht(t=1,2,3,,T), whichT is the number of the paths within risks network. All paths are placed in the set of R as (Eq. 1).


In a path, the first node is called source and the last node is called sink. As (Eq. 2) and (Eq. 3), the functions Source()andSink()respectively indicates the source event and the sink event of a path.


As Eq. 4 and Eq. 5 setSiincludes all the paths starting with risk eventEiand setFi includes all the paths finishing with risk eventEi.


As Eq. 6, the plus function can be used to add a part to the end of a path.


As in term (Eq. 7) Path1is subset ofPath2, ifSource(Path1)is equal toSource(Path2), and Path1contains the complete structure ofPath2.


According to Eq. 8, each path has a probability, which is defined as the product of free probability of its source event and the conditional probabilities related to its arcs.


Probability of the intersection of some paths equals the product of the probabilities of these paths divided by probabilities of common source event or common arcs. Besides, probability of the union of the paths, simply, could be calculated using conventional set union function.

As Eq. 9, the occurrence probability of an individual risk eventEiequals the probability of union of all the paths ending with this event. Also, as Eq. 10, the occurrence probability of at least one of the events equals union probability of all paths ending with these events. In addition, as Eq. 11, the occurrence probability of all of events equals intersection probability of all paths ending with these events. It should be noted that for the purpose of identifying the paths within risks network, a labeling algorithm is considered.


For the purpose of identifying the paths within risks network, a labeling algorithm is considered as Fig. 4, in whichFi is the set of labels for Ei(see Eq. 5); Biis a binary index that equals zero until the algorithm completes labeling of risk eventEi. To create the label of a given risk eventEi, if(Ej,Ei)A, as term (Eq. 12), the part “i ” is added to the end of the labels for risk eventEj. The algorithm does create any labels for a risk event that its free probability is equal to zero.


Figure 4.

The labeling algorithm to identify the paths within risks network

Stage 6: Calculate Ultimate Schedule (UD) & Ultimate Cost (UC): UC is the ultimate state of the project cost with considering risk events. UD is the ultimate state of the project duration with considering risk events. The project owners may be interested in knowing the total risk of their project. Indeed, it is often desirable to combine the various risk events into a single quantitative project risk estimate. This estimate is OPR that may be used as input for a decision about whether or not to execute a project, as a rational basis for setting a contingency, and to set priorities for risk response actions (US DOE, 2005). The proposed technique uses the OPR for calculating UC and UD. The main concept here is the relationship between two nodes connectedwith a direct arc in risks network. According to Fig. 5, the occurrence of a parent nodeEi affects the occurrence of a child node Ej(forward circuit), consequently, the impacts of occurrence of the child nodeEj, is also transferred to the parent Ei(backward circuit).


Figure 5.

Relationships between child and parent nodes of an arc in risks network

Assume that by use of a suitable level of CBS, the risk impacts on the project cost are as vector (Eq. 13) that is named as Cost Impact Vector (CIV). It should be noted that eachCjCIVis negative value for cost increscent (unwelcome) and is positive value for cost decrement (welcome). The risk analyst can establish the cost matrix (Eq. 14) in which the rows indicate risk events and the columns stand for the elements of vector (Eq. 13). The elements of cost matrix (Eq. 14) are binary parameterscijas definition (Eq. 15). Using CIV and cost matrix, UC could be calculated as Eq. 16.


For calculating UD, letNNcontain all the risk events that affect the project scheduling. Consider the set β including all non-empty subset of NN as Eq. 17. Now, for allβwβ calculate Eq. 18 in which SDw is the project duration for subsetβw. For calculatingSDw, we should consider the occurrence of all risk eventsEiβw. In Eq. 18, the second partP¨(Ei) indicates that all risk eventsEiβw must have occurred. The double-dots sign on the top of this term means that before calculating this probability we are required to apply some conditions related to the third part of Eq. 18. For calculatingP¨(Ei), temporarily remove all risk events in whichEiN&Eiβw. The third part of Eq. 18 indicates that all risk events in whichEiNandEiβwshould not occur. Finally, UD could be calculated as Eq. 19.


2.4. Creating the PRS efficient frontier

When evaluating a particular PRS in relation to alternative schemes, we can consider the project cost as the first basic measure of performance and the project time as the second one. The PRS efficient frontier is the set of the feasible PRSs that provides a minimum level of project time for any given project cost, or minimum level of project cost for any given level of project time. This concept is most easily pictured using a graph like Fig. 6. In this figure, B, C, D, E, F and G are the alternative feasible PRSs (schemes A and H are the infeasible PRSs which have been removed in the second phase of the process); the PRS efficient frontier is portrayed by the curve B-C-D-E.


Figure 6.

The PRS efficient frontier concept

2.5. Removing the inefficient PRSs

In the 5th phase of the process, the entire inefficient schemes should be removed from the list of candidate PRSs. Regarding the above discussions in previous section, 2.4, any points inside the frontier, like F and G in Fig. 6, represent the inefficient PRSs. F is more efficient than G, but F can be improved on with respect to both project cost and project time (e.g. moving to C).

2.6. Trading off the efficient prss to select the desirable scheme

In the 6thphase of the process, the efficient PRSs should be pair-wise compared. In each pair-wise comparison, one of the PRSs is removed as Eq. 20. The parameter α is defined as the payment (dollars) that project owners will be admitted for one time-unit (i.e. 1 day) increment in the project duration. Moreα results in more importance of the project time than the project cost. Regarding Eq. 20, it should be noted that the desirable PRS is the nearest point to the tangent point between the PRS efficient frontier and the line by gradientα1.

3. Analytical results

For analyzing the model, we consider a project includes Engineering, Procurement, and Construction (EPC) of a powerhouse cavern elevator, which has been drawn from a hydro-mechanical power plant. The project includes four sub-products cabin, hoisting machine, suspension guides and control equipments.

The entire outputs of the process phases are at one glance mapped in Table 1 that presents that twelve PRSs were designed.

Phase 1: The project experts considered the following alternatives to design candidate PRSs. They designed twelve PRSs (see Table 1).

  • Two alternatives for supplying the elevator cabin:

  • (a1) fabricating the cabin in the firm and then transporting it to the erection site;

  • (a2) fabricating the cabin in the erection site.

  • Three alternatives for supplying the elevator hoisting machine:

  • (b1) buying the hoisting machine from the foreign supplier 1;

  • (b2) buying the hoisting machine from the foreign supplier 2;

  • (b3) buying the hoisting machine from the present inside supplier.

  • Two alternatives for basic designing the control equipment:

  • (c1) employing a sub-contractor for basic designing the control equipment;

  • (c2) buying a present basic design.

PRS contentsFeasibilityUC ($)UD (days)EfficiencyDesirability
S1(a1), (b1), (c1)Feasible148,900540Inefficient-
S2(a1), (b1), (c2)Infeasible----
S3(a1), (b2), (c1)Feasible137,000390EfficientUndesirable
S4(a1), (b2), (c2)Feasible165,800485Inefficient-
S5(a1), (b3), (c1)Feasible125,975525EfficientUndesirable
S6(a1), (b3), (c2)Feasible192,900340EfficientUndesirable
S7(a2), (b1), (c1)Infeasible----
S8(a2), (b1), (c2)Feasible158,800350EfficientDesirable
S9(a2), (b2), (c1)Infeasible----
S10(a2), (b2), (c2)Feasible175,698490Inefficient-
S11(a2), (b3), (c1)Feasible138,000500Inefficient-
S12(a2), (b3), (c2)Feasible210,550335EfficientUndesirable

Table 1.

Table 1. Thedesigned PRSs for the typical project

Phase 2: The operational discussions about the feasibility of the schemes resulted in the schemes S2, S7 and S9 are not feasible to execute; consequently, these schemes were removed from the candidate list.

Phase 3: The nine feasible PRSs were evaluated. As a sample, table 2 exhibits the WBS, Fig. 7 shows the CBS and, Fig. 8 shows the risks network for PRS S4. According to Table 2, for PRS S4, SC=137,700 $ &SD=420 days; by considering the occurrence of the risk events, UC=137,700 $ and UD=485 days (see Table 1). Table 1 shows UC and UD for the nine feasible PRSs.

Phase 4: The nine feasible PRSs have beenportrayed in Fig. 9.

No.WBS codeActivityDuration
Cost ($)
11Powerhouse cavern elevator420137,700
41.1.2Material supply9023,000
51.1.3Manufacturing & Assembly3104,000
61.1.4Transportation to erection site102,000
81.2Hoisting machine40129,500
101.2.2Material supply11012,800
111.2.3Manufacturing & Assembly502,200
121.2.4Transportation to erection site171,300
141.3Suspension guides38148,000
161.3.2Material supply1152,600
171.3.3Manufacturing & Assembly15519,200
181.3.4Transportation to erection site191,400
201.4Control equipment24021,800
221.4.2Material supply1005,100
231.4.3Manufacturing & Assembly754,500
241.4.4Transportation to erection site151,100

Table 2.

The project WBS including durations and costs for PRS S4


Figure 7.

A part of the CBS for PRS S4


Figure 8.

The risks network for PRS S4 (left) and its labels (right)


Figure 9.

The PRS efficient frontier for the typical project

Phase 5: The schemes S1, S4, S10 and S11 were considered as the inefficient PRSs and were removed from the candidate list of the PRSs.

Phase 6: For choosing the desirablePRSamong the reminded schemes S3, S5, S6, S8 and S12, the experts did the pair-wise comparisons as Eq. 19. By assumingα=2200 $/day, for instance the term ((158,800-137,000)/(390-350))=545 $/day was calculated for the pair-wise comparison between the schemes S3& S8. Because 545<α&350<390 thus PRSS3 was removed; in pair-wise comparison between PRSsS6&S8, because 3410>α&158,800<192,900 thus PRSS6 was removed; in comparison between PRSsS5&S8, because 188<α&350<525 thus PRSS5 was removed and finally, in comparison between PRSs S8&S12, because 3450>α&158,800<210,550 so PRS S12 was removed. FinallyPRS S8 was considered as the desirablescheme. The selected scheme, PRS S8, contains fabricating the cabin in the erection site, buying the hoisting machine from the foreign supplier 1, and buying a present basic design for control equipment.As it has been shown in Fig. 9, the PRS S8 is the nearest point to the tangent point between the efficient frontier and the line with gradient-1/2200.

4. Discussions

Several characters of the proposed model are worthwhile emphasizing:

  • The risk researchers believe that project risk analysis should be strongly integrated to the project elements (Chapman & Ward, 2003;Kerzner, 2009; Seyedhoseini et. al., 2008 a2008b,;Ward & Chapman, 2003). In our approach, WBS plays a central role in the quantification of risks. So, the main contribution of the proposed technique is in demonstrating how overall project plan and project risk analysis could be integrated through a united framework. It should be explained that a common technique in estimating the risk probability and risk impact is the use of scales that are usually quantified directly through the expert elicitation. We believe that there is a gap between the scale tablets and the expert’s opinion. The proposed model acts a means for bridging the mentioned gap.

  • Another key feature of the model is explicitly allowing for dependency relationships among risk events. This is made possible by using DAG.

  • The model considers both upside and downside risks within a united perspective. Therefore one can observe that this perspective is a step toward the uncertainty management (Ward & Chapman, 2003).

  • Regarding the project environment, since no data record was available about project risk analysis in previous similar projects, probability distribution elicitation for task duration or cost may be difficult for projects, which in turn could limit the applicability of techniques. According to Chapman & Ward (2003), too often this precision is false, because the initial data may be too vague to be fitted into a probability function or the assumptions behind the distributions do not hold true. So, in the proposed technique, all of input data to the model is considered to be one-point estimates. These estimates areeasy to understand (Kahkonen, 1999), and do not include a range of values, standard deviation and variance, or confidence intervals, so they do not include the effects of uncertainty and are simply based on the summation of a number of point estimates for items of work.

The technique presented here can be expanded to allow for additional features of the problem.

  • Based on the two-polar concept of project risk management (Seyedhoseini et al., 2008a), one such extension is considering the implementation of risk response actions to calculate UC and UD that results in more effective the technique.

  • Another extension of the model aims to address the cyclic dependencies among the risk events. Naturally when cyclical feedbacksareconsidered, it is more difficult but more useful.

  • Finally we recall that the proposed model does not guarantee the inclusion of the quality aspects of project. It could be worthwhile to investigate the risk impacts on the project quality. Regarding this area, the reader is encouraged to study work ofSeyedhoseini et al. (2008 b).

5. Conclusion

Most of the real-world projects are multidimensional in nature and include many risky phenomena, whilein the state-of-the art of Project Roadmap Scheme (PRS) selection, risks are usually neglected.In this chapter, we proposed arisk-based modeling approach to support evaluating the alternative PRS and choosing the desirable scheme.In the proposed model, the PRSs are designed then, within a screening mechanism including three criteria of feasibility, efficiency and desirability are filtered. The project cost and the project time play a central role to identify the PRS efficient frontier. The chapteralso introduced the development and application of Directed Acyclic Graph (DAG) for estimation of the expected impacts of the project risks. The main contribution of this research was in demonstrating how project plan and Overall Project Risk (OPR) could be integrated through a united framework. We conclude that applying the proposed model helps the project experts to evaluate the feasible PRSs and to choose the desirable scheme in most effective and productive manner dealing with in real world’s uncertainties.


1 - Chapman, C.B.,& Ward, S.C. 2003.Project risk management: processes, techniques and insights Edition), 978-0-47085-355-9 John Wiley, Chichester (UK).
2 - D. Dvir, T. Raz, A. J. Shenhar, (2003).An empirical analysis of the relationship between project planning and project success, International Journal of Project Management, 21 2 8995 ).
3 - A. Henriksen, D., A. J. Traynor, 1999 A practical R&D project selection tool.IEEE Transactions on Engineering Management, 46 2 158170 ).
4 - M. Hopkinson, 2006 Top down techniques for Project Risk management, PMI Global Congress, Madrid (Spain), September 1 2006.
5 - A. Jaafari, 2007 Project and program diagnostics: a systemic approach, International Journal of Project Management, 25 8 781790 ).
6 - K. Kahkonen, 1999 Integration of qualitative and quantitative risk analysis, 15th Conference of the International Federation of Operational Research Societies, Beijing (China).
7 - R. L. Keeney, H. Raiffa, (1999, (1999).Decisions with multiple objectives: preferences and value trade-offs Edition), 978-0-52143-883-7 Cambridge University Press, UK.
8 - H. Kerzner, management. a. Project, approach. systems, planning. to, scheduling, controlling, 2009 Edition), 978-0-47027-870-3 Wiley, TX (USA).
9 - Markowitz, H.M. (2002).Portfolio selection: efficient diversification of investments Edition), Blackwell Publishers Ltd., 978-1-55786-108-0 Massachusetts (USA).
10 - S. Mc -Connel, development. Rapid, wild. taming, schedules. software, 1996 Edition), Microsoft Press, 978-1-55615-900-8Washington (USA).
11 - L. Meade, M., A. Presley, 2002 R&D project selection using the analytic network process.IEEE Transactions on Engineering Management, 49 1 5966 ).
12 - K. Molenaar, 2005 Programmatic cost risk analysis for highway mega-projects, Construction Engineering and Management, 131 3 343353 ).
13 - PMI (Project Management Institute). 2008 A guide to the project management body of knowledge (4th Edition)978-1-93389-051-7 Newtown Square, PA (USA).
14 - S. M. Seyedhoseini, S.. Noori, M. A. Hatefi, 2008a Two-polar concept of project risk management, In:New Frontiers in Enterprise Risk Management, David L. Olson & Desheng Wu, 6992 ), 978-3-64209-740-9 Springer Berlin Heidelberg, Berlin (Germany).
15 - S. M. Seyedhoseini, S.. Noori, M. A. Hatefi, 2008 An integrated decision support system for project risk response planning, Kuwait Journal of Science and Engineering, 35 2B 171192 ).
16 - Thompson, A.,& Perry, J.G. (1994).Engineering construction risks: a guide to project risk analysis and risk management Edition), 978-0-72771-665-1 Thomas Telford, London (UK).
17 - U.S. DoE (Department of Energy). (2005).The owner’s role in project risk management Edition), National Academies Press, 978-0-30909-518-1 NY (USA).
18 - S. Ward, C., C. B. Chapman, 2003 Transforming project risk management into projectuncertainty management, International Journal of Project Management, 21 2 97105 ).
19 - L. Zadeh, 1965 Fuzzy sets, Information Control, 8 338353 ).