Chapter 1: Introduction

The Ethiopian construction sector, like many other developing countries, has
numerous problems and obstacles that are similar to those faced by other developing
sectors. It is possible that nations may implement more rigorous measures. The
construction industry plays a pivotal role in modern societies, encapsulating the vital
function of building infrastructure and catalyzing economic growth across various
sectors. In order to help the industry in those nations enhance its effectiveness, it is
essential to prioritize efforts towards improving its performance. In the construction
industry, contractors hold a significant position as key stakeholders responsible for
the creation and implementation of building projects. In order to attain the end
product, any endeavors towards the advancement and enhancement of the industry
must be undertaken.

The private sector is using its capital to purchase a variety of fixed assets,
including new machinery and equipment, new buildings being built, and building
maintenance tasks. Ethiopia's construction industry has made significant contributions
to reducing poverty, expanding employment through the growth of small and
medium-sized businesses, and creating jobs. For effective construction industry
development to establish effective project management system has play a crucial role
for competitive advantage of construction firms. Improving the contractor’s project
management capability can significantly contribute to the overall improvement of
contractor’s capacity to deliver successful projects. Any project's success is
determined by how quickly it is completed, how much it costs, and how well it
performs in accordance with the original design.

Highway construction assessment in Ethiopia focuses on challenges like land

acquisition (Right of Way), contract management, financing, and stakeholder
coordination, while management involves implementing structured project
management, adopting technology, capacity building, and strengthening procurement
reforms (MAPS), with a strong push from the Road Sector Development Program
(RSDP) for better performance, quality, and asset management to drive economic
growth.

Traditional project management is a structured, step-by-step approach to managing

projects, relying on well-established techniques for planning, estimating, and
controlling activities. Its primary objective is to deliver results on time, within budget,
and according to predefined specifications.

Key Characteristics of Traditional Project Management

 Linear Sequence: Stages are completed one after another. A phase must typically
be finished before the next begins.
 Detailed Upfront Planning: Extensive planning happens before execution starts to
predict risks and resources.
 Fixed Scope: Changes to project requirements are discouraged and strictly
managed once the project is underway.
 Documentation-Heavy: Heavy emphasis on comprehensive documentation, such
as project plans, specifications, and reports.
  Control Mechanisms: Strict monitoring of project progress against the initial plan
(e.g., Gantt charts, milestones).
 Phase-Gate Process: Progression to the next stage often requires approval.

Common Methodologies

 Waterfall: The classic, linear step-by-step approach.

 Prince2: A structured, process-based, and heavily documented method.
 PMBOK(Project Management Body of Knowledge): A framework defining
standardized practices.

Advantages

 Predictability: Clearly defined milestones and deliverables.

 Clear Structure: Well-defined roles, responsibilities, and documentation.
 Efficient for Stable Requirements: Ideal when the goal and path are known.

Disadvantages

 Inflexibility: Difficult to adapt to changes or new information once in progress.

 Late Testing: Testing or review often happens late in the cycle, which can cause
significant delays if issues are found.
 Limited Stakeholder Involvement: Often, stakeholders are heavily involved only
at the beginning and end.
 Traditional project management relies on established techniques for managing
projects where predictability is paramount.

This methodology is best suited for projects where tasks can be completed in a
sequential order and changes are minimal or unlikely. Because it is based on
predictability, it emphasizes careful upfront planning and strict adherence to the
project plan once execution begins.

Traditional project management typically follows the same five-phase life-cycle:

1. Initiating – defining goals, scope, and stakeholders.

2. Planning – creating detailed schedules, budgets, and resource allocations.
3. Executing – carrying out the planned tasks and deliverables.
4. Controlling/Monitoring – tracking progress, managing risks, and ensuring compliance
with the plan.
5. Closing – finalizing deliverables, evaluating results, and formally completing the
project.
 Agile project management is an iterative and flexible approach that breaks large
projects into smaller, manageable chunks (sprints/iterations) for faster, adaptable
delivery, focusing on collaboration, customer feedback, and continuous improvement,
unlike rigid linear methods, allowing teams to respond quickly to change and deliver
value early. It emphasizes individuals, working product, customer collaboration, and
responding to change, as outlined in the Agile Manifesto, and uses frameworks like
Scrum or Kanban.
Key Characteristics & Principles:
 Iterative & Incremental: Projects are developed in short cycles (sprints, usually 1-
4 weeks) that produce working increments, allowing for early releases and
feedback.
 Adaptability: Embraces changing requirements and pivots easily, making it ideal
