CHAPTER TWO

LITERATURE REVIEW

2.1 The Conceptual Foundations of Projects and Success

2.1.1 The Pervasive Role of Projects in Modern Organizations

Projects are fundamental instruments for implementing change and achieving strategic objectives across
diverse sectors, including construction, engineering, IT, government, and finance. They are temporary,
unique endeavors undertaken to create a specific product, service, or result (PMI, 2008; Turner, 1993).
The shift towards a project-based operational model underscores their critical role in enhancing
organizational efficacy and ensuring long-term continuity (Winter, 2006a).

2.1.2 The Evolution of Project Success Criteria

The traditional metric for project success, the "Iron Triangle" of time, cost, and quality, remains
prevalent but is now considered a baseline measure rather than a comprehensive definition. This
perspective, often called project efficiency, primarily serves the vendor's interest and is established
during the project's initial, highly uncertain phases, which can lead to unrealistic benchmarks (Pinto,
2007; Turner & Cochrane, 1993).

A more holistic, multi-dimensional view of success has gained prominence. This paradigm expands the
definition to include:

Impact on the Customer: Does the deliverable meet the client's needs and provide intended value?

Business Success: Does the project achieve its strategic business objectives and deliver a strong return
on investment?

Preparing for the Future: Does the project enhance the organization's capabilities, reputation, or market
position?

This shift acknowledges that a project can be efficient (on time, on budget) yet ultimately fail if it does
not deliver value or satisfy its stakeholders (Shenhar & Dvir, 2007).

2.2 The Centrality of Stakeholder Satisfaction in Project Success

2.2.1 Defining and Measuring Stakeholder Satisfaction

Stakeholder satisfaction has emerged as a paramount, overarching criterion for project success. It
transcends the delivery of a pre-defined scope to encompass the perceptions and evaluations of all key
parties involved in or affected by the project. This includes the client, end-users, project team, sponsors,
and contractors (Baker, 1988; Lim & Mohamed, 1999).

Measuring satisfaction is inherently subjective and requires assessing whether the project's outcomes
align with the often-diverse expectations and requirements of these different groups. A project cannot
be deemed truly successful if it alienates its users, exhausts its team, or fails to meet the client's
strategic goals, regardless of its adherence to budget and schedule.

2.2.2 The Role of Communication and Expectation Management

Achieving high stakeholder satisfaction is intrinsically linked to effective communication and expectation
management. Misunderstood requirements, unclear objectives, and lack of engagement are frequently
cited sources of risk that directly lead to stakeholder dissatisfaction (Addison & Vallabh, 2002). Proactive
risk management, therefore, must include processes for managing stakeholder expectations and
ensuring continuous alignment throughout the project lifecycle.

2.3 Understanding Project Risk

2.3.1 The Inherent Nature of Risk in Projects

Risk is an intrinsic element of all projects, present throughout every phase of the project lifecycle from
initiation to closure. It represents any uncertain event or condition that, should it occur, has a positive or
negative effect on project objectives, including the critical objective of stakeholder satisfaction (PMI,
2013). This definition acknowledges the dual nature of risk: as a threat (negative impact) and an
opportunity (positive impact).

2.3.2 Conceptualizing Risk and Uncertainty

The concept of risk is multifaceted, with definitions varying across contexts. Fundamentally, risk
originates from uncertainty—the state between complete knowledge and total ignorance (Wideman,
1992; Perminova, 2008). This uncertainty can be categorized as:

Aleatoric Uncertainty: Inherent, probabilistic variability.

Epistemic Uncertainty: Uncertainty due to a lack of knowledge or information, often relating to

2.4 The Discipline of Project Risk Management

2.4.1 The Strategic Imperative of Risk Management

Risk Management (RM) is an integral component of sound project management, essential for achieving
project objectives and maximizing stakeholder satisfaction. It is a proactive, systematic process designed
to identify, analyze, and respond to project risks, thereby increasing the likelihood of positive outcomes
and minimizing the consequences of adverse events (Kerzner, 2009; PMI, 2008).

