Systematic Review of Risks in Domestic and Global IT Projects

2022 ◽  
pp. 1612-1634
Author(s):  
Franciane Freitas Silveira ◽  
Rosária de F. S. Macri Russo ◽  
Irapuan Glória Júnior ◽  
Roberto Sbragia

The development of information technology projects is no longer limited to the domestic sphere. This study identifies the differentiation of risk categories between global and domestic projects through an exploratory research carried out by means of a systematic literature review. 1367 risks were identified in 37 articles and classified within 22 categories. The major concern regarded in domestic project management was the client (external risk) and scope (internal risk) and, in global project management, the psychic distance (external) and coordination and control (internal). The main difference between the risk categories for each project type refers to the psychic distance category, which was identified almost exclusively in global projects, thus making the external risks more relevant than those in domestic projects. On the other hand, it makes risks such as client, supplier and stakeholders be underestimated. The results indicate that project managers should focus on different risks depending on the type of IT project: global or domestic.

2018 ◽  
Vol 26 (1) ◽  
pp. 20-40
Author(s):  
Franciane Freitas Silveira ◽  
Rosária de F. S. Macri Russo ◽  
Irapuan Glória Júnior ◽  
Roberto Sbragia

The development of information technology projects is no longer limited to the domestic sphere. This study identifies the differentiation of risk categories between global and domestic projects through an exploratory research carried out by means of a systematic literature review. 1367 risks were identified in 37 articles and classified within 22 categories. The major concern regarded in domestic project management was the client (external risk) and scope (internal risk) and, in global project management, the psychic distance (external) and coordination and control (internal). The main difference between the risk categories for each project type refers to the psychic distance category, which was identified almost exclusively in global projects, thus making the external risks more relevant than those in domestic projects. On the other hand, it makes risks such as client, supplier and stakeholders be underestimated. The results indicate that project managers should focus on different risks depending on the type of IT project: global or domestic.


Author(s):  
Rosaria de F. S. M. Russo ◽  
Franciane F. Silveira

The aim of this chapter is to identifier the differentiation of risk between global and local projects through exploratory research carried out using a systematic literature review. One thousand seven hundred twenty-five risks were identified in 46 articles published in the last 20 years and classified within 22 categories. The major concern regarded in local project management was the client (external risk) and scope (internal risk) and, in global project management, the psychic distance (external) and coordination and control (internal). The main difference between the risk categories for each project type refers to the psychic distance category, which was identified almost exclusively in global projects, thus making the external risks more relevant than those in local projects. On the other hand, it allows some risks, such as supplier and stakeholder, to be underestimated. The results indicate that project managers should focus on different risks depending on the type of IT project: global or local.


Author(s):  
Mira Thoumy ◽  
Joelle Moubarak

This article aims at identifying the predictive effect of Project Manager's assignment on multiple project management effectiveness in the case of information technology projects in the Lebanese banks. The multiple project management effectiveness was measured on 3 different levels: organizational, projects success and project manager. A survey-based analysis was conducted on a random sample of 43 project managers working in 19 different Lebanese commercial banks. The results showed that most of the project manager's assignment factors influence positively the multiple project effectiveness with some exceptions.


2006 ◽  
Vol 10 (01) ◽  
pp. 77-101
Author(s):  
Ahmed Nawaz Tariq ◽  
Arif Iqbal Rana

This case is about a major expansion and upgradation project undertaken at a refinery in Northern Pakistan in the 1990s. The project was the biggest expansion project since the company's inception in the 1920s. The project was carried out by a Japanese contractor, and was marked by changes in CEO's and Project Managers. Despite the vicissitudes in relationships between the construction team and company management, the project was completed in time and within budget. The case looks at project management from the client's perspective. It can be used in a module on Project Termination, or Project Monitoring and Control in a course on Project Management). The case highlights the importance of project planning, and monitoring; the management of inter-personal relationships; and 'post-mortem' analysis and learning from projects.


2009 ◽  
Vol 40 (3) ◽  
pp. 72-81 ◽  
Author(s):  
Elmar Kutsch ◽  
Mark Hall

The management of risk is considered a key discipline by the Project Management Institute and the Association for Project Management. However, knowledge of what needs to be done frequently fails to result in action consistent with that knowledge. The reasons for this seem to have received little attention. This study researched the degree of use of project risk management and barriers that prevent IT project managers from using risk management. Interviews and a survey were carried out. The results show that, in one-third of cases, because of the problem of cost justification, no formal project risk management process was applied.


2017 ◽  
Vol 19 (1) ◽  
Author(s):  
Songezo Nkukwana ◽  
Nicky H.D. Terblanche

