<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.3 20210610//EN" "https://jats.nlm.nih.gov/publishing/1.3/JATS-journalpublishing1-3.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:mml="http://www.w3.org/1998/Math/MathML" article-type="research-article" dtd-version="1.3" xml:lang="en">
<front>
<journal-meta>
  <journal-id journal-id-type="publisher-id">46</journal-id>
  <journal-id journal-id-type="short-title">gssr</journal-id>
  <journal-id journal-id-type="doi">10.31703/gssr</journal-id>
  <journal-title-group>
    <journal-title>Global Social Sciences Review</journal-title>
    <abbrev-journal-title abbrev-type="publisher">gssr</abbrev-journal-title>
  </journal-title-group>
  <issn publication-format="print">2520-0348</issn>
  <issn publication-format="electronic">2616-793X</issn>
  <self-uri xlink:href="https://gssrjournal.com"/>
  <publisher>
    <publisher-name>Humanity Publications</publisher-name>
    <publisher-loc>Pakistan</publisher-loc>
  </publisher>
</journal-meta>
<article-meta>
  <article-id pub-id-type="publisher-id">390647</article-id>
  <article-id pub-id-type="doi">10.31703/gssr.2019(IV-I).29</article-id>
  <article-id pub-id-type="other" specific-use="submission-id">1116</article-id>
  <article-version article-version-type="publisher">1.0</article-version>
  <article-categories>
    <subj-group subj-group-type="heading">
      <subject>article</subject>
    </subj-group>
  </article-categories>
  <title-group>
    <article-title xml:lang="en">Project Planning, Project Success and Project Risk</article-title>
  </title-group>
<contrib-group>
  <contrib contrib-type="author" seq="1" corresp="yes">
    <name>
      <surname>Khan</surname>
      <given-names>Shahwali</given-names>
    </name>
    <role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Conceptualization" vocab-term-identifier="https://credit.niso.org/contributor-roles/conceptualization/">Conceptualization</role>
    <role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Writing – original draft" vocab-term-identifier="https://credit.niso.org/contributor-roles/writing-original-draft/">Writing – original draft</role>
    <xref ref-type="aff" rid="aff1"/>
    <xref ref-type="corresp" rid="cor1"/>
  </contrib>
  <contrib contrib-type="author" seq="2">
    <name>
      <surname>Saher</surname>
      <given-names>Najmul</given-names>
    </name>
    <role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Writing – review &amp; editing" vocab-term-identifier="https://credit.niso.org/contributor-roles/writing-review-editing/">Writing – review &amp; editing</role>
    <xref ref-type="aff" rid="aff2"/>
  </contrib>
  <contrib contrib-type="author" seq="3">
    <name>
      <surname>Yunis</surname>
      <given-names>Mohammad Sohail</given-names>
    </name>
    <role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Writing – review &amp; editing" vocab-term-identifier="https://credit.niso.org/contributor-roles/writing-review-editing/">Writing – review &amp; editing</role>
    <xref ref-type="aff" rid="aff1"/>
  </contrib>
  <aff id="aff1">
    <label>1</label>
    <institution-wrap>
      <institution>Institute of Management Sciences, Peshawar</institution>
    </institution-wrap>
    <named-content content-type="author-role">Assistant Professor</named-content>
    <addr-line>Kp</addr-line>
    <country>Pakistan</country>
  </aff>
  <aff id="aff2">
    <label>2</label>
    <institution-wrap>
      <institution>MS Project Management, Institute of Management Sciences, Peshawar</institution>
    </institution-wrap>
    <addr-line>Kp</addr-line>
    <country>Pakistan</country>
  </aff>
</contrib-group>
<author-notes>
  <corresp id="cor1">Corresponding Author: Shahwali Khan, Assistant Professor, Institute of Management Sciences, Peshawar, Kp, Pakistan.. Contact: 0</corresp>
<fn fn-type="COI-statement" id="fn-coi">
  <p>The authors declare that they have no conflicts of interest.</p>
</fn>
<fn fn-type="ethics-statement" id="fn-ethics">
  <p>This study did not require formal ethics approval.</p>
</fn>
<fn fn-type="data-availability-statement" id="fn-data">
  <p>Data sharing is not applicable to this article.</p>
</fn>
</author-notes>
<pub-date pub-type="epub" date-type="pub" publication-format="electronic">
  <day>31</day>
  <month>03</month>
  <year>2019</year>
</pub-date>
<pub-date pub-type="collection">
  <month>03</month>
  <year>2019</year>
</pub-date>
<pub-date date-type="pub" publication-format="print">
  <day>16</day>
  <month>02</month>
  <year>2022</year>
</pub-date>
  <volume>4</volume>
  <issue>1</issue>
  <season>Winter</season>
  <fpage>219</fpage>
  <lpage>225</lpage>
  <history>
    <date date-type="accepted">
      <day>16</day>
      <month>02</month>
      <year>2022</year>
    </date>
  </history>
<funding-group>
  <funding-statement>
<p>The authors received no specific funding for this work.</p>
  </funding-statement>
</funding-group>
<permissions>
  <copyright-year>2019</copyright-year>
  <copyright-holder>Humanity Publications</copyright-holder>
  <license license-type="open-access" xml:lang="en" xlink:href="https://creativecommons.org/licenses/by/4.0/">
    <license-p>This is an open access article distributed under the terms of the Creative Commons Attribution 4.0 International License.</license-p>
  </license>
</permissions>
<self-uri content-type="text/html" xlink:href="https://gssrjournal.com/article/Project-Planning,-Project-Success-and-Project-Risk"/>
<self-uri content-type="pdf" xlink:href="https://gssrjournal.com/pdf/gssr/OlhA9nlEjF.pdf"/>
<supplementary-material id="suppl-pdf" content-type="pdf" xlink:href="https://gssrjournal.com/pdf/gssr/OlhA9nlEjF.pdf">
  <label>PDF</label>
  <caption>
    <title>Full Text PDF</title>
  </caption>
</supplementary-material>
  <abstract>
    <p>We are investigating the relation of project planning with project success and introduce project risk as a moderator. We examines how different dimensions (organizational, people, technical and technology, project management, economic and stakeholder) of project risk determine this relationship. A survey is carried out from information technology professionals from 20 registered firms in Khyber Pakhtunkhwa Information Technology Board (KPITB). We find that overall project risk has significant moderation impact on the relation of project planning with project success. Information technology (IT) professionals of KPITB plan risk related project management. Technical, technological and economic aspects are detailed and insights on how other risk factors affect project success in IT sector include in the study. Our research highlights the significance of planning in the presence of risk.</p>
  </abstract>
<kwd-group kwd-group-type="author-keywords">
  <kwd>Project Planning</kwd>
  <kwd>Project Risk</kwd>
  <kwd>Project Success</kwd>
  <kwd>Information Technology Projects</kwd>
  <kwd>Risk Factors</kwd>
  <kwd>Moderation</kwd>
  <kwd>MODMED (PROCESS Procedure)</kwd>