The benefits of effective RM are substantial and directly contribute to success: enhanced control,
improved decision-making, reduced surprises, protected business value, and, crucially, a clearer
understanding of potential pitfalls that could alienate stakeholders (Cooper, 2005; Thomas, 2006).
Conversely, the absence of proactive RM is a leading contributor to project failure and stakeholder
dissatisfaction (Kutsch, 2008; Whittaker, 1999).

2.4.2 The Risk Management Process Framework

The RM process is a structured cycle of interconnected activities. The core phases, as synthesized from
PMI (2008), Cooper (2005), and Didraga (2013), are:

Risk Management Planning: Defining how to conduct RM activities for the project.

Risk Identification: Determining which risks may affect the project and its stakeholders. Techniques
include brainstorming, stakeholder interviews, checklists, and the Delphi technique.

Risk Analysis: Evaluating risks to determine their probability and impact on all project objectives,
including satisfaction.

Qualitative Analysis: Prioritizing risks through subjective assessment (e.g., probability/impact matrices).

Quantitative Analysis: Numerically analyzing the effect of identified risks. Despite its value, it is often
underutilized (Bannerman, 2008).

Risk Response Planning: Developing actions to enhance opportunities and reduce threats. Core
strategies include Avoidance, Mitigation, Transfer, and Acceptance.

Risk Monitoring and Control: Tracking identified risks, monitoring residual risks, identifying new risks,
and evaluating the effectiveness of the RM process throughout the project lifecycle.
2.5 The Empirical Link between Risk Management and Project Success

A substantial body of empirical evidence confirms a strong positive correlation between effective risk
management practices and multi-dimensional project success. Key findings indicate that:

RM practices contribute to more accurate time and cost predictions (project efficiency) (Cooke-Davies,
2000; Ropponen & Lyytinen, 1997).

By identifying risks related to requirements and scope, RM directly safeguards client and user
satisfaction (Addison & Vallabh, 2002).

Projects that employ formal RM are significantly more successful in achieving their business and
strategic objectives (Elkington & Smallman, 2002; Rabechini & Monteiro, 2013).

The early application of RM in the project lifecycle yields greater benefits for overall outcomes (Mudau
& Pretorius, 2009).

The presence of a dedicated risk manager can positively impact project outcomes and stakeholder
confidence (Rabechini & Monteiro, 2013).

However, studies in specific contexts, such as Ethiopia (Frezewed, 2016; Getachew, 2014; Yimam, 2014),
reveal that formal RM practices are often poorly implemented or underdeveloped, relying instead on
informal methods, which limits their effectiveness in securing broad project success.

2.6 Conceptual Framework and Model Development

Building upon the established literature, this research adopts a conceptual framework where Project
Risk Management Practice (the independent variable) is operationalized through its core processes:
Planning, Identification, Analysis, and Control/Response (PRP, PRI, PRA, PRCR).

This variable is hypothesized to have a significant impact on Project Success (the dependent variable),
now measured by a modern, multi-dimensional set of criteria:

PS1: Efficiency Success: Completion within time and budget.

PS2: Product Success: Meeting quality standards and technical performance.

PS3: Stakeholder Satisfaction: The level of satisfaction among key stakeholders (client, end-users, team).

PS4: Business Success: Achieving the intended business benefits and strategic objectives.

The enhanced mathematical model for the study is expressed as:

PS = f(PRM) = f(PRP, PRI, PRA, PRCR)

PS = Project Success (a composite of PS1, PS2, PS3, PS4)

PRM = Project Risk Management

PRP = Risk Planning

PRI = Risk Identification

PRA = Risk Analysis

PRCR = Risk Control and Response