Background: To address the low success rate in information system (IS) projects, organisations in South Africa are adopting agile implementation methodologies. Agile delivery environments advocate an iterative approach where autonomous, self-organising teams share project management (PM) activities. This encroaches on the traditional project manager role. Are project managers still relevant in agile delivery environments and how should they adapt?Objectives: This case study investigated how project managers could adapt to agile IS implementation environments to remain relevant. Specifically, the views of their key stakeholders (the management and implementation teams) were elicited to provide insights into what is expected from agile project managers.Method: A qualitative, inductive content analysis approach using purposive sampling was used to identify 13 participants (comprising management and implementation team members) within a large South African insurance company. Semi-structured interviews were conducted with all participants.Results: The management and implementation teams agreed that PM remains highly relevant in an agile environment for ensuring project governance including delivery, risk management, reporting and budgeting. There was, however, disagreement between the management and implementation teams on project management interaction with the implementation team. Management preferred a command and control type project manager, while the implementation team favoured a more inclusive, facilitative PM style.Conclusion: To remain viable in an agile IS project implementation environment within large corporates, project managers need to be aware of what various stakeholders expect of them. They need to retain some of the classic PM functions while adapting to the interpersonal and collaborative requirements of the agile way.


2016 ◽  
pp. 2375-2394
Author(s):  
Kirsi Liikamaa ◽  
Tero Vartiainen ◽  
Maritta Pirhonen ◽  
Heli Aramo-Immonen

According to anecdotal evidence, project managers working on information technology (IT) projects are occasionally replaced, although the literature on information systems (IS) and project management (PM) makes little mention of it. With a view to narrowing this knowledge gap the authors examined the reasons behind the practice. The authors took an interpretive approach to the data gathering and analysis, and collected descriptions about replacing project managers (RPM) from interviews and questionnaires (n=43). The concept of contradiction served as a lens through which to identify the underlying reasons. Contradiction refers to statements asserting or expressing the opposite of another statement. The authors identified four contradictions explaining why RPM occurs in IT projects. These contradictions show that RPM appears to be a simplistic solution when there are more fundamental issues to consider. The implications extend to education, practice, and research in the context of IT project management.


SIGMA TEKNIKA ◽  
2019 ◽  
Vol 2 (1) ◽  
pp. 14
Author(s):  
Hery Irwan

Project management in the length of time of completion or better known as lead time is the time that has been agreed between the project implementers in this project managers and customers as the owner of the project. Time-based project implementers will make planning, scheduling and control of existing resources with the purpose of the length of the project in accordance with the agreed upon. In the process constraints will always occur which cause the delay activities that become part of the overall project. The delay that occurs on the critical path if not controlling and acceleration would cause backwards in time from the time of completion of the project. This will cause losses for both the executor fines for the delay as well as for the project owner to lose an opportunity of reception of the project late from agreements. This paper contains the possibility of doing a program crash or the acceleration by means of melaukukan overlapping. For sure the acceleration by means of overlapping could not immediately be implemented in all activities of the project. The decision to do overlapping largely determined by the knowledge and experience of the person in charge of the project.  Keywords: Crash program, overlapping, critical path method.


2018 ◽  
Vol 7 (4.20) ◽  
pp. 307
Author(s):  
Mohammed Neamah Ahmed ◽  
Sawsan Rasheed Mohammed

In project management there has been a shift from traditional project management to the Agile Project Management (APM) style. The proposed Agile Quality Management Framework in Construction Projects will be built as a sequence of procedure that deals with a project from primary vision of project to the final delivery of project, will trace alignment and discover a contact between Agile and Traditional Project Management (TPM) concepts and find contact points among two of the more used Agile frameworks (scrum) and one of the more confirmed Project Management framework (PMBOK®) processes. This will result in a recognition of comparable areas between scrum and PMBOK® processes. Agile quality Management Framework is a new agile framework that covers the whole project lifecycle. The goal of the framework is to assist the project managers to adapt a more flexible approach to managing and implementing the construction project. The findings arrive that the agile project management using the Scrum methodology profits effectiveness procedures and a lower duration of process, ensuring value of quality planning and control inputs.   


2020 ◽  
Vol 12 (3) ◽  
pp. 225-242
Author(s):  
João Varajão ◽  
Gabriela Fernandes ◽  
Hélio Silva

Purpose The purpose of this paper is to increase the understanding of practice in information systems (IS) project management (PM) by analyzing the use of tools and techniques by IS project managers. Design/methodology/approach The authors carried out an international questionnaire-based survey with experienced IS project managers. Findings Results reveal that, notwithstanding the similarities between the tools and techniques used in IS projects and projects from other areas, there are also significant differences concerning those more frequently used. The top five tools and techniques most used are “kick-off meeting,” “progress meetings,” “progress reports,” “requirements analysis” and “activity list.” However, the low use of some tools and techniques, from management areas such as risk and quality management, or related to the project monitoring and control, should raise concern. Research limitations/implications Through the results of this research, researchers, organizations and practitioners can identify ways of developing and enhancing PM by examining the tools and techniques identified as the most used and those that are not being used as frequently as expected. Originality/value It provides a useful benchmarking basis for evaluating the most applicable tools and techniques, designing training and teaching programs and identifying academic research opportunities in IS PM.


Sign in / Sign up

Export Citation Format

Share Document