Software Development Management Research Articles

Agile work practices: measurement and mechanisms

ABSTRACT Organizations increasingly follow agile management frameworks (e.g., Scrum), to implement practices that aim to enable continuous change. Currently, it is unclear how agile work practices (AWPs) are best conceptualized and measured. The present study draws from the taskwork-teamwork distinction to develop a new theoretical framework and measurement instrument of AWPs. We outline potential mechanisms of AWPs in terms of (a) temporality, (b) managerial control, (c) team processes, and (d) work design. Based on this framework, we validate measures of agile practices with data collected from 269 different teams, including multisource and multiwave data (n = 1664 observations). We first establish the factorial validity, internal consistency, test-retest reliability, and measurement invariance of the instrument. Subsequently, we show that AWPs diverge from centralized bureaucracy and converge with measures of emergent team planning, autonomy, and feedback. The pattern of relationships with variables in the nomological network supports the taskwork-teamwork model. Results of multilevel regression analyses indicate that the use of AWPs is associated with favorable team planning behaviors and enriched work design experiences. By disentangling the AWP concept from software development and popular management frameworks, this study broadens the scope of research on agility.

TINJAUAN SISTEMATIS TERHADAP PERSYARATAN MANAJEMEN PERUBAHAN DALAM PROYEK PENGEMBANGAN PERANGKAT LUNAK

Changes in software development are unavoidable and can occur due to changing needs of users, stakeholders, and the presence of new technologies. Analysis of the impact of changes greatly affects the cost and time of project work that can affect the success of the project. With the analysis, can help reduce the impact caused. Therefore, proper change management in software development projects is required. In this paper we present a review of the need for change management in software development. The writing of this paper is done to answer the problems that arise based on the discussion of the journals studied. The problems include: 1. what are the causes of change management, 2. What is the impact of change? 3. What methods can be used to cope with change? 4. What tools can be used to cope with change? The method used in writing this review is to draw conclusions based on the discussion obtained from the grouping of journals related to change management and the need for change management sourced from ScienceDirect and IEEE. The results obtained from this review are to answer four questions that arise and draw conclusions about the methods and tools that are often used in large case studies in change management. The method that is often used to support the management of requirements change is Requirements Change Management (RCM). RCM consists of 3 stages (1) Understanding changes (2) Analysis of changes and (3) Finalizing changes to this method can be assisted with web tools. The web is often used to support change management needs because it can be used to manage quantitative and qualitative data.
 Keywords: Change Management; Software Development, Requirement Change Management (RCM)

Organizational Construction of Financial Management Application Platform Based on Commercial Random Matrix

As one of the basic tools of statistical analysis, random matrix theory builds a bridge for the study of microscopic and macroscopic properties of complex networks. The eigenvalues of the adjacency matrix of the complex network after mapping correspond to the energy spectrum in the random matrix theory, so the characteristics of the complex network are concentrated in the volatility of the eigenvalue sequence. The eigenvalues of complex networks are analyzed through random matrix theory to find the relationship between their structure and properties. This paper discusses the design and realization of the comprehensive application platform of group enterprise financial management. Based on the current situation of the development of financial management software in domestic and foreign group companies, the thesis gives the goals and tasks of the platform research and design. The enterprise financial management platform has made a business and technical architecture design and has made an in-depth analysis and design of modules such as fund management, budget management, statement management, and accounting management. This paper finds that the critical point threshold makes the results of network community division below this threshold poor, and the results above this threshold are good. Furthermore, the tipping point threshold for the NYSE network is significantly lower than that of the CSM network. This paper further analyzes the dynamic cross-correlation matrix and examines the time-dependent changes in the number of outliers, the number of communities, the degree of network modularity, and the degree of decentralization of industry composition under the condition of two market critical point thresholds. From the magnitude of fluctuation, it is found that the NYSE network is much more stable than the CSM network, which may also be related to the basic characteristics of the two markets, because the capital chain relationship is much more stable than the supply chain relationship.

UML Transformation to Java-based Software Product Lines

Software product line engineering (SPLE) is an emerging approach that enables variability management in software development. SPLE offers tremendous benefits, but lack of tool support becomes a barrier in the adoption of SPLE. Variability modules for Java (VMJ) is an implementation approach that is defined based on the variability modules (VM) concept to support SPLE. VMJ combines Java modules system and design patterns that are commonly used by software developers. VMJ is accompanied by a UML profile, called UML-VM profile, which extends UML notation to model variability in the UML diagram. UML-VM diagram is used to model the problem domain, and VMJ is used in the domain implementation. In this research, we design a model transformation from Unified Modeling Language (UML) diagram into VMJ. The transformation rules are defined based on the UML-VM profile and implemented in the Eclipse Acceleo model to text transformation. As a result, a UML diagram can be transformed automatically into Java-based software product lines. The transformation tool is evaluated using a case study by comparing the generated code and the actual implementation.