This model will be used to test the hypothesis that a structured approach to risk management is a critical
determinant of successful project outcomes across all dimensions, with a specific focus on its vital role in
achieving stakeholder satisfaction.
CHAPTER THREE

RESEARCH METHODOLOGY

This chapter outlines the methodology employed for the study. It details the rationale for the research,
the approach taken, and the data sources utilized. The chapter includes sections on the research design
and approach, data collection procedures, target population, sample size and sampling techniques, data
types and sources, methods of data analysis, and the ethical considerations upheld during the study.

3.1 Research Approach

This study employed a mixed-methods approach, integrating both deductive and inductive reasoning, as
well as quantitative and qualitative data.

A deductive approach begins with a theoretical foundation, from which hypotheses are derived and
subsequently tested through empirical data. Conversely, an inductive approach aims to develop theory
from the analysis of collected data. In practice, these approaches are often complementary rather than
mutually exclusive. This study utilized a deductive approach by testing hypotheses concerning the
impact of risk management practices on project success. Simultaneously, an inductive approach was
applied by gathering qualitative data from stakeholders to understand the practical implementation of
risk management and other influencing factors in the specific context of eastern Amhara's construction
sector.

Regarding data types, quantitative research generates numerical data, often collected through
techniques like questionnaires and analyzed using statistical methods to explain phenomena and test
hypotheses (Aliaga & Gunderson, 2005). Qualitative research, in contrast, is concerned with the
subjective assessment of attitudes, opinions, and behaviors to gain deeper insight into a phenomenon.
This study primarily utilized a quantitative method for hypothesis testing, supplemented by qualitative
insights from interviews to enable a more comprehensive interpretation and presentation of the
findings, including exploring unspecified variables that may influence outcomes.

3.2 Research Design

The research design serves as the logical framework that connects the empirical data to the initial
research questions (Yin, 2009). It is the blueprint for the collection, measurement, and analysis of data
(Kothari, 2004). To effectively address the research questions and achieve the study's objectives, a
combined descriptive and explanatory research design was adopted.

The research is descriptive as it details how risk management practices were implemented in various
construction projects in eastern Amhara and presents the success level of these projects based on the
criteria of time, cost, quality, and stakeholder satisfaction. It is explanatory because it seeks to explain
and predict the relationships between risk management practices (independent variables) and project
performance (dependent variables), specifically testing whether these practices affect project success.

3.3 Population, Sample Size and Sampling Techniques

3.3.1 Target Population

The target population is the specific group of individuals or objects from which data is collected to
develop the required information (Hair, 2010). For this study, the target population consisted of
construction projects implemented in the eastern part of the Amhara regional state. The study focused
on projects undertaken by the Eastern Amhara Water Works Construction Enterprise (EAWWCE) and
Zemen Construction Enterprise (ZCE). Project team members, key stakeholders, and risk management
personnel from these sampled projects were the participants who answered the research
questionnaires and interviews.

3.3.2 Sample Size

A representative sample is crucial for obtaining accurate estimates of population values. Experts suggest
a sample size of at least 10-20% of the population for a representative sample (Mugenda, 2000; 2005).
The sample for this study consisted of 20 projects implemented by EAWWCE and ZCE. This represented
approximately 20% of the total projects undertaken by these enterprises, aligning with the
recommended threshold for a representative sample.

3.3.3 Sampling Techniques

A purposive (judgmental) sampling technique was employed. This non-probability sampling method is
suitable for small samples and allows the researcher to use judgment to select cases that best enable
the research questions to be answered (Saunders et al., 2009; Singh, 2006). Projects were selected
based on their relevance, the availability of information concerning their risk management practices and
performance metrics, and to ensure a diversity of stakeholders were represented.

3.4 Data Types and Sources

Both primary and secondary data were used in this study.

Primary Data: was collected directly from project team members and key stakeholders in the sampled
projects using a structured questionnaire. The questionnaire was designed to gather data on project risk
management practices and the perceived success of projects at EAWWCE and ZCE, including the critical
dimension of stakeholder satisfaction. Responses were measured on a five-point Likert scale (1 =
Strongly Disagree to 5 = Strongly Agree). A total of 35 questionnaires were distributed: 30 to project
team members and stakeholders, and 5 to the risk management departments. Thirty-two questionnaires
were properly filled and returned, yielding a high response rate of 91%, which is suitable for robust
analysis.
Secondary Data: was obtained from published and unpublished sources, including enterprise project
management office reports, stakeholder feedback records, academic journals, periodicals, and online
resources. This data provided a baseline for comparing and contextualizing the primary research findings
and helped identify other unspecified variables that may have impacted project outcomes.

3.5 Data Collection Procedures

Primary data collection was conducted using self-administered questionnaires. The structured
instrument, comprising both closed and open-ended questions, was adopted from established literature
and developed by the researcher. Volunteers were briefed on the study's objectives and ethical
considerations before participating. The questionnaire gathered data on the four key risk management
processes (planning, identification, analysis, and response/control) and project success factors (time,
cost, quality, and stakeholder satisfaction). Semi-structured interviews were also conducted with
selected individuals to gain a fuller, qualitative understanding of the projects under study and to probe
for other unspecified variables (e.g., political factors, environmental conditions, community relations)
that may have influenced results. Secondary data was collected through a comprehensive review of
relevant documents from the enterprises and academic literature.

3.6 Data Analysis

Data analysis is the process of making sense of collected data to draw inferences and answer research
questions (Bogdan & Biklen, 1982). The collected data was first checked for completeness and coded for
analysis.

The analysis employed two main techniques:

Descriptive Statistics: Data for both dependent and independent variables were summarized using
frequencies, percentages, means, and standard deviations. Results were presented using tables, bar
charts, and graphs.

Inferential Statistics: To test the hypotheses and examine the relationships between variables, Pearson’s
correlation coefficient was used to measure the strength and direction of associations. Furthermore,
regression analysis was employed to test the hypotheses and determine the impact and relative
importance of the independent variables (risk management practices) on the dependent variables
(project success). Qualitative data from open-ended questions and interviews were analyzed
thematically to identify patterns and insights related to stakeholder satisfaction and other unspecified
variables.

Variables:

Dependent Variables (Project Success): Time, Cost, Quality, Stakeholder Satisfaction.

Other Variables: Qualitative data was also analyzed to account for unspecified variables that emerged
during data collection as potential influencers on project outcomes.

3.7 Validity and Reliability

Validity refers to the degree to which an instrument measures what it is intended to measure. Reliability
is the extent to which an instrument yields consistent results upon repeated measurements (Carmines &
Zeller, 1979).

A pilot study was conducted with ten individuals to test and refine the research instrument. This helped
identify ambiguities, ensure questions were understood, and confirm that the instrument measured the
intended constructs, including the new dimension of stakeholder satisfaction. To ensure reliability,
internal consistency was measured using Cronbach's Alpha via SPSS version 16. A value above 0.6 is
considered acceptable for satisfactory internal consistency reliability (Nunnally & Bernstein, 1994). The
overall Cronbach's Alpha for the instrument was 0.85, indicating high reliability.

Table 3.1: Reliability Statistics

Cronbach's Alpha N of Items

0.850 10

Source: Researcher’s Survey (2023)

3.8 Ethical Considerations

Ethical research practice involves behaving appropriately concerning the rights of those who are the
subjects of the work (Saunders et al., 2009). This study adhered to the following ethical principles:

Confidentiality and Anonymity: Participants and their organizations were guaranteed confidentiality, and
their identities were kept anonymous. Data collected was not shared with competitors or any
unauthorized parties.

Informed Consent: Participants were briefed on the study's objectives before agreeing to take part.

Integrity in Reporting: The researcher maintained truthfulness by ensuring no fabrication, falsification,