Comparative analysis of agile and traditional methodologies in IT project management

It is known that initially, during software development, the traditional methodology was used for all IT projects and projects were often unsuccessful due to the rapid growth of the IT industry, and then agile methodologies began to be developed. Traditional methods have some advantages over agile methodologies, and mostly the most common traditional methodology is Waterfall. Given that it has limitations in handling problems, such as unstructured code, team morale, poor visibility, lack of communication between stakeholders and frequent prioritization of user requirements, it would not be bad to use agile methodologies, which focus on working with users, continuous testing, refactoring and incremental development. This paper deals with the comparison of methodologies in IT project management based on other scientific research. Some of the mentioned methodologies are Scrum, Kanban, Waterfall, etc. It was concluded that the agile Scrum methodology is mostly used in IT companies, with the combination of several methodologies often appearing, due to the need for projects, in order to eliminate the shortcomings of each methodology

Agile software development in a context of plan-based organizations

Agile software development has increasingly been used in the last fifteen years with the goal of improving traditionally time-consuming and rather non-user friendly process of developing software code. As implications of agile development and its impact on employees are still unclear, it is important to understand the benefits, opportunities and limitations of this development or collaboration mechanism. Thus, empirical evidence with implications for decision makers in the field of corporate policy and software development is an open research field. This master thesis analyzes the potentials of agile software development and how this approach can be used to support the development processes in companies, in terms of efficiency, shorter time-to-market as well as better customer fit of the developed products or services. By exploring some of the key features of different methods and processes, the potentials and limitations of the selected approaches are analyzed and linked to recent literature insights

Agile software development in a context of plan-based organizations

Agile software development has increasingly been used in the last fifteen years with the goal of improving traditionally time-consuming and rather non-user friendly process of developing software code. As implications of agile development and its impact on employees are still unclear, it is important to understand the benefits, opportunities and limitations of this development or collaboration mechanism. Thus, empirical evidence with implications for decision makers in the field of corporate policy and software development is an open research field. This master thesis analyzes the potentials of agile software development and how this approach can be used to support the development processes in companies, in terms of efficiency, shorter time-to-market as well as better customer fit of the developed products or services. By exploring some of the key features of different methods and processes, the potentials and limitations of the selected approaches are analyzed and linked to recent literature insights