</kwd-group>
  <custom-meta-group>
    <custom-meta><meta-name>views</meta-name><meta-value>3310</meta-value></custom-meta>
    <custom-meta><meta-name>downloads</meta-name><meta-value>9</meta-value></custom-meta>
    <custom-meta><meta-name>html-views</meta-name><meta-value>0</meta-value></custom-meta>
    <custom-meta><meta-name>google-scholar-citations</meta-name><meta-value>0</meta-value></custom-meta>
    <custom-meta><meta-name>crossref-citations</meta-name><meta-value>0</meta-value></custom-meta>
  </custom-meta-group>
</article-meta>
</front>
<body>
<sec id="sec-1">
  <title>Introduction</title>
<p>Project planning is an important component of project management and a key characteristic for the success of any project (Andersen, 1996; Carbone &amp; Tippett, 2004). Many  studies identify project planning as an important variable contributing towards the success of projects (Pinto &amp; Slevin, 1987;Dov Dvir, Tishler, Lipovetsky, Shenhar, &amp; Tishler, 2003;Thomas &amp; Fernández, 2008;Serrador &amp; Turner, 2015). On the contrary, some authors undermine the role of planning and claim that project planning is not correlated with project success (see e.g., Andersen 1996; Mintzberg,1994; Dor Dvir &amp; Lechler, 2004).</p><p>The initiation stage of a project is of utmost importance (King, 1988; Meyer, Tertzakian, &amp; Utterback, 1995). Project planning is equally important for information technology sector (Aladwani, 2002). The Standish Group (1994, 1996, 1998, 2000, 2004, 2006 and 2008) reveals that IT projects are in chaos and synonym to failure. Other international groups like Coverdale Organization and Oxford University (UK) report that these projects fail due many reasons. For instance, “lack of planning, undefined goals and objectives, changing objectives during the project, unrealistic time and estimates, lack of executive support and user involvement, failure to communicate as a team and inappropriate skills” (Taimour, 2005 p.4). Talet, Mat-zin, and Houari (2014) argue that it is important to improve the management of projects because many of these are facing issues like poor performance, delays and are over budget.</p><p>The failure of projects in IT sector is also observed in Pakistan. The Ministry of Science and Information Technology reported that out of every 10 projects 4 fail, which is a huge loss to the economy. During last two decades, IT industry in Pakistan is growing hastily and statistics shows that many of IT projects fail before completion (e.g., Butt, Rafiq, Aslam, Ahmed, &amp; Ayyub, 2014; Ali &amp; Naseem, 2016;Abbas, Faiz, Anam, &amp; Ander, 2017; Butt, 2017). IT projects are in chaos and they fail mainly  due to lack of planning (Whittaker, 1999; Zwikael, Pathak, Singh, &amp; Ahmed, 2014; Ahimbisibwe, Tusiime, &amp; Tumuhairwe, 2015). Datta and Mukherjee (2001) argue that the completion of successful projects is dependent upon earlier detection of risks, i.e., external and immediate project risks. Risk adversely affect project success of IT projects (Jiang, J. Klein, &amp; Ellis, 2002).</p><p>Literature shows that planning of a project is affected by the dimensions of risk, whether it is predicted vulnerability or unanticipated vulnerability (Zwikael &amp; Sadeh, 2007; Zwikael et al., 2014).</p><p>Therefore, risk is introduced as a moderator since it is considered a critical moderator in the success of projects (Zwikael &amp; Ahn, 2011). Six risk factors are adopted based on prior studies (Mcfarlan, 1981; Bohem, 1991; Sumner, 1999:2000; Nasir &amp; Sahibuddin, 2011; Talet et al., 2014; Neves, Borgman, &amp; Heier, 2016; Ali &amp; Naseem, 2016). These factors are related to organizational, people, technical and technology, project management, economical and stakeholder.</p>
</sec>
<sec id="sec-2">
  <title>Research Questions</title>
<p>We primarily examine the relation of project planning with project success.  The importance of plans and planning in the success of projects has been studied in different sectors (e.g., Armstrong, 1982; Meyer &amp; Utterback, 1995; Dor Dvir &amp; Lechler, 2004; Serrador &amp; Turner, 2015). Mixed results in literature on the significance of planning in project success, justifies further examination of this relationship. Therefore, we ask research question 1</p><p><break/></p><p>RQ1: Does project planning effect project success?</p><p>Survey has been conducted through questionnaire from randomly selected IT firms. The results show that planning does impact the success of projects in IT sector. Ineffective planning also leads to failure of projects. Therefore, other factors must be considered that may contribute towards the success of a project (Aladwani, 2002). The interaction between planning and risk factors and their moderation effect on success has not been examined in detail in prior studies, hence, we ask research question 2:</p><p><break/></p><p>RQ2: Does project risk moderate  the relation of project planning with project success?</p><p>Results show all risk factors to be statistically significant and risk as a moderator effects the relation of project planning with project success. Organizations involved in IT projects do not need to avoid risk rather its identification and early management is necessary (Aloini, Dulmin, &amp; Mininno, 2007). The findings are expected to help IT firms minimize project risks and have an efficient and effective work plan for the completion of their projects. No such study has been conducted in Peshawar (at least not in authors’ knowledge) and findings are generalizable to other parts of the country as well. This paper can help in creating a road map for policy makers of Directorate of Science and Technology for multiple mega projects e.g., Pakistan Digital city, Haripur and KP-CERC.</p><p>The remaining scheme of the paper includes literature review and hypotheses in section 3. Section 4 presents methodology. Section 5 includes data analysis whereas, section 6 is conclusion.</p>
</sec>
<sec id="sec-3">
  <title>Literature Review and Hypotheses</title>
<p>IT projects have been the equivalent of failure in the course of the most recent four decades (Al-Ahmad et al., 2009). Therefore managing IT projects is the main concern of IT professionals (Whittaker, 1999). The challenging task for a project manager is to forecast precisely at the early stage, i.e., planning for the future risks and the tasks necessary for achieving project success (Raz, Shenhar, &amp; Dvir, 2002). Few authors have underplayed the role of project planning (see e.g., Bart, 1993; Andersen, 1996). Ample and apt planning is essential before starting any IT project (Aladwani, 2002). There are mix results on the significance of planning. The hypothesis H1 assumes:</p><p><break/></p><p>Hypothesis 1 (H1): Project planning is positively related to project success</p><p>Planning may not be the only reason of project success but there are other factors responsible for project to be successful. Managing risk proficiently is a key element for project success (Carbone &amp; Tippett, 2004). Information technology projects are risky in nature but it is difficult to identify those risks (Boehm &amp; DeMarco, 1997). Risk management is believed to be the best practice for the success of IT projects (Baccarini, Salm, &amp; Love, 2004). Though it is difficult to completely mitigate risk, yet IT project managers should allocate resources for risk management as risk is thought to be important arbitrator for the success of projects (Chapman &amp; Ward, 2004). The next hypothesis claims:</p><p><break/></p><p>Hypothesis 2 (H2): Project risk will moderate the relation of planning with project success</p><p>Numerous studies have been done to examine failure in IT projects (Al-Ahmad et al., 2009). For managing risk, it is important to identify specific risk factors responsible for failure of IT projects (Aloini et al., 2007). Various risk factors have been investigated, e.g., poor project planning, organizational i.e., structure, unclear goals, scope and objectives, miscommunication, inappropriate resource planning, management and leadership, monitoring and evaluation, poor methodology, stakeholder involvement and training, technical and technology planning, inability to adapt, inexperience project managers, superficial environment for employees; and risks not managed. These different factors have been homogenized and grouped into six categories, i.e., Organizational, People, Project management, Technical and Technology, Economic and Stakeholder. Each risk factor is further classified into different proxies to measure risk occurrence and impact.</p><p>Following hypotheses suggest that each risk proxy moderates the relation of project planning with project success.</p><p>Hypothesis 2a (H2a): Organizational will moderate the relationship of planning with project success</p><p>Hypothesis 2b (H2b): People will moderate the relationship of planning with project success.</p><p>Hypothesis 2c (H2c): Project management will moderate the relationship of planning with project success.</p><p>Hypothesis 2d (H2d): Technical and technology will moderate the relationship of planning with project success.</p><p>Hypothesis 2e (H2e): Economic will moderate the relationship of planning with project success.</p><p>Hypothesis 2f (H2f): Stakeholder will moderate the relationship of planning with project success.</p>
</sec>
<sec id="sec-4">
  <title>Methodology</title>