Maturity Models for Managing People in Software Development Teams: A Systematic Literature Review

Human factors are fundamental to software development, hence the need to understand people-oriented maturity models in development teams. This article aims to identify the maturity models for people management in software development teams cited in the literature, in order to identify evidence about their use, benefits and limitations, and the human aspects involved. A systematic literature review (SLR) was carried out, where automatic searches were done in four search engines, congresses in the area of ​​human factors within software engineering, in addition to a manual search. Evidence indicates that there are numerous models aimed at developing people in development teams, but few are applied. Models based on observation and informal discussion were found, as well as non-validated models, indicating the scarcity of models applicable to people in software engineering. However, complete but complex models were also found, indicating that a more transparent, dynamic and simple process is needed for people's development. In the observed human factors, emphasis is placed on communication, collaboration, knowledge, learning, self-management, motivation and skills in general. Keywords: Maturity models; Human Factors; Software Development Teams; Teams; People DOI: 10.7176/RHSS/12-14-02 Publication date: July 31 st 2022

A novel risk management model in the Scrum and extreme programming hybrid methodology

<span>Risk management in software development has always been one of the necessities of software project management. The logical nature of software projects and products has caused several challenges and risks in these projects. On the other hand, with the emergence of Agile methodologies, especially Scrum, and extreme programming (XP) methodologies, in recent years, this issue has become more serious. This is mainly because emphasizing limited documentation in these methodologies has caused these methods to pay little attention to some aspects of project management, particularly risk management. Concentrating on this challenge, the current study has proposed a risk management model in the hybrid methodology, combining Scrum and XP. Using this model in a case study shows this model's success in achieving risk management purposes. The results of this study indicate an appropriate reduction in the number of reworks, change requests, identified risks, and occurred risks. Moreover, the number of eliminated risks and team productivity have increased.</span>

A SURVEY REPORT ON PROJECTOMATE

The Agile Development approach to systems development is the new fundamental for developers. Twelve Principles supporting the Agile Manifesto were elaborated in support. Hence the team always has to look towards identifying and proposing appropriate reference disciplines which are manifest in the Agile Development Universe of Discourse. The Manifesto evokes some reference disciplines to support its various aspects. Why is it desirable and necessary to search for such reference disciplines? The answer is Alternative Software Development and Project Management approaches, such as Software Prototyping and Rapid Development and now including Agile Development, all seemed based on pragmatic experience and have been designed mostly by consultants and practitioners. While this is not in any way to denigrate or deprecate them, it is felt that support for these approaches needs to also come from other disciplines, such as management studies, leadership studies, and the like to give Agile Development a more solid theoretical and intellectual basis.

An efficient ANFIS-EEBAT approach to estimate effort of Scrum projects

Software effort estimation is a significant part of software development and project management. The accuracy of effort estimation and scheduling results determines whether a project succeeds or fails. Many studies have focused on improving the accuracy of predicted results, yet accurate estimation of effort has proven to be a challenging task for researchers and practitioners, particularly when it comes to projects that use agile approaches. This work investigates the application of the adaptive neuro-fuzzy inference system (ANFIS) along with the novel Energy-Efficient BAT (EEBAT) technique for effort prediction in the Scrum environment. The proposed ANFIS-EEBAT approach is evaluated using real agile datasets. It provides the best results in all the evaluation criteria used. The proposed approach is also statistically validated using nonparametric tests, and it is found that ANFIS-EEBAT worked best as compared to various state-of-the-art meta-heuristic and machine learning (ML) algorithms such as fireworks, ant lion optimizer (ALO), bat, particle swarm optimization (PSO), and genetic algorithm (GA).

Causal Interactions in Agile Application Development