for dynamic environments like software development
 Collaboration: Fosters close teamwork between developers, stakeholders, and
clients.
 Customer Focus: Prioritizes customer collaboration and feedback to ensure the
final product meets needs.
 Self-Organizing Teams: Empowers cross-functional teams to manage their work.
Common Frameworks:
 Scrum: Uses sprints, daily stand-ups, and specific roles (Scrum Master, Product
Owner).
 Kanban: Visualizes workflow on a board (e.g., To Do, Doing, Done) to manage
flow.
Benefits:
 Faster delivery of value.
 Higher quality through continuous testing and feedback.
 Increased flexibility and reduced risk.
 Better alignment with business goals.

Team Collaboration and Self-Organization

A hallmark of Agile principles is emphasizing self-organizing teams and team

empowerment. Autonomy in Agile guarantees teams make decisions collaboratively
and efficiently.
Cross-functional collaboration brings together experts from different areas to create
one product. Trust and communication are key, allowing them to focus on product
prioritization and delivering value.

Flexibility in Agile Frameworks and Practices

The Agile Alliance supports different methods. These methods are flexible and suited
to various tasks. You can choose Scrum, Kanban, or a hybrid Agile approach. These
frameworks emphasize feedback and constant improvement during the software
development life cycle.

Teams use methods like Scrum-Kanban to improve workflows and stay flexible.
Following the Agile Manifesto Principles encourages adaptability and responsiveness
to change.

1.1: Background Study

Managing a project is a difficult task (Hayat, et al., 2015). Hayat [Link] (2015) stated
that often, at least one of the variables is sacrificed to meet the other performance
metrics. Moreover, the project management system in underdeveloped countries
differs from that in affluent countries (Assefa, et al., 2015). However, proper project
management methods are essential to mitigate the causes and impacts in highway
construction projects (Kaliba, et al., 2009). According to stud- ies, delays occur in
every construction project, and the magnitude of these delays varies significantly from
project to project (Ankrah, 2017). many authors discussed improper project
management, changes during the construction, inadequate planning, and slow decision
making in the top ten ranked issues. Therefore, project management issues can be
overcome by adopting agile project management to the highway construction project.
 Agile approaches use an iterative and incremental process to development that
allows for improved risk management and dynamically reacts to changing
requirements (Kumara, 2017). The agile manifesto advocated the following four
values stated here, as a set of twelve principles for agile software development (PMI,
2017). The agile Manifesto's values and principles give a solid foundation for
understanding agile (Cobb, 2015). There are four agile manifestos; (1) individual and
interaction over process and tool, (2) working software over comprehensive
documentation, (3) customer collaboration over con- tract negotiation, and (4)
responding change over following plan. Further, the agile practice guide summarized
the 12 principles of agile behind the agile manifesto as follows:-
 The most efficient and effective method of conveying information to and within a
project team is face-to-face conversation.
 Agile processes promote sustainable development. The sponsors, developers, and
users should be able to maintain a constant pace indefinitely
 Business people and developers must work together daily throughout the project.
 Our highest priority is to satisfy the customer through early and continuous
delivery of valuable software.
 Deliver working soft- ware frequently, from a couple of weeks to a couple of
months, with a preference to the shorter timescale
 Welcome changing requirements, even late in development. Agile processes
harness change for the customer's competitive advantage.
 Continuous attention to technical excellence and good design enhances agility.
 Simplicity the art of maximizing the amount of work not done is essential.
 Working software is the primary measure of progress
 Build projects around motivated individuals. Give them the environment and
support they need, and trust them to get the job done.
 at regular intervals, the team reflects on how to become more effective, then tunes
and adjusts its behaviour accordingly
 The best architectures,requirements, and emerge self-designs from organizing
teams

Although these concepts originated in the software sector, they have expanded to
various other industries(PMI, 2017). Moreover, it would be more appropriate to say
that the “agile” movement is motivated by a desire to address the needs of the type of
fast changing and uncertain business environment(HUNT, 2006).