<p>The paper is quantitative in nature and utilizes deduction approach with a positivism paradigm. A positivist study generally depends upon quantifiable examination that leads to numerical and statistical analysis (Collins, 2010). Crotty (1998) and other authors (e.g., Yin, 2003) have preferred survey methodology for such studies.</p><p>We investigate the relation of project planning with project success and include risk as moderating factor. The success of projects in IT sector is considered by the project team members including project managers and project coordinators (Nguyen, Nguyen, &amp; Cao, 2016). The sample is randomly selected from KPITB i.e., IT park Peshawar. The target population is IT project teams, therefore, the scope is limited to the project team comprising of project managers, project coordinators, project team lead, and software engineers.</p><p><break/></p><p>Data Collection Instrument</p><p>The questionnaire was devised with questions on a 5 point likert scale related to independent variables project planning; moderating variable project risk and dependent variable project success. Data was collected through simple random sampling from 44 projects of 20 IT firms and 220 questionnaires were distributed, out of which 200 were received and analysed.</p><p>The Cronbach alpha (0.92) is estimated to test the reliability the questionnaire. To test the moderating variable, the “simple linear moderation” model 1 has been adopted from Hayes (2013).</p><p>Project success Yi = i1 + b1 Planning + b2 Project risk + b3 Interaction</p>
</sec>
<sec id="sec-5">
  <title>Data Analysis</title>
<p>Table 1 present the descriptive
statistics and the means, standard deviation and data spread show that the data
is normal. The data is analyzed through regression analysis for testing
hypothesis 1. The results are shown in Table 2, the independent variable, i.e.,
project planning has a positive coefficient and indicates a highly significant positive
relationship with project success.</p><p>To
test hypothesis 2, 2a, 2b, 2c, 2d, 2e and 2f moderation analysis (MODMED) is
used. Table 3 and 4 represent these analyses. The overall project risk (moderator) significantly moderates the relationship
of project planning with project success. The p-value is highly significant,
which shows the prevalence of risk in IT sector and the success of projects is
affected due to the existence of risk proxies. Later, the individual moderation
analysis is conducted for each risk proxy. Results indicate that these risk
factors do moderate the relationship of project planning with project success
and the interaction term of planning with individual risk proxies is
statistically significant. Hence, it is evident from the results of
moderation analysis that each risk proxy has an influence on the association of
project planning with project success i.e., it can increase or decrease the
strength of relationship as explained by Hayes (2013).</p><p><bold>Table 1. </bold>Descriptive
Statistics</p><p>Descriptive statistics for the sample
of twenty IT firms with data of forty-four projects (where n=200).</p><table-wrap id="table1"><label>Table 1</label><caption><title>Table 1</title></caption><table><tbody><tr><td>  </td><td> <p><bold>N</bold></p> </td><td> <p><bold>Min</bold></p> </td><td> <p><bold>Max</bold></p> </td><td> <p><bold>Mean</bold></p> </td><td> <p><bold>Std.
  Dev</bold></p> </td></tr><tr><td> <p>PPL</p> </td><td> <p>200</p> </td><td> <p>1.04</p> </td><td> <p>4.70</p> </td><td> <p>3.1</p> </td><td> <p>.94</p> </td></tr><tr><td> <p>PR
  (Likelihood)</p>    </td><td> <p>200</p> </td><td> <p>1.46</p> </td><td> <p>4.31</p> </td><td> <p>2.8</p> </td><td> <p>.61</p> </td></tr><tr><td> <p>PR
  (Impact)</p> </td><td> <p>200</p> </td><td> <p>1.58</p> </td><td> <p>4.50</p> </td><td> <p>3.1</p> </td><td> <p>.65</p> </td></tr><tr><td> <p>Overall
  Risk</p> </td><td> <p>200</p> </td><td> <p>2.13</p> </td><td> <p>4.40</p> </td><td> <p>3.0</p> </td><td> <p>.50</p> </td></tr><tr><td> <p>PS</p> </td><td> <p>200</p> </td><td> <p>1.00</p> </td><td> <p>6.00</p> </td><td> <p>2.7</p> </td><td> <p>.81</p> </td></tr><tr><td> <p>OR</p> </td><td> <p>200</p> </td><td> <p>1.00</p> </td><td> <p>4.70</p> </td><td> <p>2.8</p> </td><td> <p>.82</p> </td></tr><tr><td> <p>PL</p> </td><td> <p>200</p> </td><td> <p>1.50</p> </td><td> <p>4.50</p> </td><td> <p>2.9</p> </td><td> <p>.75</p> </td></tr><tr><td> <p>PM</p> </td><td> <p>200</p> </td><td> <p>2.00</p> </td><td> <p>4.50</p> </td><td> <p>3.1</p> </td><td> <p>.76</p> </td></tr><tr><td> <p>TTR</p> </td><td> <p>200</p> </td><td> <p>1.20</p> </td><td> <p>4.70</p> </td><td> <p>3.1</p> </td><td> <p>.75</p> </td></tr><tr><td> <p>ER</p> </td><td> <p>200</p> </td><td> <p>1.00</p> </td><td> <p>4.50</p> </td><td> <p>3.0</p> </td><td> <p>.77</p> </td></tr><tr><td> <p>SR</p> </td><td> <p>200</p> </td><td> <p>1.00</p> </td><td> <p>5.00</p> </td><td> <p>2.9</p> </td><td> <p>.89</p> </td></tr></tbody></table></table-wrap><p>PPL denotes project planning; PR denotes