The Agile approach and tools are popular for the management of Enterprise Application Software (EAS) development. This article focuses on the issue of inconsistency between strategic business objectives and the functionality of the software developed. Agile management tools lack the functionality of EAS project activities coordination. This article aims to rethink Agile project management using the causal modelling approach. A causal model of Agile project management using a management transaction (MT) concept was developed. The notion of the space of processes was used to identify the MTs location along the axes of aggregation, generalization, and time and to formalize their interaction specifications. Taxonomy of the coordination meta-types and types was developed using the identifiers of the MTs. The modified Agile activities hierarchy was developed, and vertical and horizontal causal interactions between Agile activities were identified. This modified Agile management model helps to consistently track the integrity of EAS project content. Complexity indicators were introduced to evaluate the EAS project complexity and their average and normalized values are presented. Additional attributes in the Agile management tool Jira are proposed. Monitoring mismatch between strategic business objectives and development activities content helps to improve the success of EAS projects delivery.

Software Development, Configuration, Monitoring, and Management of Artificial Neural Networks

With the increasing demand for software systems, the software development industry is also developing rapidly. With the development of information technology, the more functions of the software, the more valuable it is, so the function design of the software becomes more complicated and difficult. The design of software system functions is increasingly large and complex. Scientific and effective use of software configuration management can well deal with collaborative work problems such as version management and change control in the software development process. In the process of software development and configuration, there will always be many problems that are difficult to detect. For example, when inputting the program code, there are not always some letter or space errors, and these errors are difficult to detect in time. For this reason, we need to establish a monitoring and management system for software development. As a computing model of human brain neural network, the artificial neural network can play the role of monitoring and management when it is applied to software development and configuration, which provides support for the security and scientificity of software development and configuration systems. This study studies the role and effectiveness of an artificial neural network in the monitoring and management of software development and configuration and validates it through experiments. The experimental results show that the artificial neural network has a strong ability to identify the problems in the software development configuration, which can improve the software development efficiency by at least 20%. It can improve the quality of software development and then improve the life cycle of software.

Deriving the minimum staff number requirement for intelligent staff scheduling: An efficient constructive method and application

AbstractEffective staff scheduling is a critical activity of successful software development management. Due to its difficulty and broad applications in many service delivery scenarios, staff scheduling has been studied for several decades. However, most existing work focus on constructing the working schedules based on a given workforce size. This paper tries to solve a prerequisite issue before performing staff scheduling, i.e., testing whether the already existed manpower can meet the scheduling requirements. Though it is possible to use network flow theory or artificial intelligence (AI) methods like genetic algorithms to solve this problem, their time complexities could be too high to be used for large problem sizes. This paper proposes a constructive method that can derive the minimum staff number for three scheduling problem variants in a linear running time, and in the meantime a corresponding working schedule that can satisfy all the problem constraints can be produced. We not only theoretically show the lower bound for the computation time complexity of our proposed method but also prove its correctness. Moreover, based on the derived minimum staff number, we further explore the genetic algorithm for generating the schedule and compare its performance with our method. The experiments show that our method outperforms the baselines in terms of both effectiveness and efficiency.

Pengembangan Aplikasi Tiga-Tingkat Menggunakan Metode Scrum pada Aplikasi Presensi Karyawan Glints Academy

The rapid development of technology requires a software development management system that can be adaptive in rapidly changing circumstances. Scrum is an agile method that has the advantage of being agile and adaptive. Glints Academy holds an Industry Project Exploration as the program to prepare students for the rapid development of technology and reduce the gap between the education field and industrial field by MBKM program from the Ministry of Education and Culture. This study aims to apply the Scrum method in a heterogeneous developer team and divergent ability backgrounds to build an application with three-level architecture. The developer team is college students who come from different regions spread across Indonesia with full online implementation. Scrum is used because it is advantageous to other methods in a relatively fast-changing environment and also provides good quality control. The sprints were carried out in two sprints with two weeks of development in each sprint. The application built is an employee attendance application with a three-tier architecture: client, server, and data. The client-tier application is a front-end server built using the React.js framework while the server-tier and data-tier are built-in back-end servers with the Node.js and Express.js frameworks. JWT (JSON Web Token) authentication determines access role to functions and resources available on the back-end server. The result is a web application that fulfills the entire product backlog determined by the product owner. The results of this research are this method can used to develop features enhancement in the middle of the application development process without affecting the main feature development and this method is effectively used for different team developer backgrounds and during its online development

Software Process Evaluation from User Perceptions and Log Data