Agile project management is a modernized project management approach that

emphasizes early delivery of business value, continuous product and process
improvement, scope adaptability and flexibility, team collaboration, and delivering
sound quality-tested products that meet customer satisfaction (Layton & Ostermiller,
2017). The agile manifesto's concepts also apply to project management (Dyba, et al.,
2014). Agile project management is a new project management style that offers
various benefits to different organizations when it comes to complicated projects
(Adil & Fatima, 2015). Therefore, despite the fact that agile project management
receives a lot of attention, there is still debate about its actual contribution to the
organization's performance (Serrador & Pinto, 2015).
At the initial level of the project, the project team conducts planning, collects
requirements, and solution design. Afterward, the team is involved with subsequent
rolling waves of iterations that entail more detailed planning, requirements analysis,
design, execution, tests, validate scope, and handover to stakeholders (Salameh,
 2014). Moreover, the four phases of an agile project are feasibility research, planning,
implementation, handover, and close (Salem, 2019). Agile planning is a process for
improving project teams' energy, focus, clarity, and transparency (Phalnikar, et al.,
2008). Moreover, the product backlog, which is used in agile projects throughout the
process, is a prioritized list of the client needs for the project (Johansson, 2012). The
origins of agile process improvement can be traced back to fundamen- tal
improvement concepts such as total quality management (Ringstad, et al., 2011).

Agile project management in highway construction replaces rigid, traditional, linear

methods with iterative, phased workflows that boost flexibility, transparency, and
stakeholder collaboration. By breaking large road projects into smaller, manageable,
and adaptable stages (sprints), it enables quicker responses to unforeseen site
conditions or design changes.

Key Applications of Agile in Highway Construction

 Iterative Planning (Sprints): Instead of one massive, rigid schedule, the project is
divided into shorter, high-intensity cycles. For example, planning, executing, and
reviewing a specific 5-kilometer stretch of road before moving to the next.
 Enhanced Collaboration: Daily stand-up meetings and frequent, constant
communication with stakeholders, clients, and subcontractors.
 Rapid Risk Mitigation: Because progress is reviewed in small chunks (often in short
"sprints"), problems like utility conflicts or material shortages are identified earlier,
reducing potential downtime.
 Handling Uncertainty: Ideal for complex projects (e.g., highway expansion in high-
traffic areas) where conditions change frequently.
Benefits in Road Construction

 Improved Efficiency: Reduced bottlenecks by focusing on actionable, short-term

goals.
 Higher Quality & Flexibility: Continuous feedback loops allow for design
adjustments on the fly rather than waiting for the end of the project.
 Reduced Delays: Faster decision-making, as teams are empowered to act quickly
rather than relying on slow, bureaucratic, linear processes.
 Enhanced Client Satisfaction: Clients are more involved, leading to higher confidence
that the final deliverable meets their needs.
Challenges to Implementation

 Cultural Shift: The construction industry is heavily rooted in traditional, document-

driven ("Waterfall") methods, making the adoption of Agile a major shift.
 Execution Hurdles: While effective in the design phase, implementing Agile in the
actual physical execution of roadwork requires careful coordination of heavy,
expensive, and inflexible, labor-intensive resources.
Recommended Approach
 1. Pilot Projects: Begin applying Agile principles to specific, smaller, or high-
risk segments of a larger highway project to test effectiveness.
2. Use Scrum or Hybrid Frameworks: Implement Scrum (roles, sprints, daily,
and sprint meetings) in combination with existing, effective scheduling tools
to balance speed with logistical needs.
3. Invest in Training: Train project managers in Agile, not just traditional
techniques.

1.2 : Statement of problem

The massive infrastructure expansion of the nation and the impressive construction
activities in major centers has given researchers a chance to examine the construction
industry and its implementers. Highway infrastructure is one of the significant
components of construction and has great contribution to attain sustainable
development of the country economy. Highway is crucial for driving socioeconomic
growth in Ethiopia given its geographic characteristics, habitation patterns, and
economic activities. Access to a better highway system fosters the promotion of both
agricultural and non-agricultural industries and encourages the expansion of all
economic sectors. Ethiopia heavily depends on its road system to provide public
transport.