project risk; while likelihood represents the prevalence of those risk factors
and impact represents the influence of those risk factors; Overall risk is the
total amount of project risk i.e., likelihood and impact; PS denotes the
project success; OR denotes the organizational risk factor; PL denotes the risk
related to people; PM denotes the risk related to project management; TTR
denotes the technical and technology risk factor; ER denotes the economic risk
factor and SR denotes the stakeholder (user) risk factor.</p><p><bold>Table 2. </bold>Regression Analysis</p><p>The
association of project planning with project success</p><table-wrap id="table2"><label>Table 2</label><caption><title>Table 2</title></caption><table><tbody><tr><td valign="top"> <p><bold>Independent
  variable</bold></p>  </td><td valign="top"> <p><bold>Beta
  value</bold></p> </td><td valign="top"> <p><bold>Dependent
  variable</bold></p> </td><td valign="top"> <p><bold>F-statistics
  (sig)</bold></p> </td><td valign="top"> <p><bold>R<sup>2</sup></bold></p> </td><td valign="top"> <p><bold>Adjusted
  r<sup>2</sup></bold></p> </td><td valign="top"> <p><bold>Df</bold></p> </td><td valign="top"> <p><bold>F
  value</bold></p> </td></tr><tr><td valign="top"> <p><bold>PPL</bold></p>  </td><td valign="top"> <p>.404</p> </td><td valign="top"> <p>PS</p> </td><td valign="top"> <p>.000</p> </td><td valign="top"> <p>.163</p> </td><td valign="top"> <p>.159</p> </td><td valign="top"> <p>1,198</p> </td><td valign="top"> <p>38.53</p> </td></tr></tbody></table></table-wrap><p>*, **, *** denote p &lt;0.10, p &lt;0.05 and p &lt;0.01
respectively.</p><p>Where PPL denotes project planning for
IT projects and PS denotes project success of IT projects.</p><p>Table 2 reports coefficients of the
following regression model.</p><p>PS <italic>j </italic>= <italic>i</italic><sub>1</sub>
+ <italic>b </italic>PPL <italic>j </italic>+ <italic>ej</italic></p><p><bold>Table 3. </bold>Moderation
Analysis</p><p>The
moderation effects of overall project risk on the association of project
planning with project success utilizing bootstrap</p><table-wrap id="table3"><label>Table 3</label><caption><title>Table 3</title></caption><table><tbody><tr><td> <p><bold>Model</bold></p> </td><td> <p><bold>Planning
  coefficient (<italic>b</italic>)</bold></p> </td><td> <p><bold>Moderator
  coefficient</bold></p> </td><td> <p><bold>Interaction
  coefficient</bold></p> </td><td> <p><bold>F</bold></p> </td></tr><tr><td> <p>Overall project risk</p> <p>R<sup>2</sup> = .282<sup>**</sup></p> <p>R<sup>2</sup> change = .030</p>  </td><td>  <p>.42<sup>*</sup></p> <p>4.5</p>  </td><td>  <p>.59<sup>**</sup></p> <p>3.9</p> </td><td>   <p>.41<sup>***</sup></p>  </td><td>  <p>21.43<sup>**</sup></p> <p>8.85<sup>**</sup></p> </td></tr></tbody></table></table-wrap><p>Table
3 reports coefficients of the following regression/moderation models.</p><p>PS<italic><sub>i</sub></italic>
= <italic>i</italic><sub>1</sub> + <italic>b</italic><sub>1</sub> PPL + <italic>b</italic><sub>2 </sub>PR + <italic>b<sub>3 </sub></italic>PPL*PR</p><p><bold>Table 4. </bold>Moderation Analysis</p><p>The moderation effects of risk proxies on the
relationship of project planning with project success using bootstrap.</p> <table-wrap id="table4"><label>Table 4</label><caption><title>Table 4</title></caption><table><tbody><tr><td> <p><bold>Model</bold></p> </td><td> <p><bold>Planning
  coefficient (<italic>b</italic>)</bold></p> </td><td> <p><bold>Moderator
  coefficient</bold></p> </td><td> <p><bold>Interaction
  coefficient</bold></p> </td><td> <p><bold>F</bold></p> </td></tr><tr><td> <p>Organizational</p> <p>R<sup>2</sup> = .223<sup>**</sup></p> <p>R<sup>2</sup> change = .031</p> </td><td> <p>.45<sup>*</sup></p> <p>4.1</p> </td><td> <p>.33<sup>**</sup></p> <p>2.7</p> </td><td> <p>.23<sup>***</sup></p> </td><td>  <p>17.11<sup>**</sup></p> <p>7.40<sup>**</sup></p> </td></tr><tr><td> <p>People</p> <p>R<sup>2</sup> = .234<sup>**</sup></p> <p>R<sup>2</sup> change = .013</p> </td><td> <p>.50<sup>**</sup></p> <p>5.0</p> </td><td> <p>.44<sup>**</sup></p> <p>3.0</p> </td><td> <p>.29</p> </td><td>  <p>19.23<sup>**</sup></p> <p>3.42<sup>**</sup></p> </td></tr><tr><td> <p>Project management</p> <p>R<sup>2</sup> = .293<sup>**</sup></p> <p>R<sup>2</sup> change = .029</p> </td><td>  <p>.41<sup>**</sup></p> <p>4.2</p>  </td><td>  <p>.52<sup>**</sup></p> <p>3.8</p> </td><td>  <p>.41<sup>**</sup></p> </td><td>  <p>20.29<sup>**</sup></p> <p>6.61<sup>**</sup></p> </td></tr><tr><td> <p>Technical and technology</p> <p>R<sup>2</sup> = .261<sup>**</sup></p> <p>R<sup>2</sup> change = .031</p> </td><td>  <p>.52<sup>**</sup></p> <p>5.8</p>  </td><td>  <p>.24<sup>**</sup></p> <p>1.9</p> </td><td>  <p>.43<sup>***</sup></p> </td><td>  <p>18.28<sup>**</sup></p> <p>7.61<sup>**</sup></p> </td></tr><tr><td> <p>Economic</p> <p>R<sup>2</sup> = .260<sup>**</sup></p> <p>R<sup>2</sup> change = .097</p> </td><td>  <p>.49<sup>**</sup></p> <p>6.3</p> </td><td>  <p>-.10</p> <p>-.86</p> </td><td>  <p>.63<sup>***</sup></p> </td><td>  <p>18.17<sup>**</sup></p> <p>18.58<sup>**</sup></p> </td></tr><tr><td> <p>Stakeholder</p> <p>R<sup>2</sup> = .217<sup>**</sup></p> <p>R<sup>2</sup> change = .026</p> </td><td>  <p>.55<sup>**</sup></p> <p>5.9</p> </td><td>  <p>.11</p> <p>1.2</p> </td><td>  <p>.19<sup>**</sup></p> </td><td>  <p>13.50<sup>**</sup></p> <p>5.54<sup>**</sup></p>   </td></tr></tbody></table></table-wrap> <p>Table
4 reports coefficients of the following regression/moderation models.</p><p>PS<italic><sub>i</sub></italic>
= <italic>i</italic><sub>1</sub> + <italic>b</italic><sub>1</sub> PPL + <italic>b</italic><sub>2 </sub>OR + <italic>b<sub>3 </sub></italic>PPL*OR</p><p>PS<italic><sub>i</sub></italic>
= <italic>i</italic><sub>1</sub> + <italic>b</italic><sub>1</sub> PPL + <italic>b</italic><sub>2 </sub>PL+ <italic>b<sub>3 </sub></italic>PPL*PL</p><p>PS<italic><sub>i</sub></italic>
= <italic>i</italic><sub>1</sub> + <italic>b</italic><sub>1</sub> PPL + <italic>b</italic><sub>2</sub> PM + <italic>b<sub>3 </sub></italic>PPL*PM</p><p>PS<italic><sub>i</sub></italic>
= <italic>i</italic><sub>1</sub> + <italic>b</italic><sub>1</sub> PPL + <italic>b</italic><sub>2 </sub>TTR+ <italic>b<sub>3 </sub></italic>PPL*TTR</p><p>PS<italic><sub>i</sub></italic>
= <italic>i</italic><sub>1</sub> + <italic>b</italic><sub>1</sub> PPL + <italic>b</italic><sub>2 </sub>ER + <italic>b<sub>3 </sub></italic>PPL*ER</p><p>PS<italic><sub>i</sub></italic>
= <italic>i</italic><sub>1</sub> + <italic>b</italic><sub>1</sub> PPL + <italic>b</italic><sub>2 </sub>SSR + <italic>b<sub>3 </sub></italic>PPL*SSR</p>
</sec>
<sec id="sec-6">
  <title>Conclusion</title>
<p>The association of project planning with project success differs for every project. It can be argued that there are many factors that affect this association. Many studies have added new risk factors that affect the project success or failure. Relevant risk factors were identified in the literature and then analyzed. Risk is considered to influence the relationship of project planning with project success but research documents conflicting views about it. The IT projects of Pakistan have not been examined much, so it is essential to study this relationship for better understanding. The paper shows that there is a positive impact of project planning on project success. Focus of the paper is to help the IT firms of Peshawar by identifying the significance of risk (organizational, technical, people, project management, stakeholder, economic) and its impact on the relationship of project planning with project success. Principally, project planning is primarily related to the success of a project and overall project risk significantly moderates this relationship. The successful completion of a project depends on planning and risk calculation play a vital role in the achievement. This empirical study gathers information on risk factors from 44 IT projects and the outcomes indicate that the significance of planning is dependent upon project risk the success is measured accordingly.</p><p>The framework of this paper will help IT professionals to measure success of IT projects considering planning as an important phase through analyzing different risk proxies. In order to improve their project planning, firms at IT Park Peshawar are highly encouraged to develop strategies on the basis of this study. The paper has important implications for IT professionals of KPITB by focusing and improving the project planning; properly identify strategy for the upcoming risk on time. In light of this paper if they improve these elements, ultimately project success can be ensured to a great extent and the skills of project manager for managing the project effectively at every stage of the project as well. Proper project planning aids in dealing with the challenges of project success. Therefore, this particular examination adds towards knowing the effectiveness associated with planning of project about project achievement with different risk configurations for progress IT projects. The final results of this exploration add to an even more intense knowledge of the achievable way to deal with IT project risk management. Findings of this paper will help policy makers, e.g., Ministry of Science and Technology.</p>
</sec>
</body>
<back>
<fn-group content-type="conflict-of-interest">
  <title>Conflict of Interest</title>
  <fn fn-type="conflict">
<p>The authors declare that they have no conflicts of interest.</p>
  </fn>
</fn-group>
<fn-group content-type="ethics-statement">
  <title>Ethics Statement</title>
  <fn fn-type="ethics">
<p>This study did not require formal ethics approval.</p>
  </fn>
</fn-group>
<fn-group content-type="data-availability">
  <title>Data Availability</title>
  <fn fn-type="data-availability-statement">
<p>Data sharing is not applicable to this article.</p>
  </fn>
</fn-group>
<app-group>
  <app id="app-suppl">
    <title>Supplementary Materials</title>
<supplementary-material id="suppl-pdf" content-type="pdf" xlink:href="https://gssrjournal.com/pdf/gssr/OlhA9nlEjF.pdf">
  <label>PDF</label>
  <caption>
    <title>Full Text PDF</title>
  </caption>
</supplementary-material>
  </app>
</app-group>
<ref-list>
  <title>References</title>
<ref id="Abbas">
  <label>1</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Abbas, A., Faiz, A., Anam, F., &amp; Ander, A</person-group>
    <year>2017</year>
    <article-title>. Reasons for the Failure of Government IT Projects in Pakistan : A Contemporary Study</article-title>
    <source>In International Conference on Service Systems and Service Management. Dalian, China: IEEE</source>
    <page-range>rojects</page-range>
    Abbas, A., Faiz, A., Anam, F., &amp; Ander, A. (2017). Reasons for the Failure of Government IT Projects in Pakistan : A Contemporary Study. In International Conference on Service Systems and Service Management. Dalian, China: IEEE.
  </mixed-citation>
</ref>
<ref id="Ahimbisibwe">
  <label>2</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Ahimbisibwe, A., Tusiime, W., &amp; Tumuhairwe, R</person-group>
    <year>2015</year>
    <article-title>. The Moderating Influence of Inherent Project Risk on the Relationship between Project Planning and Perceived Project Success</article-title>
    <source>International Journal of Supply Chain Management</source>
    <volume>4</volume>
    <issue>3</issue>
    <fpage>69</fpage>
    <lpage>77</lpage>
    Ahimbisibwe, A., Tusiime, W., &amp; Tumuhairwe, R. (2015). The Moderating Influence of Inherent Project Risk on the Relationship between Project Planning and Perceived Project Success. International Journal of Supply Chain Management, 4(3), 69-77.
  </mixed-citation>
</ref>
<ref id="AlAhmad">
  <label>3</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Al-Ahmad, W., Al-Fagih, K., Khanfar, K., Alsamara, K., Abuleil, S., &amp; Abu-Salem, H</person-group>
    <year>2009</year>
    <article-title>. A Taxonomy of an IT Project Failure : Root Causes</article-title>
    <source>International Management Review</source>
    <volume>5</volume>
    <issue>1</issue>
    <fpage>93</fpage>
    <lpage>104</lpage>
    Al-Ahmad, W., Al-Fagih, K., Khanfar, K., Alsamara, K., Abuleil, S., &amp; Abu-Salem, H. (2009). A Taxonomy of an IT Project Failure : Root Causes. International Management Review, 5(1), 93-104. https://doi.org/10.1016/S0263-7863 (98)00047-7
    <pub-id pub-id-type="doi">10.1016/S0263-7863</pub-id>
    <ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1016/S0263-7863">10.1016/S0263-7863</ext-link>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1016/S0263-7863(98)00047-7">https://doi.org/10.1016/S0263-7863 (98)00047-7</ext-link>
  </mixed-citation>
</ref>
<ref id="Aladwani">
  <label>4</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Aladwani, A. M</person-group>
    <year>2002</year>
    <article-title>. IT project uncertainty, planning and success: An empirical investigation from Kuwait</article-title>
    <source>Information Technology &amp; People</source>
    <volume>15</volume>
    <issue>3</issue>
    <fpage>210</fpage>
    <lpage>226</lpage>
    Aladwani, A. M. (2002). IT project uncertainty, planning and success: An empirical investigation from Kuwait. Information Technology &amp; People, 15(3), 210-226.
    <pub-id pub-id-type="doi">10.1108/09593840210444755</pub-id>
    <ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1108/09593840210444755">10.1108/09593840210444755</ext-link>
  </mixed-citation>
</ref>
<ref id="Ali">
  <label>5</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Ali, H., &amp; Naseem, I</person-group>
    <year>2016</year>
    <source>Identification of Risk Factors in Implementation of IT Projects in Pakistan</source>
    <volume>5</volume>
    <issue>4</issue>
    <fpage>140</fpage>
    Ali, H., &amp; Naseem, I. (2016). Identification of Risk Factors in Implementation of IT Projects in Pakistan, 5(4), 140- 151.
    <pub-id pub-id-type="doi">10.11634/216796061605627</pub-id>
    <ext-link ext-link-type="doi" xlink:href="https://doi.org/10.11634/216796061605627">10.11634/216796061605627</ext-link>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.11634/216796061605627">https://doi.org/10.11634/216796061605627</ext-link>
  </mixed-citation>