AbstractCompanies often claim to follow specific software development methodologies (SDM) when performing their software development process. These methodologies are often supported by dedicated tools that keep track of work activities carried out by developers. The purpose of this paper is to provide a novel approach that integrates analytical insights from both the perceptions of SDM stakeholders and software development tools logs to provide SDM improvement recommendations. This paper develops a new process improvement approach that combines two significantly different sources of data on the same phenomenon. First, it uses a questionnaire to gather software development stakeholder SDM perceptions (managers and developers). Second, it leverages process mining to analyze software development tools logs to obtain additional information on software development activities. Finally, it develops recommendations based on concurrent analysis of both sources. Our novel process improvement approach is evaluated in three directions: Does the presented approach (RQ1) enable managers to gain additional insights into employees' performance, (RQ2) deliver additional insights into project performance, and (RQ3) enable development of additional SDM improvement recommendations? We find that integrated analysis of software development perception data and software development tools logs opens new possibilities to more precisely identify and improve specific SDM elements. The evaluation of our novel process improvement approach follows a single case study design. Our approach can only be used in enterprises in which software development tools logs are available. The study should be repeated in different cultural settings. We practically show how concurrently analyzing data about developer SDM perceptions and event log data from software development tools enables management to gain additional insights in the software development process regarding the performance of individual developers. The main theoretical contribution of our paper is a novel process improvement approach that effectively integrates data from management and developer perspectives and software development tools logs.

Towards holistic goal centered performance management in software development: lessons from a best practice analysis

There are strong motivating factors for more effective performance measurement practices in software development. Astute practices in this domain are lauded to improve efficiency and effectiveness. However previous studies have shown that measurement in software is intricate, complex and fraught with challenges. Consequently it is poorly managed in practice. Our research seeks to better understand performance management in a real world software development setting in order to identify the challenges and generate a roadmap for improvement. This paper presents findings from an inductive analysis of a radical measurement program in a global software organization. Our study investigates the level at which non-compliance with best practice can explain the company’s disappointing results. We found that a narrow focus on projects, rather than on organizational goals, has seriously hindered its success. We also found that the rate of change in the organization as a whole was impinging on the effective implementation of its measurement program. An analysis of the results demonstrates just how challenging software measurement is. The findings provide an evaluation of best practice relative to the literature that is informed by real industry experience.

Analisis Penerapan Metode Scrum Pada Pengembangan Sistem Informasi Akuntansi Koperasi

Koperasi are one of the drivers of the economy in Indonesia. But in the operations of the koperasi, there are many problems such as lack of information, unrecorded deposits, the amount of credit that exceeds capacity, and lack of accuracy in accounting calculations. The study used the object of the employee koperasi of SWCU (Satya Wacana Christian University) Salatiga by conducting an observation process on the ongoing koperasi business system. The design of a koperasi accounting information system using a web platform with the basic model of the Scrum Process. The Scrum process model is a software development management framework with iterative and incremental characteristics and properties. The koperasi accounting information system that is built based on Scrum can reduce previous processing errors and can increase the speed and accuracy of data processing so that in the short term it can improve koperasi performance. System performance is tested by black box testing method to ensure all features can work properly. The test results showed that the system built can help reducing problems occurred in the operational process of koperasi, particularly in the accounting process. The results show that the system is more efficient to reduce problems occurred in the operational process of koperasi, reduce time in transaction processing, increase accuracy in the accounting process, and make it easier for users to produce reports with high validity.

Development and Validation of Dose Management Software in IVR Utilizing Radiation Information System

In each clinical case, the equipment display dose is used for interventional radiology (IVR) dose management and conform to the Japan diagnostic reference levels 2020 (DRLs 2020). However, dose management software corresponding to the DRLs 2020 using radiation dose structured report (RDSR) is not sufficiently widespread. This study aimed to assess the usefulness of in-house developed dose management software in IVR utilizing radiology information system (RIS), which can record both procedures and lesions. In this study, IVR from July to September 2020 was analyzed (cardiac regions: 141 cases and other regions: 149 cases). The evaluation items were air kerma-area product, air kerma at the patient entrance reference point, and patient information (height, weight, and BMI). Each subject of DRLs 2020 was analyzed by 12 radiological technologists in charge of IVR. The difference between results of the manual analysis and those of the in-house developed dose management software was calculated using paired t-test in terms of analysis time. The analysis time for the cardiac and other regions was 4180.25±1161.79 s and 4366.92±1393.19 s in the manual analysis, and 36.25±15.32 s and 38.08±17.34 s in the software. The use of software indicated a significant reduction in analysis time (p<0.05). The analysis accuracy of the cardiac and other regions was 96.30% and 98.89% in the software. These results show the usefulness of dose management software utilizing RIS.

Development of Dose Management Software Using Visual Basic for Applications and Dose Evaluation in the Field of Nuclear Medicine