MoWUD, (2006) the Ministry of Urban Development and Construction stated that the
local and international quality standards, as well as the sector's output expectations,
are not being met by the Ethiopian construction industry. From the beginning to the
end of a construction project, there are specific procedures and challenges that must
be overcome. Among the issues were time and cost overruns (2013) Hussin et al.
Time, cost, quality, client satisfaction, productivity, and safety are just a few of the
concerns and problems that the industry must deal with (Biyadgligh, 2017).

The common Factors Affecting Time and Cost Performance of Road Construction
Projects are inadequate equipment, inadequate managerial skills, project construction
complexity, equipment failure and a lack of materials are the crucial elements
affecting the timely completion/performance of highway construction projects.
(Tewdros) Inflation, inaccurate estimates, dishonest business practices, contractors'
lack of project experience, poor planning, and over design were other key factors
linked to how much highway construction projects cost over-run.(Tewdors) The
success of a project's execution is measured in terms of time, cost, and quality.
Management problems in highway design and construction leads to the failure of
properly anticipate, plan for, and mitigate the negative consequences of project
activities, resulting in significant delays, cost overruns, and quality deficiencies.
These management issues are largely driven by poor coordination between
stakeholders, inadequate planning, and unforeseen external factors.

Based on the finding from various literatures, the practice of construction project
management in Ethiopia found at low level of practice. This research propose to find
a solution by using agile management to enhance flexibility and collaboration in
highway construction.
1.3:Research Question
In relation to the objective of this research, the study addresses the following research
questions in Ethiopian highway construction projects:

 How can agile practices improve a project’s ability to adapt to changes and
variations in highway design and construction?
 What is the impact of agile management on design and construction of highway
to reduce cost over-run and delay?
 How can Building Information Modeling (BIM) be integrated with agile
management to facilitate highway construction and design?
 How can Agile methodologies improve risk identification and response in
complex, high-uncertainty highway projects?
 What are the key drivers and barriers for implementing adaptive, iterative design
approaches in traditional highway design and construction?
 What is the risk of adopting agile management in highway design and
construction?

1.4: Objective of the study

1.4.1. General objective

The general objective of this study is:-

 To identify how agile management could enhance flexibility and

collaboration in Ethiopia highway construction.
 To enhance flexibility and collaboration in highway design and construction
using agile management.

1.4.2. Specific objective

Based on the study's overall goal and the aforementioned research questions, this
study considered the subsequent specific objectives;

 To enhance adaptability of changes in highway design and construction.

 To improve cross-functional team collaboration in highway design and
construction.
 To increase project value and quality in highway design and construction.
 To reduce project risk and delays in highway design and construction.
 To implement iterative design cycles in highway design and construction.
 To assess risk of adopting agile management in highway design and.
construction.
1.5. Significance of the study
These study requires to implement practices by domestic contractors in Ethiopian highway
construction projects in terms of time, cost, quality & scope management. Studying the
enhancement of flexibility and collaboration in highway construction through agile
management is significant because it shifts infrastructure development from rigid, risk-prone,
traditional methods to a responsive, value-driven approach. As highway projects face high
uncertainty, evolving stakeholder requirements, and long life-cycles, integrating agile
principles with concepts such as iterative design, cross-functional collaboration, and
continuous feedback allows teams to adapt to changes, optimize costs, and ensure long-term
functionality.

Key Significance of this Research:

 Improved Adaptation to High Uncertainty: Highway projects often face unpredictable

environmental, social, and technological changes. Agile management allows for flexible,
iterative design, allowing the project to adapt to new information rather than rather
enforcing outdated plans.
 Enhanced Collaboration and Reduced Silos: Traditional highway design often operates in
silos. Agile promotes cross-functional teams (engineers, designers, stakeholders)
working together, fostering a shared understanding, reducing communication barriers,
and improving decision-making speed.
 Value Delivery and Reduced Waste: By using short, iterative cycles (sprints), teams can
produce "Minimum Viable Products" such as a functional section of a road early. This
delivers value sooner, allows for continuous feedback, and eliminates unnecessary,
costly rework.
 Risk Mitigation and Cost Control: Agile encourages continuous risk monitoring and
quick adjustments, which helps prevent massive overruns typical of major infrastructure
projects.
 Better Stakeholder Engagement: By incorporating client feedback through frequent,