</ref>
<ref id="Aloini">
  <label>6</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Aloini, D., Dulmin, R., &amp; Mininno, V</person-group>
    <year>2007</year>
    <article-title>. Risk management in ERP project introduction: Review of the literature</article-title>
    <source>Information and Management</source>
    <volume>44</volume>
    <issue>6</issue>
    <fpage>547</fpage>
    <lpage>567</lpage>
    Aloini, D., Dulmin, R., &amp; Mininno, V. (2007). Risk management in ERP project introduction: Review of the literature. Information and Management, 44(6), 547-567.
    <pub-id pub-id-type="doi">10.1016/j.im.2007.05.004</pub-id>
    <ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1016/j.im.2007.05.004">10.1016/j.im.2007.05.004</ext-link>
  </mixed-citation>
</ref>
<ref id="Andersen">
  <label>7</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Andersen, E. S</person-group>
    <year>1996</year>
    <source>Warning: activity planning is hazardous to your project&apos;s health! International Journal of Project Management</source>
    <volume>14</volume>
    <issue>2</issue>
    <fpage>89</fpage>
    <lpage>94</lpage>
    Andersen, E. S. (1996). Warning: activity planning is hazardous to your project&apos;s health! International Journal of Project Management, 14(2), 89-94.
    <pub-id pub-id-type="doi">10.1016/0263-7863(95)00056-9</pub-id>
    <ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1016/0263-7863(95)00056-9">10.1016/0263-7863(95)00056-9</ext-link>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1016/0263-7863(95)00056-9">https://doi.org/10 .1016/0263-7863(95)00056-9</ext-link>
  </mixed-citation>
</ref>
<ref id="Armstrong">
  <label>8</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Armstrong, J. S</person-group>
    <year>1982</year>
    <article-title>. The value of formal planning for strategic decisions : review of empirical research</article-title>
    <source>Strategic Management Journal</source>
    <volume>3</volume>
    <issue>3</issue>
    <fpage>197</fpage>
    <lpage>211</lpage>
    Armstrong, J. S. (1982). The value of formal planning for strategic decisions : review of empirical research. Strategic Management Journal, 3(3), 197-211.
  </mixed-citation>
</ref>
<ref id="Baccarini">
  <label>9</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Baccarini, D</person-group>
    <year>1999</year>
    <article-title>. The Logical Framework Method for Defining Project Success</article-title>
    <source>Project Management Journal, Volume</source>
    <page-range>roject</page-range>
    Baccarini, D. (1999). The Logical Framework Method for Defining Project Success. Project Management Journal, Volume 30(Issue 4), 25-32.
    <pub-id pub-id-type="doi">10.1086/250095</pub-id>
    <ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1086/250095">10.1086/250095</ext-link>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1086/250095">https://doi.org/10.1 086/250095</ext-link>
  </mixed-citation>
</ref>
<ref id="Bart">
  <label>11</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Bart, C. K</person-group>
    <year>1993</year>
    <article-title>. Controlling new product R&amp;D projects</article-title>
    <source>R&amp;D Management</source>
    <volume>23</volume>
    <issue>3</issue>
    <fpage>187</fpage>
    <lpage>197</lpage>
    Bart, C. K. (1993). Controlling new product R&amp;D projects. R&amp;D Management, 23(3), 187-197.
    <pub-id pub-id-type="doi">10.1111/J.1467-9310.1993.TB00822.X</pub-id>
    <ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1111/J.1467-9310.1993.TB00822.X">10.1111/J.1467-9310.1993.TB00822.X</ext-link>
  </mixed-citation>
</ref>
<ref id="Boehm">
  <label>12</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Boehm, B. W., &amp; DeMarco, T</person-group>
    <year>1997</year>
    <article-title>. Software risk management</article-title>
    <source>IEEE Software</source>
    <volume>14</volume>
    <issue>3</issue>
    <fpage>17</fpage>
    <lpage>19</lpage>
    Boehm, B. W., &amp; DeMarco, T. (1997). Software risk management. IEEE Software, 14(3), 17-19.
    <pub-id pub-id-type="doi">10.1109/MS.1997.589225</pub-id>
    <ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1109/MS.1997.589225">10.1109/MS.1997.589225</ext-link>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1109/MS.1997.589225">https://doi.org/10.1109/MS.1997.589225</ext-link>
  </mixed-citation>
</ref>
<ref id="Butt">
  <label>13</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Butt, A. S</person-group>
    <year>2017</year>
    <source>Why Information Technology Projects Fail in Pakistan ? International Journal of Advanced Research and Innovative Ideas in Education, (2), 2746-2749</source>
    <page-range>rojects</page-range>
    Butt, A. S. (2017). Why Information Technology Projects Fail in Pakistan ? International Journal of Advanced Research and Innovative Ideas in Education, (2), 2746-2749.
  </mixed-citation>
</ref>
<ref id="Carbone">
  <label>15</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Carbone, T., &amp; Tippett, D</person-group>
    <year>2004</year>
    <article-title>. Project risk management using the project risk FMEA</article-title>
    <source>Engineering Management Journal</source>
    <volume>16</volume>
    <issue>4</issue>
    <fpage>1</fpage>
    <lpage>8</lpage>
    Carbone, T., &amp; Tippett, D. (2004). Project risk management using the project risk FMEA. Engineering Management Journal, 16(4), 1-8.
    <pub-id pub-id-type="doi">10.1080/10429247.2004.11415263</pub-id>
    <ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1080/10429247.2004.11415263">10.1080/10429247.2004.11415263</ext-link>
  </mixed-citation>
</ref>
<ref id="Chapman">
  <label>16</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Chapman, C., &amp; Ward, S</person-group>
    <year>2004</year>
    <article-title>. Why risk efficiency is a key aspect of best practice projects</article-title>
    <source>International Journal of Project Management</source>
    <volume>22</volume>
    <issue>8</issue>
    <fpage>619</fpage>
    <lpage>632</lpage>
    Chapman, C., &amp; Ward, S. (2004). Why risk efficiency is a key aspect of best practice projects. International Journal of Project Management, 22(8), 619-632.
    <pub-id pub-id-type="doi">10.1016/J.IJPROMAN.2004.05.001</pub-id>
    <ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1016/J.IJPROMAN.2004.05.001">10.1016/J.IJPROMAN.2004.05.001</ext-link>
  </mixed-citation>
</ref>
<ref id="Collins">
  <label>17</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Collins, H</person-group>
    <year>2010</year>
    <article-title>. Creative research : the theory and practice of research for the creative industries</article-title>
    <source>AVA Academia. Retrieved from</source>
    <page-range>ractice</page-range>
    Collins, H. (2010). Creative research : the theory and practice of research for the creative industries. AVA Academia. Retrieved from
    <ext-link ext-link-type="uri" xlink:href="https://books.google.com.pk/books/about/Creative_Research.html?id=oyAwg8qSyJYC">https://books.google.com.pk/books/about/Creative_Research.html?id=oyAwg8qSyJYC</ext-link>
  </mixed-citation>
