Identification of Risk Factors in Implementation of IT Projects in Pakistan

Authors

  • Hussain Ali Comsats Institute of Information Technology Abbottabad

DOI:

https://doi.org/10.11634/216796061706627

Keywords:

Regression analysis, Correlation, Durbin Watson test, Miscommunication, Project Complexity, Conflicts, Project Implementation.

Abstract

The focus of this work is to identify factors such as planning, change in specification, miscommunication, stakeholder, top management, conflicts, project team,  complexity of project, culture and leadership that disturb the effectiveness of the IT project implementation Pakistan. The article presents the individual factor’s negative impact on the successful completion and implementation of the project. A survey has been conducted to check the reliability of variables percentage and frequency distribution for that purposeregression analysis, correlation and Durbin Watson test which check the long run relation and association among variables. The findings reveal overall positive and significant relationship and impact of these factors for effective software development and other IT project. The study provides new insights into the IT projects, as very limited research has been conducted in Pakistan with respect to identification of factors that significantly influence IT industry.  

References

AKeshlaf, A., & Hashim, K. (2000). A model and prototype tool to man-age software risks. In:,, pp. 297 –305. Proceedings of First Asia Pacific Conference on Quality Software, (pp. 297-305).

Akgün, A. E., Lynn, G. S., Keskin, H., & Dogan, D. (2014). Team learning in IT implementation projects: Antecedents and consequences. International Journal of Information Management , 37– 47.

Aloini, D., Dulmin, R., & Mininno, V. (2012). Modeliing and assessing ERP project risks: a Petri Net approach. European Journal of Operational Research, 484-495.

Bahrami, M., Bazzaz, D. H., & Sajjadi, S. M. (2012). Innovation and Improvements In Project Implementation and . Procedia - Social and Behavioral Sciences, 418 – 425 .

Bakker, K. d., Boonstra, A., & Wortmann, H. (2010). Does risk management contribute to IT project success? A meta-analysis of empirical evidence. International Journal of Project Management , 493–503.

Bannerman, P. L. (2008). Risk and risk management in software projects: A reassessment. The Journal of Systems and Software, 2118-2133.

Bannerman, P. L. (2008). Risk and risk management in software projects: A reassessment. The Journal of Systems and Software , 2118–2133.

Barki, H., Rivard, S., & Talbot, J. (1993). Toward an assessment of software development risk. Journal of Management Information SystemS, 203-225.

Baškarada, S., y, T. m., & na, T. m. (n.d.). Technology deployment process model.

Boehm, & B, W. (1991). Software risk management principles and prac-tices. IEEE Software, 32-41.

Dey, P. K. (2001). Decision support system for risk management: a case study. Management Decision, 634-649.

Elkington, P., & Smallman, C. (2000). Managing project risks: a case study from the utilities sector. International Journal of Project Management, 49-57.

Fan, C.-F., & Yu, Y.-C. (2004). BBN-based software project risk management. The Journal of Systems and Software , 193–203.

Hakim, A., & Hakim, H. (2010). A practical model on controlling the ERP implementation risks. Information Systems, 204–214.

Higuera, R. P., Gluch, D. P., Dorofe, A. J., Murphy, R. L., & Walker, J. A. (1994). An introduction to team risk management. Software Engineering Institute.

Holzmann, V., & Spiegler, I. (2011). Developing risk breakdown structure for information technology. International Journal of Project Management , 537–546.

Hung, Y. W., Hsu, S.-C., Su, Z.-Y., & Huang, H.-H. (2014). Countering user risk in information system development projects. International Journal of Information Management , 533–545.

Irani, Z., & PED, L. (2002). Developing a frame of reference for exante IT/IS investment evaluation. European Journal of Information Systems , 74–82.

Jaafari, A. (2001). Management of risks, uncertainties and opportunities on projects:time for a fundamental shift. International Journal of Project Management, 89±101.

Jones, C. (1998). Minimizing the risks of software development. Cutter IT journal, 13-21.

Kemerer, C. F., & Sosa, G. L. (1991). Systems development risks in strategic information systems. Information and Software Technology, 212–223.

Kutsch, E., & M Hal, ,. (. (2008). Deliberate ignorance in project risk management. International Journal of Project Management , 245–255.

Kwak, Y, H., & W, I. C. (2000). Calculating project management ’s return on investment. Project Management Journal, 38–47.

Kwak, Y., & Stoddard, J. (2004). Project risk management: lessons learned from software:lessons learned from software. Technovation, 915–920.

Law, C. C., & Ngai, E. W. (2007). ERP systems adoption: An exploratory study of the. Information & Management, 418–432.

Lipovetsky, S., Tishler, A., Dvir, D., & Shenhar, A. (1997). The relative importance of project success dimensions. R&D Management , 97 –106.

Liu, S., & Wang, L. (2014). Understanding the impact of risks on performance in internal and outsourced information technology projects: The role of strategic importance. International Journal of Project Management.

Lopez, C., & Salmeron, J. L. (2014). Dynamic risks modelling in ERP maintenance projects with FCM. Information Sciences, 25–45.

MHuang, S., Chag, I. C., HanLi, S., & Lin, M. T. ( 2004). Assessing risk in ERP projects: identify and prioritize the factors. Industrial Management & Data Systems Volume, 681–88.

Nieto-Morote, A., & Ruz-Vila, F. (2011). A fuzzy approach to construction project risk assessment. International jouranal project management, 220-231.

Oh, Y., Suh, E.-h., Hong, J., & Hwang, H. (2009). A feasibility test model for new telecom service development using MCDM method:A case study of video telephone service in Korea. Expert Systems with Applications , 6375–6388.

Ramos, P., & Mota, C. (2014). Perceptions of success and failure factors in information technology projects: a study from Brazilian companies. Procedia - Social and Behavioral Sciences, 349 – 357.

Raz, T., & Michael, E. (1999). Use and bene®ts of tools for project risk management. International Journal of Project Management , 9-17.

Sarigiannnidis, L., & Chatzoglou, D. P. ( 2014). Quality vs risk: An investigation of their relationship in software development projects. International Journal of Project Management , 1073-1082.

Stewart, R. A. (2008). A framework for the life cycle management of information:Project IT. International Journal of Project Management , 203–212.

V, K., B, M., & U, K. (2002). Enterprise resource systems adopting process: a survey of Canadian organizations. International Journal of Production Research, 209-523.

Ward, S. C. (1999). Assessing and managing important. International Journal of Project Management, 331-336.

Whitney, K. M., & MEM, C. B. (2013). The Root Cause of Failure in Complex IT Projects: Complexity Itself . Procedia Computer Science, 325 – 330 .

Xiao, N., Huang, H.-Z., Li, Y., He, L., & Jin, T. (2011). Multiple failure modes analysis and weighted risk priority numberevaluation in FMEA. Engineering Failure Analysis , 1162–1170.

Zwikael, O., Pathak, R. D., Singh, G., & Ahmed, S. (2014). The moderating effect of risk on the relationship. International Journal of Project Management , 435 – 441.

Downloads

Published

12/24/2016

How to Cite

Ali, H. (2016). Identification of Risk Factors in Implementation of IT Projects in Pakistan. American Journal of Business and Management, 5(4), 150–151. https://doi.org/10.11634/216796061706627

Issue

Vol. 5 No. 4 (2016)

Section

Articles

License

Copyrights for articles published in AJBM are retained by the authors, with first publication rights granted to the journal. The journal/publisher is not responsible for subsequent uses of the work. It is the author's responsibility to bring an infringement action if so desired by the author.