<?xml version="1.0"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.1 20151215//EN" "http://jats.nlm.nih.gov/archiving/1.1/JATS-archivearticle1.dtd">
<article>
  <front>
    <journal-meta><journal-id journal-id-type="other">Journal</journal-id>
      <journal-title-group>
        <journal-title>Austin Baraza Omonyo, IJSRM</journal-title>
      </journal-title-group>
    <publisher><publisher-name>Academic Publisher</publisher-name></publisher></journal-meta>
    <article-meta>
      <article-id pub-id-type="doi">10.18535/ijsrm/v6i3.em05</article-id>
      <title-group>
        <article-title>Influence of Ambiguity on Success of Public Infrastructural Megaprojects in Kenya</article-title>
      </title-group>
      <contrib-group content-type="author">
        <contrib contrib-type="author">
          <name><given-names>Austin Baraza Omonyo</given-names></name>
          <email>baraza@cfpm.co.ke</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <name><given-names>Roselyn Gakure</given-names></name>
          <email>rwgakure@gmail.com</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <name><given-names>Romanus Odhiambo</given-names></name>
          <email>romanusemod@yahoo.com</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        
        
        
      </contrib-group>
      <aff id="aff0">
          
          <institution content-type="orgname">Centre for Finance &amp; Project ManagementTM College House</institution>
          ,
          <addr-line>2nd Floor, Koinange Street, Nairobi</addr-line>
          ,
          <country country="KE">Kenya</country>
        </aff><aff id="aff1">
          
          <institution content-type="orgname">Jomo Kenyatta University of Agriculture &amp; Technology Office of The Deputy Vice Chancellor</institution>
          ,
          <addr-line>Academics, Main Campus, Thika</addr-line>
          ,
          <country country="KE">Kenya</country>
        </aff><aff id="aff2">
          
          <institution content-type="orgname">Jomo Kenyatta University of Agriculture and Technology School of Entrepreneurship &amp; Management</institution>
          ,
          <addr-line>Main Campus, Thika</addr-line>
          ,
          <country country="KE">Kenya</country>
        </aff><pub-date>
        <year>2018</year>
      </pub-date>
      <volume>06</volume>
      <issue>03</issue>
      <fpage>7</fpage>
      <lpage>22</lpage>
      <abstract>
        <p>The objective of this study was to investigate the influence of ambiguity on success of public infrastructural megaprojects in Kenya. The need for this study arose from the thesis that ambiguity is a key cause of complexity that results in infrastructural megaprojects being delivered over budget, behind schedule, with benefit shortfalls, over and over again. The study was designed as multiple-method research based on virtual constructionist ontology recognizing that complexity is the mid-point between order and disorder. A crosssectional census survey of completed public infrastructural megaprojects was conducted using two interlinked questionnaires. Quantitative data was analyzed using descriptive and inferential statistics while qualitative data was analyzed using expert judgment, scenario mapping and retrospective sense-making. The projects surveyed majorly utilized fixed price contracts with the outcome of increased delivery within budget than within schedule. The results showed that ambiguity had significant negative influence on process and overall success of public infrastructural megaprojects but had no significant relationship with product and organizational success. Projects in which the client assumed responsibility for cost and schedule risk had higher chances of meeting both cost and schedule objectives. In order to manage the negative effects of ambiguity, we recommend a new perspective to contract design of public infrastructural megaprojects based on complexity science, blending both outcome and behavior-based contracts. Such contracts should ensure that, in the face of ambiguity, the contractors are able to act in the best interest of their clients and that the clients have access to quality Project Management Information Systems.</p>
      </abstract>
      <kwd-group>
        <kwd>Ambiguity</kwd>
        <kwd>megaproject</kwd>
        <kwd>complexity</kwd>
        <kwd>project success</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec>
              <title>Introduction</title>
        <p>Public infrastructural megaprojects are large-scale, complex ventures that cost billions of money, take many years to develop and build, involve multiple public and private stakeholders, are transformational, and impact millions of people (<xref ref-type="bibr" id="ID5f3ab043-7d16-4571-9aa3-e88d544b071b">Flyvbjerg, 2014</xref>). These projects are generally &#x201C;greenfield&#x201D; in nature as they often create new assets and utilize a variety of delivery models depending on their inherent complexity. They are often trait-makingsince they are designed to change the structure of society. This is in contrast with smaller and more conventional projects that are trait taking, often fitting into pre-existing structures without modification (<xref ref-type="bibr" id="ID04a755e1-7e09-4eea-a83f-1349632b6ff5">Hirschman, l995</xref>). Brady and Davies (<xref rid="R12" ref-type="bibr" id="ID81462b22-4f67-4c5e-a619-da158290d578">2014</xref>) note that megaprojects are among the most complex category of project. </p>
        <p>		In Kenya, the growth in the use of infrastructural megaprojects to deliver goods and services has been phenomenal over the past few years and there appears to be no end in sight for their use. This is despite the fact that megaprojects are always delivered over budget, with schedule delays, with benefit shortfalls, over and over again (<xref ref-type="bibr" id="ID69af4f6a-00a3-4ea8-a1d6-44afd8bb3f22">Flyvbjerg, 2014</xref>). The complexity inherent in the megaproject environment is often cited as the main cause of this poor performance (Cooke-Davies, Crawford &amp; Stephens, 2011). Without a coherent research agenda to understand both its causes and navigation strategies, complexity continues to result in problems, waste and socio-economic failure (<xref rid="R13" ref-type="bibr" id="ID43cc83fc-3373-4622-b60c-0f072f075081">Remington &amp; Zolin, 2011</xref>). As a step in taking this agenda forward, and building on the work of earlier researchers such as Maylor, Vidgen and Carver (<xref rid="R19" ref-type="bibr" id="IDd63f7f65-40b5-4c07-b3c5-e8d3bb71ab78">2008</xref>), the Project Management Institute (PMI) published a Practice Guide on Navigating Complexity in 2014. This Guide describes the causes of complexity in three categories namely; human behavior, ambiguity and system behavior. </p>
        <p>	Whereas a number of studies have been conducted to explain the centrality of complexity in determining success of infrastructural megaprojects, most of these studies conclude that human behavior is the main cause of poor performance in these projects (<xref ref-type="bibr" id="ID82e8d786-38e3-4431-a0cb-f0abc0fc4798">Collyer, 2016</xref>; <xref ref-type="bibr" id="ID9af96345-1a06-4250-bee6-feff0ac547ed">Olaniran, Love, Edwards, Olatunji &amp; Mathews, 2015</xref>; <xref ref-type="bibr" id="IDc34c458a-8b56-462c-9239-a0d679f862dc">Meyer, 2014</xref>; <xref ref-type="bibr" id="IDe980cacd-eefa-4be5-8010-a546e8a1d0cf">Shore, 2008</xref>; <xref ref-type="bibr" id="IDa22edb8b-3990-483a-af36-4cfe8db2fe47">Flyvbjerg, Holm &amp; Buhl, 2004</xref>; <xref ref-type="bibr" id="ID7551634f-160d-4d22-91fb-bd88f404d397">Lovallo &amp; Kahneman, 2003</xref>; <xref ref-type="bibr" id="IDb5fc14c2-d731-4f5d-9aa7-73d7fa42dcf6">Bruzelius, Flyvbjerg &amp; Rothengatter, 2002</xref>; <xref ref-type="bibr" id="IDa6f567cf-2d75-4f42-8676-ae9fb9acccf0">Mackie &amp; Preston, 1998</xref>; <xref ref-type="bibr" id="IDf2bd7c0f-a4ba-475f-ba80-203fabe4bbe2">Kahneman &amp; Tversky, 1979</xref>). This is despite existence of the thesis that there is a significant positive relationship between ambiguity and both customer and organizational outcomes (<xref ref-type="bibr" id="ID2af241d7-e1d3-4bf9-a005-84ac9273b134">Hargen &amp; Park, 2013</xref>). 	Ambiguity arises from unclear or misleading events, cause and effect confusion, emergent issues or situations open to more than one interpretation in programs and projects (<xref ref-type="bibr" id="ID4aa60c05-28a6-4b76-957a-c0ef529d2151">PMI, 2014</xref>). As a result of this ambiguity, the whole is always greater than the sum of the parts leading to uncertainty in performance of the project metrics. As Brady and Davis (<xref rid="R12" ref-type="bibr" id="ID5f0d8283-061c-4859-9219-daeb7037b645">2014</xref>) demonstrate, handling this inherent ambiguity to ensure stability can indeed enhance success of megaprojects. Once stability is achieved, the project schedule is able to absorb emerging disruption arising from dependencies and connections among its component parts thus ensuring that the dynamics of the system as a whole are kept under control. It is argued that achieving stability is as important as the more common measures of project performance (<xref rid="R19" ref-type="bibr" id="IDfa24e4f5-3a31-465c-8013-252e27cc6676">Swartz, 2008</xref>). It is on the basis of this proposition that this multiple-method research based on virtual constructionist ontology was designed. The study surveyed managers, team members, sponsors and key stakeholders of completed public infrastructural megaprojects to investigate the influence of ambiguity on success of public infrastructural megaprojects with a view to making recommendations on how to manage its effects. Ambiguity was operationalized through its components namely; context, emergence and uncertainty (<xref ref-type="bibr" id="ID34645b16-4501-4b3c-99be-b83c383d28d9">PMI, 2014</xref>). The results of the study showed that each of these components of ambiguity were related to success and that the overall ambiguity had significant negative influence on success of public infrastructural megaprojects. 	 	The remainder of this article is organized as follows: the relevant theoretical and empirical literature are reviewed leading to the formulation of the study hypothesis and a presentation of the conceptual framework. The next section describes the methodology followed by the study and this is followed by a section on results of the study and a discussion of those results. The last section presents the conclusions and references.</p>
      </sec>
      <sec>
        <title>Theoretical and Conceptual Framework</title>
        <sec>
          <title>2.1 Theoretical Framework</title>
          <p>This study was operationalized through two theories namely; Complex Adaptive Systems and Project Success theories. Each of these theories is briefly discusses below:</p>
          <sec>
            <title>2.1.1 Complex Adaptive Systems Theory</title>
            <p>Complex Adaptive Systems (CAS) theory also referred to as Complexity theory, states that critically interacting components self-organize to form potentially evolving structures exhibiting a hierarchy of emergent system properties (<xref ref-type="bibr" id="ID00e4fc52-2306-4674-a007-e6692d2fc1ff">Lucas, 2009</xref>). The rise of CAS as a school of thought is usually attributed to the mid-1980&#x2019;s formation of the Santa Fe Institute, a New Mexico think tank formed in part by the former members of the nearby Los Alamos National Laboratory. The scientists here claimed that through the study of complexity theory, one can see both laws of chaos and that of order; through which an explanation for how any collection of components will organize itself can be generated (<xref rid="R21" ref-type="bibr" id="ID87603cd4-5f44-4555-984a-1dda8184636a">Waldrop, 1992</xref>). </p>
            <p>	Complexity theory is concerned with the study of how order, structure, pattern, and novelty arise from extremely complicated, apparently chaotic systems and conversely, how complex behavior and structure emerges from simple underlying rules. The theory attempts to discover how the many disparate elements of a system work with each other to shape the system and its outcomes, as well as how each component changes over time (<xref ref-type="bibr" id="ID68318365-ae32-4944-8df1-c4c4caead4ed">PMI, 2014</xref>). Insights from the study of complexity in the life sciences suggests that there is a natural tendency for all organisms (including human kind and social organisms such as project teams) to evolve complex responses to challenges that they encounter in their environment.</p>
            <p>	Another important concept in complexity theory is that there is no master controller of any system. Rather, coherent system behavior is generated by the competition and cooperation between actors that is always present. The components of a system have different levels of organization-made up of divisions, which contain different departments, which in turn comprise different workers. But the important differentiation from this organization is that complex adaptive systems are constantly revising and rearranging their building blocks as they gain experience (<xref ref-type="bibr" id="ID05429060-cf37-4931-a136-61d4a346c792">Caldart &amp; Joan, 2004</xref>). 	 	 	The CAS theory is reinforced by the Chaos theory which studies the behavior of <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://en.wikipedia.org/wiki/Dynamical_system" ext-link-type="uri" xlink:type="simple">dynamical systems</ext-link> that are highly sensitive to initial conditions. The theory is attributed to Edward Lorenz who while using a computer to simulate weather systems in 1960 at Massachusetts Institute of Technology, discovered one important aspect of how non-linearity affects the weather-the principle of sensitive dependence on initial conditions (<xref ref-type="bibr" id="IDb94cd534-ebb7-411a-adb0-6e9897ceae82">Lorenz, 1963</xref>). Lorenz&#x2019;s discovery of how minute changes can have major and unpredictable consequences in nonlinear systems became known as the &#x201C;butterfly effect&#x201D;. According to this theory, small differences in initial conditions yield widely diverging outcomes for such dynamical systems, rendering long-term prediction impossible in general (<xref ref-type="bibr" id="ID5cc8f18a-43ae-415f-ba0a-e44d2af7dbab">Kellert, 1993</xref>). Thus, a small initial schedule delay in delivering one component of a megaproject can lead to more than proportionate delay in the entire project. </p>
            <p>	The CAS and Chaos theory are helpful in defining the main aspects of ambiguity namely; context, emergence and uncertainty. Emergence is an unanticipated change, spontaneous or gradual, that occurs within the context of a program or project. Uncertainty is a state of imperfect knowledge about future occurrences on the project while context is the environmental set-up within which the project is implemented.</p>
          </sec>
          <sec>
            <title>2.1.2 Project Success Theory</title>
            <p>There have been various attempts over the history of project management to define suitable criteria against which to anchor and measure project success (<xref ref-type="bibr" id="IDb5ed4960-8a87-4172-bfad-9e0f49aa6ed1">McLeod, Doolin &amp; MacDonell, 2012</xref>). The most recognized of these measures is the long established and widely used &#x201C;iron triangle&#x201D; of time, cost and quality (<xref ref-type="bibr" id="IDd7edc472-5ca9-4d8d-96df-369d2b37cd64">Atkinson, 1999</xref>; Cooke-Davies, 2002; <xref ref-type="bibr" id="ID07aaa560-64da-4220-b5a3-cf93abfc974e">de Wit, 1988</xref>, <xref ref-type="bibr" id="IDa7a0d91d-eba3-4afa-9af2-b5f1f3f41242">Ika, 2009</xref>; Jugdev, Thomas, &amp; Delisle, 2001). However, the &#x201C;iron triangle&#x201D; dimensions are inherently limited in scope (<xref ref-type="bibr" id="ID0c671483-7bee-4382-b3d3-e46ee93e53f8">Atkinson, 1999</xref>; Ika, 2009; <xref rid="R22" ref-type="bibr" id="ID2b6907e7-fec2-47cd-93f5-c47908279265">Wateridge, 1998</xref>). A project that satisfies these criteria may still be considered a failure; conversely a project that does not satisfy them may be considered successful (<xref ref-type="bibr" id="IDff056681-4cb7-4ebd-afa7-11641c8d925f">Baccarini, 1999</xref>; <xref ref-type="bibr" id="IDb04146dc-f926-4402-8e40-b8374a4ba357">de Wit, 1988, Ika, 2009</xref>). The &#x201C;iron triangle&#x201D; only focuses on the project management process and does not incorporate the views and objectives of all stakeholders (<xref ref-type="bibr" id="ID84a76720-ae4d-4709-a750-90a3ca6841ea">Atkinson, 1999</xref>; <xref ref-type="bibr" id="ID8eb7dba9-b60b-4330-a230-158b024cd40e">Baccarini, 1999</xref>; <xref ref-type="bibr" id="IDd6402d5f-30f2-463f-80c8-bf13f3758683">Bannerman, 2008</xref>; <xref ref-type="bibr" id="IDee702471-eae9-4a06-b672-13671e1e06bc">de Wit, 1988</xref>; <xref ref-type="bibr" id="ID451db938-cdc4-4ef5-afa1-7b4a7a62b142">Jugdev &amp; Muller, 2005</xref>; <xref rid="R22" ref-type="bibr" id="ID62ccbb17-342f-47b2-ba14-197135655f7f">Wateridge, 1998</xref>).</p>
            <p>	Researchers have progressively widened the scope and constituency of what is meant by project success, recognizing that project success is more than project management success and that it needs to be measured against overall objectives of the project thus reflecting a distinction between the success of a project&#x2019;s process and that of its product (<xref ref-type="bibr" id="ID3c13eba5-7167-4fd4-9ac0-6e3d28bce18c">Baccarini, 1999</xref>; <xref ref-type="bibr" id="ID70724e68-1c67-4b0e-a37c-06e132406fd5">Markus &amp; Mao, 2004</xref>; <xref rid="R22" ref-type="bibr" id="IDdd70706e-6983-4b07-afab-894ccb432376">Wateridge, 1998</xref>). Product success involves such criteria as product use, client satisfaction and client benefits (<xref ref-type="bibr" id="ID39bf64e1-903f-4865-823b-ad2a8783caf0">McLeod et al., 2012</xref>). </p>
            <p>	Researchers are also increasingly advocating for project success criteria that incorporates achievement of broader set of organizational objectives involving benefits to the wider stakeholder base (see Shenhar, Dvir, &amp; Levy, 1997; Shenhar, Dvir, Levy &amp; Maltz, 2001; Shenhar &amp; Dvir, 2007; Hoegl &amp; Gemuenden, 2001). This is plausible given that projects are a means of delivering the organization&#x2019;s strategic objectives. Proponents of this school of thought advocate for inclusion of success criteria such as business and strategic benefits.  It is this broader context of success that appeals to infrastructural megaprojects. </p>
          </sec>
        
        <sec>
          <title>2.2 Conceptual Framework</title>
          <p>Even though there are no studies that have directly assessed the influence of ambiguity on success of public infrastructural megaprojects, studies have been done that show the importance and usefulness of ambiguity in explaining project outcomes. For instance, in a study on managing structural and dynamic complexity, Brady and Davis (<xref rid="R12" ref-type="bibr" id="IDbc0a7f7f-a506-4de3-aade-fc7f241dc72a">2014</xref>) used a comparative study of two successful megaprojects to illustrate the importance of handling ambiguity in order to deliver such projects successfully. The study underscored the need for: integrated project teams expected to come up with innovative solutions in the face of uncertainty and emergence; prototyping and testing new technology offsite prior to introduction on site; and an integrated change control system to deal with progressive elaboration in scope and its consequences.</p>
          <p>		To determine the relationship between ambiguity acceptance and project outcomes, Hargen and Park (<xref ref-type="bibr" id="ID02ce0b17-d13d-4e53-a2b5-4f7eba718ff1">2013</xref>) conducted an online survey of 2 Fortune 100 and 2 Fortune 500 companies, all of which had implemented Six Sigma and used teams as the core deployment tool for improvement projects. Using a combination of Principal Component Analysis, Correlation Analysis and Regression Analysis, the study established a significant positive relationship between ambiguity and both customer and organizational outcomes.</p>
          <p>		In a study of the antecedents and impacts of ambidexterity in project teams, Liu and Leitner (<xref ref-type="bibr" id="IDaff59fb7-87fb-4962-8a9f-9d49c2946778">2012</xref>) used an in-depth case study of a complex infrastructure project facing unique challenges and tight budget and schedule to demonstrate the need for simultaneous pursuit of innovation and efficiency in complex engineering projects. They argue that both exploration and exploitation are likely to be needed for complex engineering projects to succeed. The study found that ambidexterity at the project team level is a significant contributor to project performance; the effects of temporal separation and project context on project performance are mediated by the project team's degree of ambidexterity. A key contribution of this study is the characterization of contextual ambidexterity as that which utilizes behavioral and social means of integrating exploration and exploitation. Contextual ambidexterity is achieved through empowering individuals to decide on the time spent on exploration activities or exploitation activities. To achieve contextual ambidexterity, alignment and adaptability of organizational activities and capabilities must be ensured so as to meet changing demands (<xref ref-type="bibr" id="IDc2a84ee6-3f73-41f6-8106-24924f6f2770">Birkinshaw, 2004</xref>). </p>
          <p>	In a study to investigate the importance and usefulness of stability (i.e., ability of schedules to absorb emerging disruption) to project outcomes, Swartz (<xref rid="R19" ref-type="bibr" id="IDf40676a1-d68b-49be-8e8b-52a269666bf0">2008</xref>) conducted a survey with managers involved in aviation systems development. The study established that stability was perceived to be as important as the more common measures of project performance (time, cost, quality) and that perceptions differed depending on program size, scope (both could be used to explain complexity) and stage of completion and between managers based on their levels of experience and training. </p>
          <p>	In a study to examine the influence of product requirements ambiguity on new product development task structures, Duimering, Ran, Derbentseva and Poile (<xref ref-type="bibr" id="ID424cd890-8393-4157-bb90-8952ddfeb625">2006</xref>) used interview data from new product development project managers in a large telecom firm to show that knowledge of how the task structures evolve (emergence) can lead to improved strategies for managing projects with ambiguous requirements. These strategies include decomposition of project tasks to reduce interdependence among tasks and flexible adaptation of the task structures. The study also underscores the role of communication, coordination, knowledge and problem solving in resolving ambiguity. </p>
          <p>	From the foregoing, it is clear that ambiguity plays a major role in success of projects. The direction of the relationship of ambiguity and success is not apparent as there are instances when it leads to negative consequences and others when it leads to positive consequences, depending on how it is handled. It is on this basis that this study sought to test a non-directional hypothesis that:</p>
          <p><bold>H</bold>A<italic>: Ambiguity has significant influence on success of public infrastructural megaprojects.</italic></p>
          <p>The relationship is shown below:</p>
          <p><bold>Ambiguity </bold> ContextEmergenceUncertainty<bold>Megaproject Success  </bold>Process Product  Organizational </p>
        </sec>
      </sec>
    </sec>
    <sec>
      <title>Ha:+/-</title>
    </sec>
    <sec>
      <title>Figure 1: Research Model</title>
      <sec>
        <title>Methodology</title>
        <sec>
          <title>3.1 Research Design</title>
          <p>This study was operationalized through exploratory, descriptive and explanatory research goals based on Neuman (<xref ref-type="bibr" id="ID1151ced7-ebf0-4525-85b7-ecd96a1b1e1f">2003</xref>) classification of research goals. To achieve these goals, a post-positivist philosophy emphasizing virtual constructionist ontology (<xref ref-type="bibr" id="IDf0ea5148-3fdd-4f69-bc37-32c3c10d75a4">Gauthier &amp; Ika, 2012</xref>) was assumed. The choice of this philosophical perspective was guided by the social world of complex megaprojects. In this social world, megaproject management is neither a practice nor a tool (as is the case with projects implemented in the modern social world) but a rallying rhetoric in a context of power play, domination and control (<xref ref-type="bibr" id="ID76c156c6-6563-4d29-a67f-ac5bdbabba22">Gauthier &amp; Ika, 2012</xref>). </p>
          <p>	The study was designed to be mixed-method research combining both quantitative and qualitative strategies (<xref ref-type="bibr" id="ID4b6e4d0b-6fb9-492d-a831-d2d3d5d04343">Burch &amp; Carolyn, 2016</xref>). The mixed-method research provides an epistemological paradigm that occupies the conceptual space between positivism and interpretivism (<xref ref-type="bibr" id="ID295627d1-e5e1-402f-bc95-cb1e260fa5f8">Tashakkori &amp; Creswell, 2007</xref>), the main epistemologies on which the virtual constructionist ontology thrives. To generate data for this study, a cross-sectional survey design was used. This design entails the collection of data (predominantly by questionnaire or structured interview) on usually quite a lot more than one case and at a single point in time in order to collect a body of quantitative or quantifiable data in connection with two or more variables, which are then examined to detect patterns of association (<xref ref-type="bibr" id="IDb166ec87-dd3b-4057-9ddc-41d2052a5d50">Bryman &amp; Bell, 2007</xref>). </p>
        </sec>
        <sec>
          <title>3.2 Target Population</title>
          <p>This study had as its primary population public sector infrastructural megaprojects implemented by the government of Kenya since 2005. Given the continual reorganizations within government and the several projects implemented by the government, it was unlikely that project records and managers for earlier projects could be traced with ease. Following Flyvbjerg (<xref rid="R12" ref-type="bibr" id="IDcf27da4c-ed2d-49bb-ac6b-45b81d5e9c01">2014</xref>), the minimum budget for megaprojects included in this study was approximately Ksh. 1 billion. Managers, team members, sponsors and key stakeholders of these projects constituted the population of respondents from whom data was collected. </p>
          <p>	The rationale for selecting infrastructure among other foundations of national transformation was based on its huge actual and projected expenditure in comparison to other sectors. Specifically, in the Government of Kenya (<xref ref-type="bibr" id="IDdddb871d-29db-4ec7-9745-c2e4f3fa4e06">2013</xref>) Second Medium Term Plan, infrastructure was allocated over Ksh. 7.5 trillion with the second highest allocation  of Ksh. 2.5 trillion going to the Information, Communication and Technology sector. </p>
        </sec>
        <sec>
          <title>3.3 Sampling Frame and Sample</title>
          <p>The sampling frame of this study comprised a listing of completed public sector infrastructural megaprojects implemented in Kenya since 2005 with a minimum budget of approximately Ksh. 1 billion. The list of these projects was obtained from the Vision 2030 Secretariat and counterchecked with key informants from government parastatals. A total of 31 such projects was identified. Given the number of completed infrastructural megaprojects for the period under study as described by the sample frame, a census survey was found to be appropriate. Generally, when a sample frame is known, it can also be construed to mean that the population is known. In this case, collecting data on each member of the population becomes possible. </p>
        </sec>
        <sec>
          <title>3.4 Instruments</title>
          <p>The fieldwork for this study utilized two interlinked questionnaires namely, the Complexity Assessment Questionnaire, (CAQ) and the Project Success Questionnaire (PSQ). The CAQ was constructed based on the Practice Standard for Navigating Complexity (<xref ref-type="bibr" id="ID4f39f2c9-96ee-446e-bf89-66bdb13d546a">PMI, 2014</xref>) while the PSQ was developed based on Shenhar and Dvir (<xref ref-type="bibr" id="ID2b1e964c-c831-4aad-885b-4c116533c745">2004</xref>) and McLeod et al. (<xref ref-type="bibr" id="ID3310b262-fb27-4a7e-8078-233dff5abeee">2012</xref>). Questionnaire survey is hailed to be an efficient data collection mechanism when the researcher knows exactly what is required and how to measure the variables of interest (<xref ref-type="bibr" id="ID388624d9-e1ba-46c8-a08d-7e373eb3307e">Neuman, 2003</xref>). Both questionnaires utilized a mixture of Likert scale, open ended questions, checklists and probing questions including those soliciting for specific project metrics. 	 	 	Ambiguity was measured on a 19-item scale comprising three constructs namely; context, emergence and uncertainty. The PSQ scale comprised 18 items blending open and closed ended questions on one part and Likert-type questions on the other part. This scale measured success along three constructs namely; process, product and organizational success. The first part involving closed and open ended questions was meant to assess process success while the Likert type questions assessed product and organizational success on a scale of 1 (strongly agree), 2 (agree), 3 (<xref ref-type="bibr" id="ID0c0149f0-f86a-400a-88e2-62a7b63e8b2d">Neither agree nor disagree</xref>), 4 (disagree) and 5 (strongly disagree). </p>
        </sec>
        <sec>
          <title>3.5 Pilot Test and Reliability </title>
          <p>The pilot test involved validating data collection instruments and testing the feasibility of the data collection schedule. Through this study, the reliability and dimensionality of the measurement scales were tested to ensure that the items in the scales actually and reliably measured the intended variables. A total of four public infrastructural megaprojects and 16 respondents were surveyed as part of the pilot study. This was well above the &#x201C;10% of the sample projected for the larger parent study&#x201D; rule (<xref ref-type="bibr" id="ID5a09fba1-10a0-44ce-9b5e-93695416f321">Connelly, 2008</xref>). Reliability is concerned with the question of whether the results of a study are repeatable. It is concerned with whether or not the measures that are devised for concepts are consistent (<xref ref-type="bibr" id="ID2a30110f-2412-417b-af0b-080cb2259c96">Bryman &amp; Bell, 2007</xref>). Cronbach&#x2019;s (<xref ref-type="bibr" id="ID69d846b9-aaf7-4783-b49c-dfac2872d481">1951</xref>) coefficient alpha (&#x3B1;) is commonly used to measure the reliability of the scales for Likert-scaled sub-items (<xref rid="R17" ref-type="bibr" id="IDf2acc10d-4451-4865-83f4-5c4d3237bfe6">Spector, 1992</xref>). This is because the underlying assumption of the Likert scale is that it represents an underlying continuous latent scale, although the observations are ordinal (<xref ref-type="bibr" id="IDfb38d33b-0748-40b2-88f6-e709659be4f1">Likert, 1931</xref>), and a high score of Cronbach&#x2019;s coefficient alpha means high reliability, stability and accuracy (<xref ref-type="bibr" id="ID46341d8c-7825-420d-b9ef-8bce07f132d3">Papadopoulos, Ojiako, Chipulu &amp; Lee, 2012</xref>). If the sub-items have high agreement and are highly correlated then &#x3B1; will be close to 1. Hair, Babin, Money and Samouel (<xref ref-type="bibr" id="IDb942ee90-e61a-4502-9d62-c411bf5d7b6c">2003</xref>) asserted that an alpha coefficient between 0.8 and 0.9 shows very good strength of association. When &#x3B1; is &#x2265; 0.7, the scale is generally reliable (<xref ref-type="bibr" id="IDe37eee04-a603-4487-858d-b4d468be859c">Nunnally, 1978</xref>). Following this rule, both instruments were found to be reliable with the Ambiguity scale recording a Cronbach&#x2019;s alpha of 0.837 while the overall internal reliability of the success scale was 0.889.</p>
        </sec>
        <sec>
          <title>3.6 Data Analysis </title>
          <p>To aid data processing and analysis, this study utilized the Statistical Package for Social Sciences (SPSS) version 20, Microsoft Access 2010 and Microsoft Excel 2010. The original database was created in MS Access (due to its versatility) and then transferred to SPSS for ease of analysis. MS Excel was used to complement SPSS in navigating through data sets during analysis. The SPSS software was chosen for its analytical superiority, availability and ability to handle large amounts of data. </p>
          <p>	Descriptive statistics for quantitative data analysis were derived using frequencies and percentages, measures of central tendency (mainly the mean), measures of dispersion (mainly standard deviation coefficient of variation, skewness and kurtosis) and Earned Value measures (mainly Cost Performance Index, CPI and Schedule Performance Index, SPI). Inferential statistics were derived using regression and correlation analysis. The overall model for this study assumed the form of a simple linear regression model and was specified as:</p>
          <p><mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" overflow="scroll"><mml:mover><mml:mrow><mml:msub><mml:mrow><mml:maction actiontype="lit"><mml:mtext>PS</mml:mtext></mml:maction></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mrow><mml:mo>&#x2212;</mml:mo></mml:mrow></mml:mover><mml:mo>=</mml:mo><mml:msub><mml:mrow><mml:mi>&#x3B2;</mml:mi></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mrow><mml:mi>&#x3B2;</mml:mi></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msub><mml:msub><mml:mrow><mml:maction actiontype="lit"><mml:mtext>AM</mml:mtext></mml:maction></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:mi>&#x3BC;</mml:mi></mml:math> (1) </p>
          <p>where <mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" overflow="scroll"><mml:msub><mml:mrow><mml:mi>&#x3BC;</mml:mi></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:math>the stochastic term and &#x3B2;2 is the slope of the regression-change in the coefficient of project success as a result of a unit change in ambiguity score. <italic>&#x3B2;</italic>1 is the intercept-the coefficient of project success when there is no ambiguity.	The regression coefficients were extracted using Ordinary Least Squares (OLS) method and tested for significance at the 95 percent confidence level using two-tailed <italic>t</italic>-test based on the hypothesis that: <mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" overflow="scroll"><mml:msub><mml:mrow><mml:mi>H</mml:mi></mml:mrow><mml:mrow><mml:mn>0</mml:mn></mml:mrow></mml:msub><mml:mo>:</mml:mo><mml:msub><mml:mrow><mml:mi>b</mml:mi></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mn>0</mml:mn></mml:math>;  <mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" overflow="scroll"><mml:msub><mml:mrow><mml:mi>H</mml:mi></mml:mrow><mml:mrow><mml:mi>A</mml:mi></mml:mrow></mml:msub><mml:mo>:</mml:mo><mml:msub><mml:mrow><mml:mi>b</mml:mi></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2260;</mml:mo><mml:mn>0</mml:mn></mml:math>; where <mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" overflow="scroll"><mml:msub><mml:mrow><mml:mi>b</mml:mi></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:math>are the values of individual betas in the estimated regression equation. The significance of the overall model was tested using multiple coefficient of determination (<italic>R</italic>2) and the <italic>F-test</italic>. Qualitative data was analyzed using a combination of expert judgment, scenario mapping, retrospective sense-making and critical thinking</p>
        </sec>
      </sec>
      <sec>
        <title>Research Findings and Discussion</title>
        <sec>
          <title>4.1 Introduction</title>
          <p>A total of 27 completed infrastructural megaprojects were studied as part of this research. This represented a return and response rate of 87.1%. Of these projects, 2 (7.4%) were from Kenya Ports Authority, 2 (7.4%) were from Kenya Pipeline Company, 6 (22.2%) were from Kenya Airports Authority, 3 (11.1%) were from Kenya Power and Lighting Company, 1 (3.7%) was from Kenya Electricity Generating Company, 5 (18.5%) were from Kenya Urban Roads Authority, 1 (3.7%) was from Kenya Civil Aviation Authority, 1 (3.7%) was from Geothermal Development Company, with the remaining 6 (22.2%) coming from Kenya National Highways Authority.</p>
          <p>	The projects surveyed had a budget at appraisal ranging from approximately Ksh. 1 Billion to Ksh. 327 Billion with 8 of these projects (29.6%) having a budget at appraisal of over Ksh. 10 Billion. The scheduled duration for these projects ranged from 4 months to 72 months with most projects having a scheduled duration of above 20 months. The project locations were spread across several counties in Kenya. All the projects were turnkey, involving a variation of Engineer-Procure-Construct (EPC) and Design-Build-Transfer (DBT) delivery arrangements.</p>
        </sec>
        <sec>
          <title>4.2 Findings</title>
          <sec>
            <title>4.2.1 Project Context</title>
            <p>Ambiguity due to project context was assessed using a checklist that contained several statements regarding various project contractual arrangements and risk handling. The respondents were required to choose all the statements in the checklist that applied to their individual projects. The results showed that of the 27 projects surveyed, 20 projects (74.1%) utilized Fixed Price (FP) Contracts with 9(45%) of these utilizing a Firm Fixed Price/Lump sum (FFP) contract and 11 projects (55%) utilizing Fixed Price with Economic Price Adjustment (FPEA) contract. One project (3.7%) utilized a Cost Plus Fixed/Percentage Fee (CPFF/PF)contract while 6 projects (22.2%) utilized some form of Cost Contracts that involved re-measurement and ad-measurement based on initial estimates and Bill of Quantities respectively. Table 1 presents the mean performance statistics of the megaprojects studied based on their contract types.</p>
            <p><bold>Table 1: </bold>Project Success by Contract Types</p>
            <table-wrap specific-use="rules" id="ID729405c2-77cb-4c34-8758-9858d2328a41" position="float" orientation="portrait">
              <label>	The results showed that with the exception of the 1 project that utilized a CPF/PF contract, the projects that utilized cost contracts involving re-/ad-measurement had the highest mean success score at 5</label>
              <caption>
                <p>11 points out of the possible 600 These projects also recorded the lowest relative variability (CV=01174) in the individual mean success scores Using the CV values as measures of riskiness in project success, projects using re-/ad-measurable contracts had less risk followed by those utilizing FP-EPA The projects utilizing FFP recorded the highest risk in mean success</p>
              </caption>
              <table>
                <tr>
                  <td rowspan="1" colspan="1">
                    <bold>Contract Type</bold>
                  </td>
                  <td rowspan="1" colspan="1">
                    <bold>No. of Projects</bold>
                  </td>
                  <td rowspan="1" colspan="1">
                    <bold>Mean Success </bold>
                  </td>
                  <td rowspan="1" colspan="1">
                    <bold>STDEV</bold>
                  </td>
                  <td rowspan="1" colspan="1">
                    <bold>CV</bold>
                  </td>
                </tr>
                <tr>
                  <td rowspan="1" colspan="1">FP-EPA</td>
                  <td rowspan="1" colspan="1">11</td>
                  <td rowspan="1" colspan="1">4.86</td>
                  <td rowspan="1" colspan="1">0.79</td>
                  <td rowspan="1" colspan="1">0.16</td>
                </tr>
                <tr>
                  <td rowspan="1" colspan="1">FFP</td>
                  <td rowspan="1" colspan="1">9</td>
                  <td rowspan="1" colspan="1">4.3</td>
                  <td rowspan="1" colspan="1">1.01</td>
                  <td rowspan="1" colspan="1">0.24</td>
                </tr>
                <tr>
                  <td rowspan="1" colspan="1">Remeasurable</td>
                  <td rowspan="1" colspan="1">6</td>
                  <td rowspan="1" colspan="1">5.11</td>
                  <td rowspan="1" colspan="1">0.60</td>
                  <td rowspan="1" colspan="1"> 0.13</td>
                </tr>
                <tr>
                  <td rowspan="1" colspan="1">CPF/PF</td>
                  <td rowspan="1" colspan="1">1</td>
                  <td rowspan="1" colspan="1">5.4</td>
                  <td rowspan="1" colspan="1">-</td>
                  <td rowspan="1" colspan="1">-</td>
                </tr>
              </table>
            </table-wrap>
            <p> 	Since contractual arrangements are usually a means of allocating cost and schedule risks, this study established that of the 11 megaprojects that utilized FPEA contracts, 6 (54.5%) recorded cost overrun while 8 (72.7%) experienced schedule slippage. Of the 9 projects that utilized FFP contracts, 4 (44.4%) experience cost overruns while 8 (88.9%) experienced schedule delay. Of the 6 projects that utilized re-/ad-measurable contracts, 4 (66.7%) were delivered over budget with 5 (83.3%) being delivered behind schedule. This study noted that for projects utilizing FFP contracts, project scope ended up being narrowed to fit into the budget. The CPF/PF contract project was delivered on budget but behind schedule. Table 2 summarizes this information.</p>
            <p><bold>Table 2:</bold> Project Efficiency by Contract Type</p>
            <table-wrap specific-use="rules" id="IDbc9ba519-7fba-4b75-b673-3ee3f2c8a479" position="float" orientation="portrait">
              <label>	Barring the results of the project utilizing CPF/PF, the results showed that projects utilizing FFP contracts recorded the highest cost performance (55</label>
              <caption>
                <p>6%) but also recorded the lowest schedule performance (889%) Projects that utilized FP-EPA contracts exhibited the second highest cost performance (455%) but also the third lowest schedule performance (after 833% from re-/ad-measurable contract projects)</p>
              </caption>
              <table>
                <tr>
                  <td rowspan="1" colspan="1">Contract Type</td>
                  <td rowspan="1" colspan="1">Percentage of Projects Delivered With:</td>
                </tr>
                <tr>
                  <td rowspan="1" colspan="1"/>
                  <td rowspan="1" colspan="1">
                    <mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" overflow="scroll">
                      <mml:maction actiontype="lit">
                        <mml:mtext>CPI</mml:mtext>
                      </mml:maction>
                      <mml:mo>&#x2265;</mml:mo>
                      <mml:mn>1</mml:mn>
                    </mml:math>
                  </td>
                  <td rowspan="1" colspan="1"><mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" overflow="scroll"><mml:maction actiontype="lit"><mml:mtext>CPI</mml:mtext></mml:maction></mml:math>&#x2C2;1</td>
                  <td rowspan="1" colspan="1">
                    <mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" overflow="scroll">
                      <mml:maction actiontype="lit">
                        <mml:mtext>SPI</mml:mtext>
                      </mml:maction>
                      <mml:mo>&#x2265;</mml:mo>
                      <mml:mn>1</mml:mn>
                    </mml:math>
                  </td>
                  <td rowspan="1" colspan="1"><mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" overflow="scroll"><mml:maction actiontype="lit"><mml:mtext>SPI</mml:mtext></mml:maction></mml:math>&#x2C2;1</td>
                </tr>
                <tr>
                  <td rowspan="1" colspan="1">FP-EPA</td>
                  <td rowspan="1" colspan="1">45.5%</td>
                  <td rowspan="1" colspan="1">54.5%</td>
                  <td rowspan="1" colspan="1">27.3%</td>
                  <td rowspan="1" colspan="1">72.7%</td>
                </tr>
                <tr>
                  <td rowspan="1" colspan="1">FFP</td>
                  <td rowspan="1" colspan="1">55.6%</td>
                  <td rowspan="1" colspan="1">44.4%</td>
                  <td rowspan="1" colspan="1">11.1%</td>
                  <td rowspan="1" colspan="1">88.9%</td>
                </tr>
                <tr>
                  <td rowspan="1" colspan="1">Remeasurable</td>
                  <td rowspan="1" colspan="1">33.3%</td>
                  <td rowspan="1" colspan="1">66.7%</td>
                  <td rowspan="1" colspan="1">16.7%</td>
                  <td rowspan="1" colspan="1">83.3%</td>
                </tr>
                <tr>
                  <td rowspan="1" colspan="1">CPF/PF</td>
                  <td rowspan="1" colspan="1">100%</td>
                  <td rowspan="1" colspan="1">-</td>
                  <td rowspan="1" colspan="1">-</td>
                  <td rowspan="1" colspan="1">100%</td>
                </tr>
              </table>
            </table-wrap>
            <p>	In 13 (48.1%) of the surveyed projects the risk of schedule delay and cost overrun was contractually shared between the client and contractor. Of these projects, 3 (11.1%) were delivered both on budget and on schedule, 5 (18.5%) were delivered on budget but behind schedule with the remaining 5 (18.5%) delivered both with cost overrun and schedule delay. In 3 projects (11.1%) the client assumed full responsibility for all the risks and insured against schedule delay and cost overrun. Of these, 1 (3.7%) was delivered within budget and ahead of schedule, 1 (3.7%) was delivered within budget but behind schedule with the remaining 1 (3.7%) project delivered over budget but within schedule. </p>
            <p>	In 8 projects (29.6%) the contractor assumed full responsibility for all the risks and provided guarantees. Of these projects, 3 (11.1%) were delivered on budget, while none was delivered on schedule. In 3 projects (11.1%) FIDIC conditions were used and schedule and cost risks were handled as they occurred. Of these projects, 1 (3.7%) was delivered within budget while none was delivered within schedule. In summary, these results show that of the 24 megaprojects that either transferred risk to the contractor or shared it between the client and the contractor, 13 megaprojects (54.2%) were delivered on budget while only 3 megaprojects (12.5%) were delivered within schedule. </p>
            <p>	Of the 3 megaprojects where the client assumed full responsibility for cost and schedule risk, 2 (66.7%) of these met both cost and schedule objectives. Generally, the results show that megaprojects that either transferred risk to the contractor or shared risk between the contractor and client had better cost performance but poor schedule performance.</p>
          </sec>
          <sec>
            <title>4.2.2 Emergence</title>
            <p>Project ambiguity arising from emergence was measured using a 6-item Likert type scale largely centred on assessing project stability. The responses on each item were rated on a 5-point mutually exclusive scale where a rating of 1 denoted a &#x201C;strongly agree&#x201D; response, 2 denoted &#x201C;agree&#x201D; response, 3 denoted &#x201C;somewhat agree&#x201D; response, 4 denoted &#x201C;disagree&#x201D; response, while 5 denoted a &#x201C;strongly disagree&#x201D; response. A choice of either 1 (strongly agree) or 2 (agree) implied low ambiguity while a choice of either 4 (disagree) or 5 (strongly disagree) implied high ambiguity. A choice of 3 (somewhat disagree) implied a neutral and borderline response which did not communicate much on the complexity of projects studied. As such, this neutral response was dropped from further analysis.</p>
            <p>	The results indicated that a total of 48.1% of the respondents agreed that assumptions, metrics and constraints remained stable throughout the life of their projects while 22.2% of the respondents disagreed with this statement. A total of 40.7% of the respondents agreed that the stakeholder requirements remained stable throughout their project life while 29.6% disagreed. On average, 55.5% of the respondents agreed that their projects were implemented in a politically and environmentally stable context with 18.5% of the respondents disagreeing. An aggregate of 81.5% of the respondents confirmed that the actual rate and type or propensity for change within their projects was manageable while 3.7% disagreed. In 70.3% of the projects surveyed, the respondents agreed that there was a documented change control system with identifiable change authority. However, in 14.8% of the projects, this was not the case. The results further indicated that contractual arrangements included incentives for the parties to assume responsibility for emerging project risks in only 7.4% of the projects. Table 4.20 summarizes these responses. </p>
            <p>	The cost and schedule performance results were mapped onto the responses with one cluster containing projects that either strongly agreed or agreed with the statements and the other containing those that disagreed or strongly disagreed. The results showed that for the projects in which assumptions, metrics and constraints remained stable through the life of the project, 53.8% were delivered on budget while 15.4% of those projects were delivered on schedule. Where assumptions, metrics and constraints did not remain stable throughout the life of the project, the results indicate that 66.7% of such projects were delivered within budget with only 16.7% of them being delivered within schedule. </p>
            <p>	Of the 11 projects in which stakeholder requirements remained stable throughout their life cycle, 54.5% were delivered within budget while 18.2% of those projects were delivered within schedule. For the projects in which stakeholder requirements did not remain stable throughout their life cycle, 50% were delivered within budget with only 12.5% of those projects being delivered within schedule. Projects which were conducted in a politically and environmentally stable context recorded a 46.7% chance of delivery within budget but only 20% of those projects were delivered within schedule. </p>
            <p>	Of the projects which were conducted in a politically and environmentally unstable context, 40% were delivered within budget with none of those projects being delivered within schedule. For the projects in which the actual rate and type or propensity for change was not manageable, 45.5% were delivered on budget while only 13.6% were delivered on schedule. Where the actual rate and type or propensity for change was not manageable, the project was delivered with both cost overrun and schedule delay. For the projects that had a documented change control system with identifiable change authority, 57.9% were delivered within budget while 21.1% were delivered within schedule. </p>
            <p>	The results further indicated that of the projects in which there was no documented change control system with identifiable change authority, 50% were delivered within budget but none of them was delivered within schedule. None of the projects surveyed utilized contractual arrangements that included incentives for the parties to assume responsibility for emerging project risks. However, for the projects in which contractual arrangements did not include incentives for the parties to assume responsibility for emerging project risks, 48.2% were delivered within budget with 18.5% being delivered within schedule. </p>
          </sec>
          <sec>
            <title>4.2.3 Uncertainty</title>
            <p>Ambiguity arising from uncertainty was measured using an 11-item Likert-type scale. The responses on each item were rated on a 5-point mutually exclusive scale where a rating of 1 denoted a &#x201C;strongly agree&#x201D; response, 2 denoted &#x201C;agree&#x201D; response, 3 denoted &#x201C;somewhat agree&#x201D; response, 4 denoted &#x201C;disagree&#x201D; response, while 5 denoted a &#x201C;strongly disagree&#x201D; response. A choice of either 1 (strongly agree) or 2 (agree) implied low ambiguity while a choice of either 4 (disagree) or 5 (strongly disagree) implied high ambiguity. A choice of 3 (somewhat disagree) implied a neutral and borderline response which did not communicate much on the complexity of projects studied. As such, this neutral response was dropped from further analysis.</p>
            <p>	The results showed that 40.7% of the respondents agreed that their projects were conducted over a relatively short period of time with a manageable number of stakeholder changes, while an equal proportion of respondents disagreed.  A total of 77.7% of the projects surveyed indicated that the requirements, scope and objectives were clearly developed while 7.4% disagreed. An aggregate 74% of the respondents confirmed that the success criteria for their projects were defined, documented and agreed upon by the stakeholders while 7.4% of the respondents disagreed. </p>
            <p>	Funding in 63% of the projects surveyed came from a single source or sponsor. In 33.3% of the projects, funding came from multiple sources. A total of 66.7% of the respondents indicated that their organizations had implemented similar projects before while 29.6% had not. In 81.5% of the projects, there were a manageable number of issues, risks and uncertainties but this was not the case in 11.1% of the projects.  It was indicated in 66.6% of the projects that suppliers were able to meet their commitments to the projects while in 7.4% of the projects, suppliers did not meet their commitments.                                    	 	In 71.3% of the projects, the client was prepared in advance to accept and sign off deliverables but this was not the case in 11.1% of the projects. In slightly over 85% of the projects surveyed, project documents and files were kept current in an accessible location by the team but this was not the case in 3.7% of the projects. Finally, 74% of the respondents indicated that their projects had a manageable number of critical paths while 3.7% did not agree. Table 4.22 summarizes these responses. 	 	To check the relationship between uncertainty and project success, the cost and schedule performance results for the projects were mapped onto the responses. The results indicated that 54.5% of the projects in which respondents agreed that the project was conducted over a relatively short period of time with a manageable number of stakeholder changes were delivered within budget with 27.3% of those projects being delivered within schedule. Of the 11 projects in which the respondents disagreed with this statement, 63.6% were delivered within budget while only 9.1% of those projects were delivered within schedule.                                                                                                       	Of the projects in which requirements, scope and objectives were clearly developed, 54.5% were delivered within budget with only 22.7% of those projects being delivered within schedule. Both the two projects in which the project requirements, scope and objectives were not clearly defined, were delivered within budget but only 1 was delivered on schedule. For the projects in which the success criteria was defined, documented and agreed upon by the stakeholders, 55% were delivered within budget while 25% were delivered within schedule. Both the projects in which the success criteria was not defined, documented and agreed upon by the stakeholders, were delivered on budget with none being delivered on schedule.  	 	An aggregate 46.7% of the projects whose funding was obtained from a single source or sponsor were delivered within budget with 26.7% of those projects being delivered within schedule. Where project funding came from multiple sources or sponsors, 55.6% were delivered within budget with none being delivered on schedule. For projects which had not been undertaken by the organization before, the chance of delivery within budget was 44.4% while that of delivery within schedule was 22.2%. Where that type of project was being delivered by the organization for the first time, the chance of delivery within budget went down to 37.5% while that of delivery on schedule dropped to 12.5%. 	In circumstances where the project had a manageable number of issues, risks and uncertainties, delivery within budget was recorded in 45.5% of the projects while delivery within schedule was recorded in only 13.6% of the projects. Where there were unmanageable number of issues, risks and uncertainties, cost delivery went down to 33.3% while schedule delivery slipped to zero. In projects where suppliers were able to meet commitments, 44.4% were delivered within budget and 16.7% were delivered within schedule. For the 2 projects in which suppliers could not meet their commitments, one was delivered on budget while both were delivered behind schedule. Of the 7 projects that were delivered to the committed deadlines, only 1 was delivered within budget, none was delivered within schedule. Where the projects did not deliver to the committed deadlines, 25% were delivered within budget but none was delivered within schedule. 		 	In circumstances where the client was prepared in advance to accept and sign off deliverables, the chance of delivery within schedule was 52.6% and that of delivery within budget was 26.3%. These went down to 33.3% and 0% in circumstances where the client was not prepared in advance to accept and sign off deliverables. The results also indicate that of the 26 projects in which project documents and files were kept current in an accessible location by the team, 43.5% of those projects were delivered within budget with 17.4% of those projects being delivered within schedule. The project in which this was not the case was delivered within budget but behind schedule. Of the 20 projects in which there were a manageable number of critical paths in the project, delivery within budget was recorded in 40% of the projects while delivery within schedule was recorded in 25% of the projects. The project in which there were many critical paths was delivered within budget but behind schedule. </p>
          </sec>
          <sec>
            <title>4.2.4 Hypothesis Testing</title>
            <p>In order to test the hypothesis that ambiguity has a significant influence on success of public infrastructural megaprojects, the constructs of ambiguity were scored to determine their complexity scores. The context construct was used to explain the constructs of emergence and uncertainty and was therefore not scored to determine the overall ambiguity score. The results show that the emergence construct had a mean score of 2.49 with a standard deviation of 0.66 while the uncertainty construct recorded a mean score of 2.17 with a standard deviation of 0.52. The weighted ambiguity score had a mean of 2.33 with a standard deviation of 0.52. The results indicated that the emergence scores had the highest relative variability (CV=0.26) compared to that of uncertainty (CV=0.24) and the weighted score (CV=0.22). With the coefficients of skewness and kurtosis being within the acceptable range of -1 to +1 for skewness and -2.2 to +2.2 for kurtosis (<xref rid="R18" ref-type="bibr" id="IDcf472e84-2881-4199-9aa8-5e59fdba4660">Sposito, Hand, &amp; Skarpness, 1983</xref>), the data was approximately normal and could therefore be used to conduct parametric tests such as correlation and regression.</p>
            <p>	Ambiguity scores were first correlated with those of project success to determine if they had any association. The results showed that at 99% confidence level, emergence had a significant negative correlation with process success (r=-0.495) and uncertainty had a strong significant negative correlation with process success (r=-0.706). Overall, the results showed that ambiguity had significant negative correlation with process success (CV=-0.687). The results indicated that both emergence and uncertainty had no relationship with product and organizational success, but uncertainty had a -0.641 correlation with the overall project success. The correlations are shown in Table 3. </p>
            <p><bold>Table 3: </bold>Correlation between Ambiguity and Project </p>
            <p>Success</p>
            <p> Project SuccessEmergenceUncertaintyAmbiguityscoreProcess Success-.495**-.706**-.687**Product Success-.139-.236-.214Organizational Success.133-.101.035Composite Success-.353-.641**-.561***. Correlation is significant at the 0.05 level (2-tailed).**. Correlation is significant at the 0.01 level (2-tailed).Project SuccessEmergenceUncertaintyAmbiguityscoreProcess Success-.495**-.706**-.687**Product Success-.139-.236-.214Organizational Success.133-.101.035Composite Success-.353-.641**-.561***. Correlation is significant at the 0.05 level (2-tailed).**. Correlation is significant at the 0.01 level (2-tailed).</p>
            <p>Causal relationship between ambiguity and megaproject success was tested using OLS linear regression at the 95% confidence level. The results indicated that there was no serial correlation in the data used to conduct regression analysis given a Durbin-Watson statistic value less than 2. Data was also checked for collinearity using the Tolerance and VIF statistics. The results indicated that the VIF was much lower than the cut-off value of 4 which is used as the threshold to indicate multicollinearity particularly in small samples (O&#x2019;Brien, 2007). The problem of heteroscedasticity was checked using residual statistics plotted on a scatter diagram. The results indicated that almost all the residuals had a mean of 0.000 and approximately equally spread around their mean implying that the data was roughly homoscedastic and was therefore good for OLS regression analysis. The results indicated that the overall model had a 31.5% predictive power (<italic>R</italic>2=0.315). ANOVA results showed that the overall model was significant with <italic>F</italic>(1<italic>,</italic>25)<italic>=11.501</italic> and <italic>P-Value&lt;</italic>
                     <mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" overflow="scroll"><mml:mfrac><mml:mrow><mml:mi>&#x3B1;</mml:mi></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:mfrac></mml:math>
                     <italic>. </italic>The regression equation is presented below:</p>
            <p><mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" overflow="scroll"><mml:mover><mml:mrow><mml:msub><mml:mrow><mml:maction actiontype="lit"><mml:mtext>PS</mml:mtext></mml:maction></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mrow><mml:mo>&#x2212;</mml:mo></mml:mrow></mml:mover></mml:math>= <mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" overflow="scroll"><mml:mn>6</mml:mn><mml:maction actiontype="lit"><mml:mtext>.</mml:mtext></mml:maction><mml:maction actiontype="lit"><mml:mtext>461</mml:mtext></mml:maction><mml:mo>&#x2212;</mml:mo><mml:mn>0</mml:mn><mml:maction actiontype="lit"><mml:mtext>.</mml:mtext></mml:maction><mml:maction actiontype="lit"><mml:mtext>743</mml:mtext></mml:maction><mml:msub><mml:mrow><mml:maction actiontype="lit"><mml:mtext>AM</mml:mtext></mml:maction></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:math></p>
            <p><mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" overflow="scroll"><mml:mover><mml:mrow><mml:msub><mml:mrow><mml:mi>b</mml:mi></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mrow/></mml:mover><mml:mo>)</mml:mo></mml:math>=(0.522) (0.219)</p>
            <p><mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" overflow="scroll"><mml:mi>t</mml:mi><mml:mo>=</mml:mo></mml:math> (12.368)   (-3.392)   <mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" overflow="scroll"><mml:msup><mml:mrow><mml:mi>R</mml:mi></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msup><mml:mo>=</mml:mo><mml:mn>0</mml:mn><mml:maction actiontype="lit"><mml:mtext>.</mml:mtext></mml:maction><mml:maction actiontype="lit"><mml:mtext>315</mml:mtext></mml:maction></mml:math>
                  </p>
            <p>Where <italic>s(</italic>
                     <mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" overflow="scroll"><mml:mover><mml:mrow><mml:msub><mml:mrow><mml:mi>b</mml:mi></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mrow/></mml:mover><mml:mo>)</mml:mo></mml:math> is the standard error of beta estimate. </p>
            <p>The results show that at 95% confidence level, the <italic>s(</italic>
                     <mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" overflow="scroll"><mml:mover><mml:mrow><mml:msub><mml:mrow><mml:mi>b</mml:mi></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mrow/></mml:mover><mml:mo>)</mml:mo></mml:math>&#x2C2; <mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" overflow="scroll"><mml:mfenced separators="|"><mml:mrow><mml:mfrac><mml:mrow><mml:mover><mml:mrow><mml:msub><mml:mrow><mml:mi>b</mml:mi></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mrow/></mml:mover></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:mfrac></mml:mrow></mml:mfenced></mml:math> for both the intercept and the slope of the equation. Thus, following Koutsoyiannis (1992), the null hypothesis that <mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" overflow="scroll"><mml:msub><mml:mrow><mml:mi>b</mml:mi></mml:mrow><mml:mrow><mml:mn>0</mml:mn></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:msub><mml:mrow><mml:mi>b</mml:mi></mml:mrow><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mn>0</mml:mn></mml:math> was rejected and a conclusion made that the betas were significant. The results showed that the slope of Ambiguity was significant, implying that a one unit increase in ambiguity reduced project success score by 0.743. Thus, the research hypothesis that ambiguity has a significant influence on success of public infrastructural megaprojects was accepted.</p>
          </sec>
        </sec>
      </sec>
      <sec>
        <title>Discussion</title>
        <p>It is generally recognized in normative literature that the FFP is the most commonly used contract type (<xref ref-type="bibr" id="ID9096635e-d42c-4016-9a51-4d0baa315e18">PMI, 2013c</xref>). However, this study established that most infrastructural megaprojects utilized FP-EPA and the FFP was utilized by just one third of the projects surveyed. Given the sample size of this study, it may be difficult to draw a conclusion against the postulation of normative literature. The use of FP-EPA contractual arrangements is backed by the long term nature of the projects studied with the implementation of some spanning up to 6 years. With such longer implementation periods, it is likely that factors outside the control of the client or contractor, such as inflation and currency fluctuation, may adversely affect cost performance. </p>
        <p>	The use of Fixed Price contracts is usually a tactic of transferring the risk of cost overrun to the contractor. In the case of FFP contracts, the entire risk of cost overrun is actually transferred from the client to the contractor. In such cases, the contractors are usually careful not to eat into their profit margins. The results of this study agree with this practice given that a larger proportion of projects that utilized FFP contracts recorded the highest cost performance. This was followed by projects that utilized FP-EPA, which is a variation of FP contracts. Despite having recorded superior cost performance, projects that utilized FFP recorded the highest schedule slippage. This could mean that utilizing FFP contracts could be a zero sum game-since project management success must take into account both cost and schedule performance. It is noted that projects whose contracts included late delivery penalties actually delivered on schedule. This means that the use of FFP should be adjusted to include late delivery penalties if the objectives of both cost and schedule are to be achieved simultaneously. </p>
        <p>	The results indicated that none of the projects utilized contractual arrangements with incentives for accelerated cost or schedule delivery. Such pain/gain contracts would include Fixed Price Incentive Fee, Cost-Plus Incentive Fee or Cost-Plus Award Fee. The use of these types of contracts incentivizes the contractor for superior delivery of the pre-agreed performance metrics such as schedule and cost performance (<xref ref-type="bibr" id="ID51bb47bf-9c94-4bea-928e-360c1d6dc2c1">PMI, 2013</xref>). As such, using these types of contracts is strongly associated with superior project performance (<xref ref-type="bibr" id="IDc22e34b6-12d2-430a-8f3f-826d6513881c">Brady &amp; Davis, 2014</xref>) since the parties involved in the project may prefer different actions because of their different risk preferences (<xref ref-type="bibr" id="ID50ee1866-332d-43c6-8fab-f50a84b9ca93">Eisenhardt, 1989</xref>). Thus, the pain/gain contractual arrangements can be critical in solving the agency problem that characterizes most employer-contractor relationships (<xref ref-type="bibr" id="ID765ec192-1508-4197-8757-aa252fe0596e">Jensen &amp; Meckling, 1976</xref>) on projects.</p>
        <p>	It is argued that transferring risk to the contractor (as in the use of Fixed Price contracts) offers no real protection for the client because the client is always accountable for cost, time, quality and safety (<xref ref-type="bibr" id="ID53c1da31-139e-4805-9082-d83051c78150">Brady &amp; Davis, 2014</xref>). The results of this study agree with this argument given that 2 out of the 3 projects in which the client assumed full responsibility for risk of cost overrun and schedule delay met their cost and schedule objectives. Thus, even though numbers are still small, the findings of this study could be pointing to the fact that behavior-oriented contracts lead to better results than outcome-based contracts.</p>
        <p> 	The results of this study seem to agree with the postulation of normative literature that emergence can have both positive and negative effect on project outcomes. (<xref ref-type="bibr" id="ID160a794a-583f-4642-8da9-e11d0f206af9">PMI, 2014</xref>). Emergence may enhance the ability of a project to innovate which in turn could improve project delivery capability. As an illustration, projects in which assumptions, metrics and constraints did not remain stable throughout their life recorded much better cost and schedule performance compared to those in which assumptions, metrics and constraints remained stable. The implication of this is that contractual arrangements in projects should ensure collaborative efforts with appropriate incentives to encourage the parties to solve problems that emerge as a result of progress elaboration and during execution (<xref ref-type="bibr" id="IDc739d499-eece-4b43-8b2e-227b0b646d40">Brady &amp; Davis, 2014</xref>).</p>
        <p>	Stability of stakeholder requirements is a key aspect of complexity that affects the delivery capability of a project since emergence in stakeholder requirements implies emergence in scope. As the findings of this study attest, emergence in stakeholder requirements throughout the project&#x2019;s life cycle could lead to reduced cost and schedule performance thereby dimming chances of project management success. </p>
        <p>	Likewise, stability in the political and physical environment of a project could affect project delivery capability. In this study, instability in the political and physical environment adversely affected chances of delivery within budget and schedule. This is plausible particularly given that public infrastructural projects are implemented in delivery of a &#x201C;political manifesto&#x201D; and so instability in the political system inevitably affects project management success.</p>
        <p>	As noted by Swartz (<xref rid="R19" ref-type="bibr" id="ID64023dbd-c879-4ada-ab1c-eddb2a90d20e">2008</xref>), emergence can disrupt a project schedule, and the ability of the schedule to absorb that disruption is critical for the delivery of project outcomes. In situations where the actual rate and type or propensity for change is not manageable, as is the case in complex infrastructural megaprojects, the apparent schedule disruption may also disrupt cost performance. Indeed, the results of this study attest to this-where the actual rate and type or propensity for change was not manageable, cost and schedule delivery slipped to zero. In most cases where the project context was not stable, schedule delivery was adversely affected.</p>
        <p>	Change management is known to create a superior culture that supports open communication, trust and cooperation (<xref ref-type="bibr" id="ID6a117a36-c227-45ec-a8c0-280ec401abfc">Kerzner, 2009</xref>) among various stakeholders on the project. It allows for documented changes within the project to be considered in an integrated fashion while reducing project risk (<xref ref-type="bibr" id="IDbd1fb898-8d13-4cf8-b0cc-a7db6ae107d6">PMI, 2013c</xref>). A well-documented change control system helps to identify, assess and control any potential and approved changes to the project baselines (<xref ref-type="bibr" id="ID1797bdeb-cdb0-4306-8521-e79aa7c72bb1">Axelos, 2017</xref>) in order to avoid scope creep. In support of this, the results of this study show that projects that had a documented change control system with identifiable change authority returned a higher probability of delivery within budget and schedule. </p>
        <p>	Whereas none of the projects surveyed utilized contractual arrangements that included incentives for the parties to assume responsibility for emerging project risks, positive literature suggests that behavior-based contracts could return better project success results than outcome-based contracts. Such contracts enhance ambidexterity (simultaneous pursuit of efficiency and innovation) on projects, which in effect has significant effect on project performance (<xref ref-type="bibr" id="ID8aa4c72b-521c-46df-95f5-822022232597">Liu &amp; Leitner, 2012</xref>). This is supported in a study to compare the complexity of two successful projects by Brady and Davis (<xref rid="R12" ref-type="bibr" id="ID17ebb9c1-d080-4257-b254-766eedf44bb5">2014</xref>) who showed that the use of collaborative pain/gain contracts can indeed enhance project success. </p>
        <p>	Empirical research shows that the longer the duration of the project the larger its cost overrun (<xref ref-type="bibr" id="ID56ac9cbc-6e3c-4089-8a65-802e1c2f6db3">Flyvbjerg et al., 2004</xref>). However, based on the findings of this study, longer schedule duration is associated with increased delivery of projects under budget. This finding appears to be in line with the thinking of economic theory that uncertainties are necessary conditions for the existence of opportunities and that without uncertainty entrepreneurial profits would be impossible (<xref ref-type="bibr" id="IDb9b1a7a0-4d86-4379-ae45-634caa3ca439">Knight, 1948</xref>). What is apparent from the findings of this study is that longer schedule duration is associated with reduced delivery within schedule.</p>
        <p>	Clear requirements documentation and scope definition are critical prerequisites for designing quality scope baselines. This also involves developing and documenting clear success criteria that is agreed upon by the stakeholders. Complexity arising from uncertainty affects the stability of project baselines and of the decisions made. The results of this study showed that high uncertainty has more negative effect on schedule performance than on cost performance. Chances of delivery over budget and behind schedule were high where the client was not prepared in advance to accept and sign off deliverables, implying that benefits realization planning is important for project success. </p>
        <p>	The results also showed that delivery over budget and behind schedule was equally high where the project had a large number of issues, risks and uncertainties. The implication of this is that change and risk management planning are critical to avoid firefighting whenever the vagaries of uncertainty hit a project. The Practice Guide on Navigating Complexity (<xref ref-type="bibr" id="ID41345933-dd07-46fb-b5cb-e2b37a14e363">PMI, 2014</xref>) recognizes that adequate risk and change management procedures should be in place to enable proper actions during the times of uncertainty, and risk sharing and collaboration are key strategies to handle uncertainty. This study found that chances of delivery over budget and behind schedule are also high in circumstances where that type of project had not been undertaken by the organization before. This confirms that the principle of learning from experience could lead to better project outcomes (<xref ref-type="bibr" id="IDdd0e4c5c-71c7-4f41-9238-89d086fb2a58">Axelos, 2017</xref>). </p>
        <p>	The results of this study indicate that ambiguity has only significant relationship with process success. The implication of this is that accepting and dealing with ambiguity should be a key aspect of project management. Hagen and Park (<xref ref-type="bibr" id="ID573bfe21-0116-4596-88af-d02c382b9d02">2013</xref>) assert that acceptance of ambiguity is a key trait that differentiates between effective and ineffective leaders. The results of this study also indicate a significant positive relationship between emergence and uncertainty (r=.454). The implication of this is that there is an overlap between these constructs and distinguishing their independent effects on project outcomes can be difficult. </p>
        <p>	It is recognized in normative literature that ambiguity can have either positive or negative effect on project outcomes (<xref ref-type="bibr" id="ID110a6004-bc75-4294-9494-9972f2f8062e">PMI, 2014</xref>).  In a study on the effects of ambiguity on project task structure in new product development, Duimering, Ran, Derbentseva and Poile (<xref ref-type="bibr" id="ID33491aba-6086-4cd5-af67-9fe023c30ef4">2006</xref>) concluded that knowledge of how the task structures evolve (emergence) can lead to improved strategies for managing projects with ambiguous requirements. However, the findings of this study only established that ambiguity leads to negative project outcomes. </p>
      </sec>
      <sec>
        <title>Conclusions and Recommendation</title>
        <p>Ambiguity had significant negative influence on process and overall project success but had no significant relationship with product or organizational success. Thus, as the infrastructural megaproject&#x2019;s context becomes ambiguous, its success is negatively impacted. Both uncertainty and emergence appeared to negatively affect schedule delivery more than cost delivery. This is explained by the contractual context in which these projects were implemented. 	Infrastructural megaprojects majorly utilized FFP and FP-EPA contracts. Even though usage of these contract types led to increased chances of delivery within budget, they carried with them an inherent risk of delivery behind schedule. However, inclusion of late delivery penalties in these contracts helped remedy the risk of schedule slippage. 	Projects in which the client assumed responsibility for cost and schedule risk had higher chances of meeting both cost and schedule objectives when compared to those in which risk was either transferred to a third party or shared contractually. Transferring or sharing project risk increased chances of achieving the cost objective but greatly reduced chances of meeting the schedule objective. The results of this study point to the fact that the effects of ambiguity-whether from the project&#x2019;s context, emergence or uncertainty, can be managed contractually. 	 	Neither the usage of outcome-based nor behavior-based contracts in isolation can solve the negative effect of ambiguity on success of public infrastructural megaprojects. We recommend that the design of these projects utilizes hybrid contracts based on complexity science and blending both outcome and behavior based contracts. Such contracts should ensure that the contractors are able to act in the best interest of their clients and that the clients have access to Project Management Information Systems (PMIS) capable of supplying them with information required to verify the behavior of contractors. Such PMIS could include Earned Value Management Systems (EVMS) or Risk Management System (RMS) to enable identification of management of Early Warning Signs (EWS).</p>
      </sec>
      <sec>
        <title>References</title>
        <list list-type="order">
          <list-item>
            <p>Atkinson, R. (<xref ref-type="bibr" id="ID4b3a2673-b24f-413c-a0f6-8cd474ec29c3">1999</xref>). Project management: Cost, time and quality, two best guesses and a phenomenon, it is time to accept other success criteria. <italic>International Journal of Project Management, 17</italic>(<xref ref-type="bibr" id="IDc563690f-ebd5-41b1-b63a-c199fea8d42a">6</xref>), 337-342.</p>
          </list-item>
          <list-item>
            <p>Axelos Limited. (<xref ref-type="bibr" id="IDdedd29de-8409-4365-ab42-f461eafb4a2e">2017</xref>). <italic>Managing Successful Projects with PRINCE2</italic>&#xAE; (6th ed.). United Kingdom: TSO, ISBN: 9780113315338.</p>
          </list-item>
          <list-item>
            <p>Baccarini, D. (<xref ref-type="bibr" id="ID4de8aeab-f7e4-42b1-9da0-f8911d66bcb5">1999</xref>). The logical framework method of defining project success. <italic>Project 	Management Journal, 30</italic>(<xref ref-type="bibr" id="IDb8557995-7c2d-46d2-a757-83d95dcf1d0f">4</xref>), 25-32.</p>
          </list-item>
          <list-item>
            <p>Bannermann, P.L. (<xref rid="R19" ref-type="bibr" id="ID78862a09-3ee2-4da4-98cd-eaa8e3001f8a">2008</xref>). Defining project success: A multilevel framework. In 	<italic>Proceedings of the PMI Research Conference</italic> (pp. 1-14). Newton Square, PA: Project Management Institute.</p>
          </list-item>
          <list-item>
            <p>Brady, T., &amp; Davies, A. (<xref rid="R12" ref-type="bibr" id="ID4f404527-5ddb-4a1e-8def-37da0fc66587">2014</xref>). Managing Structural and Dynamic Complexity: A Tale 	of Two Projects. <italic>Project Management Journal</italic>, <italic><xref ref-type="bibr" id="IDffea76b4-354d-4404-88a0-842267ada082">4</xref>5</italic>(4), 21-38. </p>
          </list-item>
        </list>
        <list list-type="order">
          <list-item>
            <p>Bruzelius, N., Flyvbjerg, B., Rothengatter, W. (<xref ref-type="bibr" id="ID43a1e508-9f7c-4b98-8be0-c043d4dc603c">2002</xref>). Big decision, big risks.  Improving accountability in mega projects. <italic>Transport Policy</italic>, <italic>9</italic>(<xref ref-type="bibr" id="IDb7d00f91-3bf6-45f9-bee8-862e109562e1">2</xref>), 143&#x2013;154.</p>
          </list-item>
          <list-item>
            <p>Bryman, A., &amp; Bell, E. (<xref rid="R20" ref-type="bibr" id="ID91b1c64b-45a5-4d55-884b-45c7fafc2479">2007</xref>). <italic>Business Research Methods</italic> (2nded.). New York, United States: 	Oxford University Press Inc., p. 55. </p>
          </list-item>
          <list-item>
            <p>Burch, P., &amp; Carolyn, H. J. (<xref ref-type="bibr" id="IDddb3b42c-c89d-4562-8b32-8f94a4b738c6">2016</xref>). <italic>Mixed Methods for Policy Research and Program 	Evaluation</italic>. Thousand Oaks, CA: Sage.</p>
          </list-item>
          <list-item>
            <p>Caldart, A. A., &amp; Joan, E. R., (<xref ref-type="bibr" id="ID4ad9a5fd-05f0-4792-9a98-eebce99418dc">2004</xref>). <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.referenceforbusiness.com/knowledge/Strategic_management.html" ext-link-type="uri" xlink:type="simple">Corporate Strategy </ext-link> Revisited: A View from 	Complexity Theory.<italic> European Management Review, <xref rid="R20" ref-type="bibr" id="IDae93b5eb-2ada-467e-8698-f982cdc34de9">1</xref>
                     </italic>(1).</p>
          </list-item>
          <list-item>
            <p>Collyer, S. (<xref ref-type="bibr" id="IDb8d8f51f-712a-48d1-9a42-c45e5f94e803">2016</xref>). Culture, Communication, and Leadership for Projects in Dynamic Environments. <italic>Project Management Journal</italic>, <italic>47</italic>(<xref ref-type="bibr" id="IDaacae691-7b16-4f63-829d-dc9939562d7a">6</xref>), 111&#x2013;125.</p>
          </list-item>
          <list-item>
            <p>Connelly, L. M. (<xref rid="R19" ref-type="bibr" id="ID87022eb9-5c7e-4768-a181-97c9b8cf1a24">2008</xref>). Pilot studies. <italic>Medsurg Nursing</italic>, <italic>17</italic>(<xref ref-type="bibr" id="IDf2885de3-bcbd-42cc-ae71-46c3b4505ce3">6</xref>), 411-412.</p>
          </list-item>
          <list-item>
            <p>Cooke-Davies, T. (<xref ref-type="bibr" id="ID0eed6296-7e24-459f-9b4d-f8b725191255">2002</xref>). The real success factors on projects. <italic>International Journal of 	Project Management, 20</italic>(<xref ref-type="bibr" id="IDcc6c5495-fea6-4db0-a67f-e9ca95bdd6c2">3</xref>), 185-190.</p>
          </list-item>
          <list-item>
            <p>Cooke-Davies, T., Crawford, L., &amp; Stevens, C. (<xref rid="R13" ref-type="bibr" id="ID94c7f6de-2dc3-4e5a-9596-1f220d64db91">Eds.</xref>). (<xref rid="R13" ref-type="bibr" id="IDb4eb3dc3-ddc8-4924-8443-68ce2b752557">2011</xref>). <italic>Aspects of Complexity: Managing projects in a complex world</italic>. Pennsylvania, USA: Project Management Institute.</p>
          </list-item>
          <list-item>
            <p>Cronbach, L.J. (<xref ref-type="bibr" id="ID8a40fcf4-daf0-42d1-99c0-05cc244d460b">1951</xref>). Coefficient alpha and the internal structure of tests. <italic>Psychometrika, 	16</italic>(<xref ref-type="bibr" id="IDefe6998e-d6bd-46b4-884c-673659fd6cc4">3</xref>), 297-334.</p>
          </list-item>
          <list-item>
            <p>de Wit, A. (<xref ref-type="bibr" id="IDe87ec15d-ae97-43a5-a31c-3152b35020d7">1988</xref>). Measurement of Project success. <italic>Project Management Journal, 6</italic>(<xref ref-type="bibr" id="IDad30a987-cb6e-4c51-ab9d-8462e75259a4">3</xref>), 164-170<italic>.</italic>
                  </p>
          </list-item>
          <list-item>
            <p>Duimering, P.R., Ran, B., Derbentseva, N., &amp; Poile, C. (<xref ref-type="bibr" id="ID8db4dea8-288d-42ca-9ef3-cbceca1e5686">2006</xref>). The Effects of Ambiguity 	on Project Task Structure in New Product Development, <italic>Knowledge and Process 	Management, 13</italic>(<xref ref-type="bibr" id="ID48f64154-1cbd-4fcd-8e09-183c2d7a59ba">4</xref>), 239-251.</p>
          </list-item>
          <list-item>
            <p>Flyvbjerg, B. (<xref rid="R12" ref-type="bibr" id="ID6e919fb7-7a2a-4d70-a948-102d9e78eb85">2014</xref>). What You Should Know About Mega Projects and Why: An 	Overview<italic>. Project Management Journal, 45</italic>(<xref ref-type="bibr" id="IDf4950a88-b6d7-44b1-a016-01073bbd8962">2</xref>), 6-17.</p>
          </list-item>
          <list-item>
            <p>Flyvbjerg, B., Holm, M.K.S., &amp; Buhl, S.L. (<xref ref-type="bibr" id="ID42cfe0dd-2bfd-4364-9555-d4e680d64212">2004</xref>). What causes cost overrun in transport 	infrastructure projects? <italic>Transport Reviews, 24</italic> (<xref rid="R20" ref-type="bibr" id="ID3abd42c0-ab7d-4de6-a78b-1c64675c1a2f">1</xref>), 3-18.</p>
          </list-item>
          <list-item>
            <p>Gauthier, J-B., &amp; Ika, L.A. (<xref ref-type="bibr" id="IDdb4ca9c5-7cd7-463b-967b-3c74df9813bb">2012</xref>). Foundations of Project Management Research: An Explicit and Six-facet Ontological Framework. <italic>Project Management Journal</italic>, <italic>43</italic>(<xref ref-type="bibr" id="IDbec2b523-46bb-4f2b-8647-6f04b797ef98">5</xref>), 5-23.</p>
          </list-item>
          <list-item>
            <p>Government of Kenya. (<xref ref-type="bibr" id="IDe9063fd1-cbe1-4ee4-8a65-88c1796bbca8">2013</xref>). <italic>Second Medium Term Plan</italic>, <xref ref-type="bibr" id="ID0032300c-919f-4c3e-90ac-e174105f81b9">2013</xref>-2013. Kenya Vision 	2030: Author.</p>
          </list-item>
          <list-item>
            <p>Hagen, M., &amp; Park, S. (<xref ref-type="bibr" id="ID5dd62725-68a3-4d6b-8bd4-6ec75a5cee52">2013</xref>). Ambiguity Acceptance as a Function of Project Management: A new Critical Success Factor. <italic>Project Management Journal, 44</italic>(<xref ref-type="bibr" id="IDd660d20f-a0b6-407b-998a-17e993248ad3">2</xref>), 	52-66.</p>
          </list-item>
          <list-item>
            <p>Hair, J.F., Babin, B., Money, A., &amp; Samouel, P. (<xref ref-type="bibr" id="IDacf02445-67af-4449-8bbb-78e37fa4e80a">2003</xref>). <italic>The essentials of business 	research methods</italic>. London: Wiley.</p>
          </list-item>
          <list-item>
            <p>Hirschman, A.O. (<xref ref-type="bibr" id="ID62e964fd-6c2a-428f-8742-5c152dd0a9f1">1995</xref>). <italic>Development projects observed</italic> (2nd ed.). Washington, D.C: Brookings Institution.</p>
          </list-item>
          <list-item>
            <p>Hoegl, M., &amp; Gemuenden, H.G. (<xref rid="R16" ref-type="bibr" id="ID277908ca-c2ec-4151-862d-d82168cb6316">2001</xref>). Team work quality and the success of innovative projects: A theoretical concept and empirical evidence. <italic>Organization Science, 12</italic>(<xref ref-type="bibr" id="ID4a094198-fb3e-49e2-b6fd-1297019cf635">4</xref>), 435-449<italic>.</italic>
                  </p>
          </list-item>
          <list-item>
            <p>Ika, L.A. (<xref ref-type="bibr" id="ID3299c372-7e65-426a-b0d9-9f6bcc22d343">2009</xref>). Project success as a topic in project management journals. <italic>Project Management 	Journal, <xref ref-type="bibr" id="ID44120536-2dce-4637-8071-e1598c3bc4b2">4</xref>0</italic>(4),<italic> 6-19.</italic>
                  </p>
          </list-item>
          <list-item>
            <p>Jensen, M., &amp; Meckling, W. (<xref ref-type="bibr" id="IDb9e3a993-bc89-4e08-ab94-de7f22a21b23">1976</xref>). Theory of the firm: Managerial behavior, agency costs, and ownership structure.  <italic>Journal of Financial Economics, 3</italic>, 305-360.</p>
          </list-item>
          <list-item>
            <p>Jugdev, K., &amp; Muller, R. (<xref ref-type="bibr" id="ID16a24186-dccc-4f60-ad29-cd466730070e">2005</xref>). A retrospective look at our evolving understanding of project success. <italic>Project Management Journal, 36</italic>(<xref ref-type="bibr" id="IDd5067c1f-c7a5-4df1-b914-29dd4d168c5d">4</xref>), 19-31.</p>
          </list-item>
          <list-item>
            <p>Jugdev, K., Thomas, J., &amp; Delisle, C.L. (<xref rid="R16" ref-type="bibr" id="ID01cccb7b-1ac8-481d-9558-fc43419bb8bd">2001</xref>). Rethinking Project Management: Old 	truths and new insights. <italic>Project Management Journal, 7</italic>(<xref rid="R20" ref-type="bibr" id="IDae010f42-b733-4836-8add-ace1a175c36c">1</xref>), 36-43<italic>.</italic>
                  </p>
          </list-item>
          <list-item>
            <p>Kahneman, D., &amp; Tversky, A. (<xref ref-type="bibr" id="ID68541195-7c93-41f1-91d6-c773b1640397">1979</xref>). Intuitive prediction: biases and corrective procedures. In S. Makridakis, &amp; S. C. Wheelwright (<xref rid="R13" ref-type="bibr" id="ID20ebb1b9-0e37-4983-b94a-12fa74802b7e">Eds.</xref>), <italic>Studies in the 	Management Sciences: Forecasting</italic>, <italic>12</italic>. North-Holland, Amsterdam, pp.313&#x2013;27.</p>
          </list-item>
          <list-item>
            <p>Kellert, S. H. (<xref ref-type="bibr" id="ID86d68a9b-8c72-4cd4-9385-80fd2eb78269">1993</xref>). <italic>In the Wake of Chaos: Unpredictable Order in Dynamical Systems</italic>. University of 	Chicago Press. </p>
          </list-item>
          <list-item>
            <p>Kerzner, H. (<xref rid="R19" ref-type="bibr" id="ID642d6ae7-6d7a-42f5-96c6-9a68668891a7">2008</xref>), <italic>Project Management-A Systems Approach to Planning, Scheduling, 	and Controlling</italic>, (10th ed.). John Wiley &amp; Sons Inc.</p>
          </list-item>
          <list-item>
            <p>Knight, E. H. (<xref ref-type="bibr" id="ID008d71a4-30e4-4644-87c6-851fd26e1656">1948</xref>). <italic>Risk, Uncertainty and Profits</italic> (7th ed.). London, England: London School of Economics and Political Science.</p>
          </list-item>
          <list-item>
            <p>Koutsoyiannis, A. (<xref rid="R21" ref-type="bibr" id="IDd27b64c8-7d95-4505-b648-f91975bdd76d">1992</xref>). <italic>Theory of Econometrics</italic> (2nd ed.). Hong Kong: Macmillan Education.</p>
          </list-item>
          <list-item>
            <p>Likert, R. (<xref ref-type="bibr" id="ID80636583-071c-48d6-8e81-fb87dd169293">1931</xref>). A technique for the measurement of attitudes. <italic>Archive of psychology, 22</italic>(<xref ref-type="bibr" id="ID06df3acf-2ad2-4425-94c8-f251d3555e52">140</xref>), 1-55.</p>
          </list-item>
        </list>
        <list list-type="order">
          <list-item>
            <p>Liu, L., &amp; Leitner, D. (<xref ref-type="bibr" id="IDa4f36d07-6a37-401b-b114-7c44a3cc2923">2012</xref>). Simultaneous Pursuit of Innovation and Efficiency in Complex Engineering Projects-A Study of the Antecedents and Impacts of Ambidexterity in Project Teams. <italic>Project Management Journal, 43</italic>(<xref ref-type="bibr" id="ID1d1219d9-1611-4597-b75b-0744030b5dab">6</xref>), 97-110.</p>
          </list-item>
          <list-item>
            <p>Lorenz, E. N. (<xref ref-type="bibr" id="IDcc64e2f4-c64c-466e-8fee-5b6e8392835e">1963</xref>). Deterministic non-periodic flow. <italic>Journal of the Atmospheric Sciences, <xref ref-type="bibr" id="ID5a50c324-d980-48a2-a3bc-5dba66da5fec">2</xref>0</italic> (2), 130&#x2013;141. </p>
          </list-item>
          <list-item>
            <p>Lovallo, D., &amp; Kahneman, D. (<xref ref-type="bibr" id="ID225a2fe3-e01e-4648-83fe-fe77cca4c81e">2003</xref>). Delusions of success, how optimism undermines executives&#x2019; decisions.<italic>Harvard Business Review</italic>, <italic>81</italic> (<xref ref-type="bibr" id="ID9356bfe2-260f-43fb-9300-f10f38e1daba">7</xref>), 57&#x2013;63</p>
          </list-item>
          <list-item>
            <p>Lucas, T. (<xref ref-type="bibr" id="IDabe7ed37-0481-4a14-85f8-b3d06d97d09a">2009</xref>). <italic>Quantifying complexity</italic>. Website. </p>
          </list-item>
          <list-item>
            <p><ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.calresco.org/lucas/quantify.htm" ext-link-type="uri" xlink:type="simple">www.calresco.org/lucas/quantify.htm</ext-link>. March 2015.</p>
          </list-item>
          <list-item>
            <p>Mackie, P. and J. Preston (<xref rid="R22" ref-type="bibr" id="IDb47c25ec-7f82-4e83-93f5-09085c820401">1998</xref>). "Twenty-one sources of error and bias in transport 	project appraisal." Transport Policy, 5, pp 1-7.</p>
          </list-item>
          <list-item>
            <p>Markus, M.L., &amp; Mao, J.Y. (<xref ref-type="bibr" id="IDbe88fc6f-2d33-474f-aa6b-19ce62b07b38">2004</xref>). Participants in development and implementation-	Updating an old tired concept for today&#x2019;s IS contexts. <italic>Journal of the Association for Information Systems, 5</italic>(11-12), 514-544<italic>.</italic>
                  </p>
          </list-item>
          <list-item>
            <p>Maylor, H., Vidgen, R., &amp; Carver, S. (<xref rid="R19" ref-type="bibr" id="ID83962667-6bf8-4294-ae74-6d03086deb45">2008</xref>). Managerial Complexity in Project based Operations: A grounded model and its implications for practice. <italic>Project Management Journal,</italic> 
                     <italic>39</italic>(<xref rid="R20" ref-type="bibr" id="ID0c2cfa8f-fdf7-49db-b035-5ba86103b241">1</xref>), 15-26.</p>
          </list-item>
          <list-item>
            <p>McLeod, L., Doolin, B., &amp; MacDonell, G. S. (<xref ref-type="bibr" id="IDfee7d1bb-4608-4acc-acc6-0fc7540a8b8e">2012</xref>). A Perspective-Based Understanding of Project Success. <italic>Project Management Journal, 43</italic>(<xref ref-type="bibr" id="ID5920e655-23f7-4864-a127-b0960bacb1b3">5</xref>), 68-86.</p>
          </list-item>
          <list-item>
            <p>Meyer, W. G. (<xref rid="R12" ref-type="bibr" id="ID29a973a7-89ff-401a-a12d-14453c3bff68">2014</xref>). The Effect of Optimism Bias on the Decision to Terminate Failing Projects. <italic>Project Management Journal, <xref ref-type="bibr" id="ID56619aeb-3bbe-473a-a732-4c50973cefd2">4</xref>5</italic>(4), 7-20.</p>
          </list-item>
          <list-item>
            <p>Neuman, W.L. (<xref ref-type="bibr" id="ID107576d3-bc65-4a61-903d-3b42fa66bde5">2003</xref>). <italic>Social research methods: Qualitative and quantitative approaches,</italic> (5th ed.). Upper Saddle River, NJ: Pearson Education.</p>
          </list-item>
          <list-item>
            <p>Olaniran, O.J., Love, P.E.D., Edwards, D., Olatunji, O.A., &amp; Mathews, J. (<xref ref-type="bibr" id="ID65112b4f-881b-4079-8184-5f9e702c4e5b">2015</xref>). Cost Overruns in Hydrocarbon Megaprojects: A Critical Review and Implications for Research. <italic>Project Management Journal, 4<xref ref-type="bibr" id="ID68511c9d-3910-4e76-a584-200329d5ff59">6</xref>
                     </italic>(6), 126-138.</p>
          </list-item>
          <list-item>
            <p>Papadopoulos, T., Ojiako, U., Chipulu, M., &amp; Lee, K. (<xref ref-type="bibr" id="ID8e9f2fba-4366-45cf-9a42-d9a653004b8b">2012</xref>). The Criticality of Risk Factors in Customer Relationship Management Projects. <italic>Project Management Journal, 43</italic>(<xref rid="R20" ref-type="bibr" id="IDf21be166-034c-4fad-9e6e-0dbba9218e4e">1</xref>), 65-75.</p>
          </list-item>
          <list-item>
            <p>Project Management Institute. (<xref ref-type="bibr" id="ID201d2f51-9754-4735-8f44-7fdd64bfb7d3">2013</xref>). <italic>A Guide to the Project Management Body of Knowledge</italic> (5th ed.). Pennsylvania, USA: Author.</p>
          </list-item>
        </list>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list><ref id="R12"><element-citation publication-type="journal"><person-group person-group-type="author"/><article-title>Going beyond theProject Management Body of Knowledge(PMBOK&#xAF;)Guide</article-title><source>Complexity Theory and Project Management</source><publisher-name>John Wiley &amp; Sons, Inc.</publisher-name><year>2010</year><fpage>15</fpage><lpage>48</lpage><pub-id pub-id-type="doi">10.1002/9780470949986.ch2</pub-id></element-citation></ref><ref id="R13"><element-citation publication-type="journal"><person-group person-group-type="author"/><article-title>Successful Project Management Strategies of Complexity</article-title><source>Complexity Theory and Project Management</source><publisher-name>John Wiley &amp; Sons, Inc.</publisher-name><year>2010</year><fpage>103</fpage><lpage>115</lpage><pub-id pub-id-type="doi">10.1002/9780470949986.ch5</pub-id></element-citation></ref><ref id="R14"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Mulenburg</surname><given-names>Gerald</given-names></name></person-group><article-title>Reinventing Project Management: The Diamond Approach to Successful Growth and Innovation by Aaron Shenhar and Dov Dvir</article-title><source>Journal of Product Innovation Management</source><year>2008-sep</year><fpage>635</fpage><lpage>637</lpage><pub-id pub-id-type="doi">10.1111/j.1540-5885.2008.00327_2.x</pub-id></element-citation></ref><ref id="R15"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Shenhar</surname><given-names>Aaron</given-names></name><name><surname>Dvir</surname><given-names>Dov</given-names></name></person-group><article-title>Project Management Research - The Challenge and Opportunity</article-title><source>IEEE Engineering Management Review</source><year>2008</year><fpage>112</fpage><lpage>121</lpage><pub-id pub-id-type="doi">10.1109/emr.2008.4534315</pub-id></element-citation></ref><ref id="R16"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Shenhar</surname><given-names>AaronJ</given-names></name><name><surname>Dvir</surname><given-names>Dov</given-names></name><name><surname>Levy</surname><given-names>Ofer</given-names></name><name><surname>Maltz</surname><given-names>AlanC</given-names></name></person-group><article-title>Project Success: A Multidimensional Strategic Concept</article-title><source>Long Range Planning</source><year>2001-dec</year><fpage>699</fpage><lpage>725</lpage><pub-id pub-id-type="doi">10.1016/s0024-6301(01)00097-8</pub-id></element-citation></ref><ref id="R17"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Spector</surname><given-names>Paul</given-names></name></person-group><article-title>Summated Rating Scale Construction</article-title><year>1992</year><pub-id pub-id-type="doi">10.4135/9781412986038</pub-id></element-citation></ref><ref id="R18"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Sposito</surname><given-names>VA</given-names></name><name><surname>Hand</surname><given-names>ML</given-names></name><name><surname>Skarpness</surname><given-names>Bradley</given-names></name></person-group><article-title>On the efficiency of using the sample kurtosis in selecting optimal lpestimators</article-title><source>Communications in Statistics - Simulation and Computation</source><year>1983-jan</year><fpage>265</fpage><lpage>272</lpage><pub-id pub-id-type="doi">10.1080/03610918308812318</pub-id></element-citation></ref><ref id="R19"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Swartz</surname><given-names>StephenM</given-names></name></person-group><article-title>Managerial perceptions of project stability</article-title><source>Project Management Journal</source><year>2008-nov</year><fpage>17</fpage><lpage>32</lpage><pub-id pub-id-type="doi">10.1002/pmj.20078</pub-id></element-citation></ref><ref id="R20"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Tashakkori</surname><given-names>Abbas</given-names></name><name><surname>Creswell</surname><given-names>JohnW</given-names></name></person-group><article-title>Editorial: The New Era of Mixed Methods</article-title><source>Journal of Mixed Methods Research</source><year>2007-jan</year><fpage>3</fpage><lpage>7</lpage><pub-id pub-id-type="doi">10.1177/2345678906293042</pub-id></element-citation></ref><ref id="R21"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Waldrop</surname><given-names>MMitchell</given-names></name><name><surname>Stein</surname><given-names>Daniel</given-names></name></person-group><article-title>Complexity: The Emerging Science at the Edge of Order and Chaos</article-title><source>Physics Today</source><year>1992-dec</year><fpage>83</fpage><lpage>83</lpage><pub-id pub-id-type="doi">10.1063/1.2809917</pub-id></element-citation></ref><ref id="R22"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Wateridge</surname><given-names>John</given-names></name></person-group><article-title>How can IS/IT projects be measured for success?</article-title><source>International Journal of Project Management</source><year>1998-feb</year><fpage>59</fpage><lpage>63</lpage><pub-id pub-id-type="doi">10.1016/s0263-7863(97)00022-7</pub-id></element-citation></ref></ref-list>
  </back>
</article>