</ref>
<ref id="CookeDavies">
  <label>18</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Cooke-Davies, T</person-group>
    <year>2001</year>
    <source>The</source>
    Cooke-Davies, T. (2001). The
    <pub-id pub-id-type="doi">10.1016/S0263-7863(01)00067-9</pub-id>
    <ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1016/S0263-7863(01)00067-9">10.1016/S0263-7863(01)00067-9</ext-link>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1016/S0263-7863(01)00067-9">https://doi.org/10.1016/S0263-7863(01)00067-9</ext-link>
  </mixed-citation>
</ref>
<ref id="Crotty">
  <label>19</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Crotty, M</person-group>
    <year>1998</year>
    <article-title>. Introduction: the research process</article-title>
    <source>The Foundations of Social Research: Meaning and Perspective in the Research Process, 256</source>
    <page-range>rocess</page-range>
    Crotty, M. (1998). Introduction: the research process. The Foundations of Social Research: Meaning and Perspective in the Research Process, 256.
    <pub-id pub-id-type="doi">10.1017/CBO9781107415324.004</pub-id>
    <ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1017/CBO9781107415324.004">10.1017/CBO9781107415324.004</ext-link>
  </mixed-citation>
</ref>
<ref id="Datta">
  <label>20</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Datta, S., &amp; Mukherjee, S. K</person-group>
    <year>2001</year>
    <article-title>. Risk Management Matrix for Effective Project Planning</article-title>
    <source>Project Management Journal</source>
    <volume>32</volume>
    <issue>2</issue>
    <fpage>45</fpage>
    <lpage>57</lpage>
    Datta, S., &amp; Mukherjee, S. K. (2001). Risk Management Matrix for Effective Project Planning. Project Management Journal, 32(2), 45-57. Retrieved from
    <ext-link ext-link-type="uri" xlink:href="https://www.pmi.org/learning/library/risk-management-matrixeffective-project-planning-5279">https://www.pmi.org/learning/library/risk-management-matrixeffective-project-planning-5279</ext-link>
  </mixed-citation>
</ref>
<ref id="De">
  <label>21</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">De Wit, A</person-group>
    <year>1988</year>
    <article-title>. Measurement of project success</article-title>
    <source>International Journal of Project Management</source>
    <volume>6</volume>
    <issue>3</issue>
    <fpage>164</fpage>
    <lpage>170</lpage>
    De Wit, A. (1988). Measurement of project success. International Journal of Project Management, 6(3), 164-170.
    <pub-id pub-id-type="doi">10.1016/0263-7863(88)90043-9</pub-id>
    <ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1016/0263-7863(88)90043-9">10.1016/0263-7863(88)90043-9</ext-link>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1016/0263-7863(88)90043-9">https://doi.org/10.1016/0263-7863(88)90043-9</ext-link>
  </mixed-citation>
</ref>
<ref id="Dvir">
  <label>22</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Dvir, D., &amp; Lechler, T</person-group>
    <year>2004</year>
    <article-title>. Plans are nothing, changing plan is everything: The impacts of changes on project success</article-title>
    <source>Research Policy</source>
    <volume>33</volume>
    <issue>1</issue>
    <fpage>1</fpage>
    <lpage>15</lpage>
    Dvir, D., &amp; Lechler, T. (2004). Plans are nothing, changing plan is everything: The impacts of changes on project success. Research Policy, 33(1), 1-15.
  </mixed-citation>
</ref>
<ref id="Ika">
  <label>24</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Ika, L. A</person-group>
    <year>2009</year>
    <article-title>. Project Success as a Topic in Project Managment Journals</article-title>
    <source>Project Management Journal</source>
    <volume>40</volume>
    <issue>4</issue>
    <fpage>6</fpage>
    <lpage>19</lpage>
    Ika, L. A. (2009). Project Success as a Topic in Project Managment Journals. Project Management Journal, 40(4),6-19.
    <pub-id pub-id-type="doi">10.1002/pmj</pub-id>
    <ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1002/pmj">10.1002/pmj</ext-link>
  </mixed-citation>
</ref>
<ref id="Jiang">
  <label>25</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Jiang, J., J. Klein, G., &amp; Ellis, T. S</person-group>
    <year>2002</year>
    <article-title>. A Measure of Software Development Risk</article-title>
    <source>Project Management Journal</source>
    <volume>33</volume>
    <issue>3</issue>
    <fpage>30</fpage>
    <lpage>41</lpage>
    Jiang, J., J. Klein, G., &amp; Ellis, T. S. (2002). A Measure of Software Development Risk. Project Management Journal, 33(3), 30-41. Retrieved from
    <ext-link ext-link-type="uri" xlink:href="https://www.pmi.org/learning/library/measure-software-development-risk2019">https://www.pmi.org/learning/library/measure-software-development-risk2019</ext-link>
    <ext-link ext-link-type="uri" xlink:href="https://www.pmi.org/learning/library/measure-software-">https://www.pmi.org/learning/library/measure-software-</ext-link>
  </mixed-citation>
</ref>
<ref id="Mcfarlan">
  <label>26</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Mcfarlan, W. F</person-group>
    <year>1981</year>
    <article-title>. Portfolio Approach to Information Systems | Request PDF</article-title>
    <source>Retrieved February</source>
    <page-range>ortfolio</page-range>
    Mcfarlan, W. F. (1981). Portfolio Approach to Information Systems | Request PDF. Retrieved February 17, 2019, from
    <ext-link ext-link-type="uri" xlink:href="https://www.researchgate.net/publication/243534444_Portfolio_Approach_to_Information_Systems">https://www.researchgate.net/publication/243534444_Portfolio_Approach_to_Information_Systems</ext-link>
  </mixed-citation>
</ref>
<ref id="Meyer">
  <label>27</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Meyer, M. H., Tertzakian, P., &amp; Utterback, J. M</person-group>
    <year>1995</year>
    <source>Metrics for Managing Research and Development</source>
    Meyer, M. H., Tertzakian, P., &amp; Utterback, J. M. (1995). Metrics for Managing Research and Development.
    <pub-id pub-id-type="doi">10.1287/mnsc.43.1.88</pub-id>
    <ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1287/mnsc.43.1.88">10.1287/mnsc.43.1.88</ext-link>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/http://dx.doi.org/10.1287/mnsc.43.1.88">https://doi.org/http://dx.doi.org/10.1287/mnsc.43.1.88</ext-link>
  </mixed-citation>
</ref>
<ref id="Nasir">
  <label>29</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Nasir, M. H. N., &amp; Sahibuddin, S</person-group>
    <year>2011</year>
    <article-title>. Critical success factors for software projects: A comparative study</article-title>
    <source>Scientific Research and Essays</source>
    <volume>6</volume>
    <issue>10</issue>
    <fpage>2174</fpage>
    <lpage>2186</lpage>
    Nasir, M. H. N., &amp; Sahibuddin, S. (2011). Critical success factors for software projects: A comparative study. Scientific Research and Essays, 6(10), 2174-2186.
    <pub-id pub-id-type="doi">10.5897/SRE10.1171</pub-id>
    <ext-link ext-link-type="doi" xlink:href="https://doi.org/10.5897/SRE10.1171">10.5897/SRE10.1171</ext-link>
  </mixed-citation>