regular meetings, the final highway design is more likely to meet user needs, leading to
higher satisfaction.

Core Areas of Focus in this Research:

 Implementing Flexibility: Moving beyond technical design to include managerial

flexibility, such as changing processes, adjusting resources, or altering the sequence of
construction.
 Inter-Organizational Relationships: Studying how contracts, alliance agreements, and
shared goals (e.g., gain-share/pain-share) promote collaboration among diverse
stakeholders.
 Integrating Technology: Leveraging BIM (Building Information Modelling) and other
digital tools to support rapid adjustments and improve visual collaboration.

By studying these factors, researchers and practitioners can create a more resilient
transportation infrastructure capable of meeting future needs.

The delimitation of scope for studying enhanced flexibility and collaboration in

highway construction through Agile management defines the boundaries of the
research, focusing on specific phases, methodologies, and environmental constraints.

1. Delimitations (What is Included)

Methodological Focus: The study focuses on integrating Agile practices (e.g.,
Scrum, Kanban, daily stand-ups, retrospectives) with traditional, linear (Waterfall)
construction approaches, often termed "Hybrid Management".
Core Areas: Research is delimited to improving project flexibility (adapting to scope
changes) and collaboration (improving communication between stakeholders,
contractors, and clients).
Project Phase: While Agile is applicable throughout, studies often focus heavily on
the pre-construction phase (planning, design, and initial coordination), where
flexibility is most achievable, or specific iterative phases of construction.
Key Goals: The investigation aims at reducing time delays, enhancing responsiveness
to unforeseen site conditions, and improving stakeholder satisfaction.
Predictability: The study accepts that increased flexibility leads to lower
predictability in initial, detailed long-term, and static scheduling.
Industry Type: Specifically targeted at infrastructure/civil projects (highways, roads,
bridges) rather than software development.
Project Complexity: The scope is often limited to projects with high levels of
uncertainty, frequent design changes, or complex stakeholder environments.
Cultural Shift: The study includes the need for a cultural shift towards self-
organizing teams and increased collaboration, recognizing that purely technical Agile
tools are insufficient.

2. Limitations and Exclusions (What is Excluded)

Physical Constraints: Agile cannot change the physical, sequential nature of certain
construction tasks (e.g., concrete curing time), meaning its application is limited to
scheduling and coordination, not the physical science of construction.
Regulatory/Contractual Limits: The research acknowledges, but often cannot
overcome, rigid, legally binding, fixed-price contracts that inhibit flexibility.
Full Agile Adoption: The study typically excludes the adoption of pure Scrum/Agile
(as used in software) in favor of hybrid models, recognizing that total flexibility is not
feasible in infrastructure.
Geographical limitation: include Addis Ababa

Chapter 3: Material and Methods

A Systematic Literature Review (SLR) is a rigorous, transparent, and reproducible

method for identifying, evaluating, and synthesizing all relevant, high-quality
literature on a specific research topic. It uses pre-defined criteria to minimize bias,,
often following a structure of planning, conducting, and reporting to map research
gaps and consolidate existing knowledge.

Core Steps in SLR Methodology

Defining Research Questions (RQs): Formulate specific, answerable questions that
the review aims to address.
Developing the Protocol: Create a plan outlining the research strategy,
inclusion/exclusion criteria, and assessment methods.
Literature Search: Conduct a comprehensive search across databases (e.g., Scopus,
Web of Science, IEEE Xplore) using predefined keywords.
Screening and Selection: Apply inclusion/exclusion criteria to titles, abstracts, and full
texts to select relevant studies.
Quality Assessment: Evaluate the rigor and validity of the selected studies.
Data Extraction: Systematically extract data (e.g., author, methodology, findings)
from the selected papers.
Synthesis and Analysis: Synthesize the collected data to answer the research
questions, often using thematic analysis.
Reporting: Document the findings in a structured, transparent, and reproducible
report.
Key Components
Search Strategy: Defines the databases, time range, and keywords (including
Boolean operators) used to locate studies.
Inclusion/Exclusion Criteria: Strict rules determining which studies are included
or rejected to reduce selection bias.
PRISMA Framework: Often used as a standard, structured framework for
conducting and reporting the review.
This video provides an introduction to the key characteristics of a systematic
literature review: