Sustainable Risk Management in IT Enterprises

Abstract

A synthesis of literature studies covering the determinants of agile project management methods, risk management processes as well as factors influencing the shaping of project success and failure clearly indicates that in most publications on risk in agile managed projects, the human factor is heavily underestimated at the expense of often excessive favoring of procedures. Meanwhile, after analyzing the risk factors that arise in agile-managed IT projects, it became apparent that in addition to aspects such as technology, hardware, system, or even project schedule and cost, the project team is highlighted, which is also the second concept with the GPM P5 Standard for Sustainability in Project Management. Thus, the purpose of this article is to develop a model for risk management in IT projects. As a result of the empirical research carried out by means of an expert interview (108 experts) and a questionnaire survey (123 respondents), a risk management model was developed and six original risk management areas were identified, describing 73.92% of all risk factors that may occur during the implementation of an IT project. Furthermore, empirical studies confirm that basic processes such as risk factor identification, impact assessment, and key risk factor management are used by managers and/or team leaders during the implementation of IT projects.

A Systematic Review of Risk Management Tools and Techniques in Software Projects

“…Identify Risk [22] Root Cause of the Problems [23] Learning Cycle [24] Periodic Risk Reporting [22] Periodic risk status reporting…”

“…In addition, a number of studies have reviewed, screened, and determined a collection of risk variables that significantly influence each project goal by using rank-ordering techniques of risk [21], [23], [25]- [27], [29]. To analyze the data, Shrivastava [25] used the Kendall Concordance test, a statistical tool that allows quantification of consensus among responses with regard to the effect of each risk factor on project objectives.…”

Risks associated with the development process of in-house information system projects

“…Traditional project management methods, such as the waterfall method, and the Project Management Body of Knowledge focus on large projects and involve considerable documentation, standardization, and numerous planning and control processes; thus, they lack flexibility and agility for handling changes in management [28], [29]. Agile project management is characterized by frequent feedback loops and iterative reviews; thus, agile risk management emphasizes human factors, including communication, participation, and collaboration among stakeholders interested in the project, as well as the control of relevant resources [19], [30], [31]. Consequently, risk management is a crucial part of the software development process.…”

“…According to several authors [1], [9], [24], [27], in an IS project, users' requirements and the organization's strategic goals should be aligned with the developed technology applications and systems, which enables business needs to be supported while maximizing performance and minimizing risks. In in-house projects, business needs are met through the development of application systems, whose feasibility is examined through post-implementation reviews [7], [8], [30].…”

“…The project manager may be focused on task-, structure-, and actor-related risks in the analysis phase [1], [7]- [9], [13], [18], [26], [30].…”