</ref>
<ref id="Neves">
  <label>30</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Neves, F. G., Borgman, H., &amp; Heier, H</person-group>
    <year>2016</year>
    <article-title>. Success lies in the eye of the beholder: The mismatch between perceived and real IT project management performance</article-title>
    <source>Proceedings of the Annual Hawaii International Conference on System Sciences, 2016-March(January), 5878-5887</source>
    <page-range>erceived</page-range>
    Neves, F. G., Borgman, H., &amp; Heier, H. (2016). Success lies in the eye of the beholder: The mismatch between perceived and real IT project management performance. Proceedings of the Annual Hawaii International Conference on System Sciences, 2016-March(January), 5878-5887.
    <pub-id pub-id-type="doi">10.1109/HICSS.2016.745</pub-id>
    <ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1109/HICSS.2016.745">10.1109/HICSS.2016.745</ext-link>
  </mixed-citation>
</ref>
<ref id="Nguyen">
  <label>31</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Nguyen, T. D., Nguyen, T. M., &amp; Cao, T. H</person-group>
    <year>2016</year>
    <article-title>. The relationship between IT adoption, IS success and project success</article-title>
    <source>2016 International Conference on Advances in Computing, Communications and Informatics, ICACCI</source>
    <page-range>roject</page-range>
    Nguyen, T. D., Nguyen, T. M., &amp; Cao, T. H. (2016). The relationship between IT adoption, IS success and project success. 2016 International Conference on Advances in Computing, Communications and Informatics, ICACCI 2016, (September), 1192-1198.
    <pub-id pub-id-type="doi">10.1109/ICACCI.2016.7732207</pub-id>
    <ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1109/ICACCI.2016.7732207">10.1109/ICACCI.2016.7732207</ext-link>
  </mixed-citation>
</ref>
<ref id="Pinto">
  <label>32</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Pinto, J. K., &amp; Slevin, D. P</person-group>
    <year>1987</year>
    <article-title>. Critical factors in successful project implementation</article-title>
    <source>IEEE Transactions on Engineering Management, EM-34(1), 22-27</source>
    <volume>34</volume>
    <issue>1</issue>
    <fpage>22</fpage>
    <lpage>27</lpage>
    Pinto, J. K., &amp; Slevin, D. P. (1987). Critical factors in successful project implementation. IEEE Transactions on Engineering Management, EM-34(1), 22-27.
    <pub-id pub-id-type="doi">10.1109/TEM.1987.6498856</pub-id>
    <ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1109/TEM.1987.6498856">10.1109/TEM.1987.6498856</ext-link>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1109/TEM.1987.6498856">https://doi.org/10.1109/TEM.1987.6498856</ext-link>
  </mixed-citation>
</ref>
<ref id="Raz">
  <label>33</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Raz, T., Shenhar, A. J., &amp; Dvir, D</person-group>
    <year>2002</year>
    <article-title>. Risk management, project success, and technological uncertainty</article-title>
    <source>R and D Management</source>
    <volume>32</volume>
    <issue>2</issue>
    <fpage>101</fpage>
    <lpage>109</lpage>
    Raz, T., Shenhar, A. J., &amp; Dvir, D. (2002). Risk management, project success, and technological uncertainty. R and D Management, 32(2), 101-109.
    <pub-id pub-id-type="doi">10.1111/1467-9310.00243</pub-id>
    <ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1111/1467-9310.00243">10.1111/1467-9310.00243</ext-link>
  </mixed-citation>
</ref>
<ref id="Serrador">
  <label>34</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Serrador, P., &amp; Turner, R</person-group>
    <year>2015</year>
    <article-title>. The relationship between project success and project efficiency</article-title>
    <source>Project Management Journal</source>
    <volume>46</volume>
    <issue>1</issue>
    <fpage>30</fpage>
    <lpage>39</lpage>
    Serrador, P., &amp; Turner, R. (2015). The relationship between project success and project efficiency. Project Management Journal, 46(1), 30-39.
    <pub-id pub-id-type="doi">10.1002/pmj.21468</pub-id>
    <ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1002/pmj.21468">10.1002/pmj.21468</ext-link>
  </mixed-citation>
</ref>
<ref id="Taimour">
  <label>35</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Taimour, A. N</person-group>
    <year>2005</year>
    <source>Why IT Projects Fail, 1-8</source>
    <page-range>rojects</page-range>
    Taimour, A. N. (2005). Why IT Projects Fail, 1-8.
  </mixed-citation>
</ref>
<ref id="Thomas">
  <label>36</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Thomas, G., &amp; FernÃ¡ndez, W</person-group>
    <year>2008</year>
    <source>Success in IT projects: A matter of definition? International Journal of Project Management</source>
    <volume>26</volume>
    <issue>7</issue>
    <fpage>733</fpage>
    <lpage>742</lpage>
    Thomas, G., &amp; FernÃ¡ndez, W. (2008). Success in IT projects: A matter of definition? International Journal of Project Management, 26(7), 733-742.
    <pub-id pub-id-type="doi">10.1016/j.ijproman.2008.06.003</pub-id>
    <ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1016/j.ijproman.2008.06.003">10.1016/j.ijproman.2008.06.003</ext-link>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1016/j.ijproman.2008.06.003">https://doi.org/ 10.1016/j.ijproman.2008.06.003</ext-link>
  </mixed-citation>
</ref>
<ref id="Whittaker">
  <label>37</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Whittaker, B</person-group>
    <year>1999</year>
    <article-title>. What went wrong? Unsuccessful information technology projects</article-title>
    <source>Information Management &amp; Computer Security</source>
    <volume>7</volume>
    <issue>1</issue>
    <fpage>23</fpage>
    <lpage>30</lpage>
    Whittaker, B. (1999). What went wrong? Unsuccessful information technology projects. Information Management &amp; Computer Security, 7(1), 23-30.
    <pub-id pub-id-type="doi">10.1108/09685229910255160</pub-id>
    <ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1108/09685229910255160">10.1108/09685229910255160</ext-link>
  </mixed-citation>
</ref>
<ref id="Zwikael">
  <label>38</label>
  <mixed-citation publication-type="journal">
    <person-group person-group-type="author">Zwikael, O., &amp; Ahn, M</person-group>
    <year>2011</year>
    <article-title>. The Effectiveness of Risk Management: An Analysis of Project Risk Planning Across Industries and Countries</article-title>
    <source>Risk Analysis</source>
    <volume>31</volume>
    <issue>1</issue>
    <fpage>25</fpage>
    <lpage>37</lpage>
    Zwikael, O., &amp; Ahn, M. (2011). The Effectiveness of Risk Management: An Analysis of Project Risk Planning Across Industries and Countries. Risk Analysis, 31(1), 25-37.
    <pub-id pub-id-type="doi">10.1111/j.1539-6924.2010.01470.x</pub-id>
    <ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1111/j.1539-6924.2010.01470.x">10.1111/j.1539-6924.2010.01470.x</ext-link>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1111/j.1539-6924.2010.01470.x">https://doi.org/10.1111/j.1539-6924.2010.01470.x</ext-link>
  </mixed-citation>
</ref>
</ref-list>
</back>
</article>