Academic journal article Informatica Economica

Study on Risk Approaches in Software Development Projects

Academic journal article Informatica Economica

Study on Risk Approaches in Software Development Projects

Article excerpt

Risk approaches in project development led to the integration in the IT project management methodologies and software development of activities and processes of risk management. The diversity and the advanced level of the used technologies in IT projects with increasing complexity leads to an exponential diversification of risk factors.The purpose of this research is to identify the level of the risk approach in IT projects both at the IT project management and software development methodologies level and the level of the perception of IT project managers, IT managers and IT analysts in Romanian IT companies. Thus, we want to determine the correlation between the use of a project management or software development methodology and the overall level of risk perceived by the project managers using these methodologies.

Keywords: Risk, Software Development, IT Projects, Project Management, Methodologies

1 Introduction

With the increasing level of complexity of IT projects for software development, associated risks have increased. This has generated increasing interest in the risk approach both in terms of research, and that of professional standards for IT project management and software development.

In recent researches, we noticed the relationship between risk and IT project performance, and the relationship between risk and performance of IT project management [1]; [2]; [3]; [4]; [5]; [6].

The diversity and the advanced level of the used technologies in IT projects with increasing complexity leads to an exponential diversification of risk factors. The recent IT approaches of complex projects such as Smart Cities are quite eloquent in this context [7].

Focusing on risk is more than just a formal act. This focus is required in ensuring the performance of software development projects. The relationship between risk and performance of software development projects is positive [6];[8].

In this context, focusing on performance requires mandatory use of risk management methods in the management of IT projects. Risk factors are represented by any element or condition that can negatively or positively affect the project throughout its life cycle, but especially the final outcome of the project.

IT projects risks have many shapes, making it difficult to measure, and are divided into several dimensions: users, requirements, complexity of project, planning and control, project team, organizational environment [1]; [2]; [9]; [10]; [11].

Risk management is an iterative process of risk identification, analysis and risk assessment, risk response planning, monitoring and control of risk response and is conducted throughout the project life cycle [11].

Practical experience indicates that the use of a formal and structured process for handling expected or unexpected risk events minimizes unpredictable events, costs, delays, stress or misunderstandings. In the last decade [12], standards for project management have become comparable on structure and content.

Analyzing each methodology, we can observe how the risks are approached in IT projects. Thus, PMBOK (Project Management Body of Knowledge) is known as a standard methodology in project management and it is developed by PMI. In this methodology, the risk approach occurs within "Risk management" domain applied in the planning and control of the project [13].

The risk approach in the CMMI framework (Capability Maturity Model Integration)focuses on improving processes that provide essential elements of effective processes to the organizations [14]. CMMI addresses risks in the level 3 of maturity ("Defined").

RUP (Rational Unified Process)[15] is a customizable methodology framework project, which is primarily focused on software development.

From large projects to condensed projects, RUP enables organizations to develop projects quickly and to provide high quality modeling according to specific requirements. Also, it addresses processes by focusing on risks that processes are exposed to in software development [16]. …

Search by... Author
Show... All Results Primary Sources Peer-reviewed

Oops!

An unknown error has occurred. Please click the button below to reload the page. If the problem persists, please try again in a little while.