The purpose of this study was to develop software for smooth dose management based on the Japan diagnostic reference levels (DRLs 2020) in the field of nuclear medicine. Using the programming language Visual Basic for Applications (VBA), we implemented a function for calculating actual doses, a function for comparing doses at one's own facility with those of DRLs 2020, a function for calculating appropriate doses for pediatric nuclear medicine examinations, and so on. In addition, we evaluated actual doses before and after the software implementation. The software enabled easy calculation of actual doses and comparison with DRLs 2020 for smooth dose management. Furthermore, we were able to use the results of dose evaluation to determine the dosage at our facility and to use them as a reference for optimization. In the field of nuclear medicine, it is possible to manage doses in accordance with DRLs 2020 by introducing own software into our clinical practice.

Development of an application for providing corneal topography reports based on artificial intelligence.

To develop an application (TopEye) in the iOS platform for mobile devices to allow the capture and interpretation of color maps generated by corneal topographers using artificial intelligence. In the execution, follow-up, and assessment of the project, we used the Scrum methodology and interactive and incremental development process for the project management and agile software development. The ge nerated diagnostic pattern bank consists of 1,172 examples of corneal topography, divided into 275 spherical, 302 symmetrical, 295 asymmetrical, and 300 irregular patterns (keratoconus). For the development of the artificial intelligence of the application, network training was established with 240 images of each pattern type, with a total of 960 patterns (81.91%). The remaining 212 images (18.09%) were used to test the application and will be used for the results. The process is semi-automatic, so the topographic image is captured with a smartphone, the examiner performs the contour of the corneal relief manually, and then the neural network performs the diagnosis. The application diagnosed 201 cases (94.81%) correctly. In 212 images, the algorithm missed the classification of 11 cases (5.19%). The major error that occurred was in distinguishing between symmetrical and asymmetrical classes. In keratoconus screening, the application reached 95.00% sensitivity and 98.68% specificity. The work resulted in obtaining an efficient application to capture topographic images using a smartphone camera and their interpretations through applied artificial intelligence.

Too Drained from Being Agile? The Self-Regulatory Effects of the Use of Agile ISD Practices and their Consequences on Turnover Intention

While much is known about the beneficial effects of agile information systems development (ISD), scholars have largely neglected to address its potential downsides. Specifically, research on this topic has thus far overlooked the ambivalent implications of the specific demands placed on developers working in agile ISD teams, including potentially depleting effects. Drawing on ego depletion theory and the associated literature, we provide a more balanced view and introduce self-regulatory resource depletion triggered by using agile ISD practices—encompassing software development (SD) and project management (PM) practices—as a theoretical perspective on why agile developers experience different levels of work-related fatigue that lead to stronger or weaker turnover intentions. Furthermore, we propose that due to the specific way in which agile ISD methods organize ISD project work, developers’ perceived workload influences the intensity by which agile ISD practices affect self-regulatory resources and developers’ feelings of fatigue. We examined our research model using a multimethod approach including quantitative and qualitative data. We found that the use of agile SD practices enhances developers’ self-regulatory resources and reduces fatigue and turnover intention. Our results also show that perceived workload strengthens the energizing effects of the use of agile SD practices and reveals a depleting effect of the use of agile PM practices, with countervailing implications for turnover intention. This study contributes to agile ISD literature by drawing a more nuanced and balanced picture with both resource-enhancing and resource-draining effects of the use of agile ISD practices. Finally, we give managerial advice regarding factors to consider when designing and managing agile ISD projects.

System Based on Market Segmentation to Improve the Export of Peruvian Coffee

In 2021 Peru exported 250 thousand tons of coffee, ranking seventh among the main coffee exporters in the world compared to the 4,000 thousand tons exported by Brazil, which ranks first. This research project aims to optimize coffee export processes through the development of management software for these exporting companies that allows them to have optimized processes, better control of their activities and make better decisions when exporting. Due to the great variety of types of coffee and the different destination markets, market segmentation was defined as a marketing strategy, which will allow the application of differentiated, efficient and effective commercial strategies. With the implemented software, the companies have been able to improve their export processes, the complexity of the different objectives and scenarios, the software plans quite accurately, as well as the calendar, volumes, and types of coffee to be exported. This helps coffee exporters to have adequate control of their activities and improve export processes, being more efficient and above all, making better decisions based on the information stored; With the use of a management tool, a higher percentage of organized producers is achieved, the export process is considerably improved and there is a greater participation in the international market.