Presenting a model for measuring agility in software companies based on agile principles

Dissertation for Master degree in Computer Engineering (M.Sc)

Software Orientation

Abstract

The use of agile methods in software development instead of traditional methods has been expanding for some time. These methods, which have been presented as a reaction to the inherent problems of traditional methods, have promised the realization of new goals and values. Unlike traditional methods, these methods try to build an agile software development process in the organization, so that both the customer and the organization are satisfied with the results. Due to their focus on people and not processes, full compliance with agile methods is not possible in the short term and requires appropriate time. Therefore, the more agility an organization can provide, the more agility values ??it can provide for itself and its customers. Considering the need for agility measurement tools, in this research, it has been tried to provide an agility measurement model that can calculate the agility level in software organizations based on globally acceptable criteria. Although the quantitative measurement of a qualitative value may not have the necessary accuracy, it can be used as a measure to improve and promote agility in the organization. In this research, instead of focusing on agile methods, agile exercises are considered as the foundation of the measurement model. In this way, the designed model is independent of development methods and can be used in all companies, even companies that have only used a part of agile methods. Keywords: agile modeling, agile organizational architecture, agile methods, agile modeling. For 60 years, software companies have been using traditional methods to produce their software products. During this period, it is a good opportunity to properly codify these development methods and provide developers with a suitable standard for software development. Since the beginning of the new century and simultaneously with the increasing development of the Internet and the web, as well as the widespread use of software packages, the traditional problems of software development methods have shown themselves more than ever. The delay in the delivery of software packages, the possibility of no change in customer requirements, and ultimately customer dissatisfaction are the things that hinder the development of software using traditional methods. The emergence of new development methods, which require new mechanisms in the development environment, was considered as a solution to the aforementioned problems. The new methods, which are called agile development methods, try to give appropriate agility to software manufacturing companies by providing new development processes.

1-2 statement of the basic research problem in general

Today, agile methods in software development (Agile methodologies) are being replaced by traditional software development methods (Traditional methodologies) [1]. Agile methods, which are a kind of reaction to traditional methods, follow different values ??compared to traditional methods [2].  One of the issues that software companies and organizations face frequently in the process of changing their methods from traditional to agile is measuring the amount of agility they have achieved at each point in time. The point here is that this change is not a sudden process and sometimes it takes more than a year and sometimes it is accompanied by many difficulties [3]. This shows the need for a measurement tool. Unfortunately, there is still no measurement tool that has a good agreement on it. A suitable measurement criterion should be in a way that, while having a proper scientific support, it also has simplicity and can be easily used by companies and organizations (even small organizations). Using agile principles as a standard on which there is a general agreement can be helpful in this direction [4]. Based on this, the agile values ??that have been proposed in the agile statement [2] and its addendum should be considered as a measure for organizational agility. But certainly, agile values ??and principles are not very suitable to be judged in a practical environment. Because each of the agile methods such as Scrum (Scrum) [5] or XP (XP) [6] or other methods have specific activities, roles and features that cannot be compared with other methods.  As a better suggestion, it is to use agile exercises as the primary core of the measurement tool.In fact, based on the implementation of these exercises in the organization and the amount of exercises that are being used in an institutionalized way in the organization, the agility of the organization can be estimated. This criterion is the basis of the desired measurement of this research. 1-3 Necessity of Research Many companies that are changing their software development methods from traditional methods to agile methods, need to check their progress in agile at different times. This issue can both help to investigate the potential of attainable values ??in the organization and can be useful in increasing efficiency and organizational benefits by creating a positive atmosphere resulting from the progress of the agility process in the team spirit of people. Having a tool that can show the level of agility based on a scientific research can be of great interest to these companies. Also, this tool can be a basis for determining the future processes that can be chosen to make the organization agile. In this way, in addition to the discussion of measurement, it will also be a suitable guide for the process of changing the organization's behavior.

1-4 Innovation

What makes this research innovative in its own way is to present an agility measurement model whose main task is to show the amount of agility that the organization has achieved so far. Also, in an additional step, it can show exercises that have not yet been institutionalized in the organization with their impact on the organization's agility.

Such a model can be used as a guide for software companies to become more agile. Perhaps it can be used as an auxiliary tool in the process of becoming agile in software companies.

1-5 goals

At the end of this project, a simple tool for measuring agility will be prepared in the form of an application or website. In this website, organizations should answer the questions they are asked about agile practices. Based on these answers, the level of agility of the organization is shown.

Organizations or companies producing software can test their growth in achieving agility goals with the help of this tool. This tool is suitable both for companies that want to use agile methods and for those who are using some aspects of agility.

1-6 Research Hypotheses

The following are assumed in this research:

This research will not discuss the adaptation of agile methodologies to organizations and software projects.

Due to the need to provide an acceptable model. In general, only the documents and documents that are of interest to software companies in the framework of agile methods are considered.

This research is independent of the methodology. In this way, all organizations and software companies that use one or more agile software development methods in all or part of their projects will be able to take advantage of the research results. The importance of using the right research method is to the extent that it can strongly affect the research results. It is for this reason that in all research studies, in order to clarify and create a proper understanding of the research results, before starting the research operation, the method and steps of conducting the research will be clearly stated.

Development of the structure of the measurement model

Implementation of the tool

6-

Chapter Two: Review of the literature and research background

2-1 Introduction

The speed of life has increased a lot compared to the past. Computers are becoming faster and more powerful than before every day, and people are always connected to computer networks through cables, modems, mobile phones, and other electronic devices. Everything is changing and change has become an integral part of people's electronic life. In the meantime, software engineering, as a supplier of processes necessary for digital life, is required to grow rapidly and not fall behind the unbridled train of technology growth.

Software engineering must produce processes that not only respond to changes but also welcome them.