Search results

The use of structured literature review methods like bibliometric analysis is growing in the management fields, but there is limited knowledge on how they can be facilitated by technology. Hence, we conducted a broad overview of software tools, their roles, and limitations in structured (bibliometric) literature reviewing activities. Subsequently, we show that several software tools are freely available to aid in searching the literature, identifying/ extracting relevant publications, screening/assessing quality of the extracted data, and performing analyses to generate insights from the literature. However, their applications may be confronted with several challenges such as limited analytical and functional capabilities, inadequate technological skills of researchers, and the fact that the researcher's insights are still needed to generate compelling conclusions from the results produced by software tools. Consequently, we contribute toward advancing the methodologies for performing structured reviews by providing a comprehensive and updated overview of the knowledge base of key technological software tools and the conduct of structured or bibliometric literature reviews.

This study aims to understand how practitioners use their insights in software development models to share experiences within and between organizations.

This is a qualitative study of practitioners in software development projects, in large-, medium- or small-size businesses. It analyzes interview material in three-step iterations to understand reflexive practice when using software development models.

The study shows how work processes are based on team members’ experiences and common views. This study highlights the challenges of organizational learning in system development projects. Current practice is unreflective, habitual and lacks systematic ways to address recurring problems and share information within and between organizations. Learning is episodic and sporadic. Knowledge from previous experience is individual not organizational.

Software development teams and organizations tend to learn about, and adopt, software development models episodically. This research expands understanding of how organizational learning takes place within and between organizations with practitioners who participate in teams. Learnings show the potential for further research to determine how new curriculums might be formed for teaching software development model improvements.

This paper aims to examine the impact of problem-solving activities, emotional experiences and contextual and personal factors on learning from dealing with software-related problems in everyday office work.

To measure the use of problem-solving activities, emotional experiences and the contextual factors of problem characteristics and learning in situ, a research diary was used. To measure team psychological safety (contextual factor) and personal factors, including the Big Five personality traits, occupational self-efficacy and technology self-efficacy, the authors administered a self-report questionnaire. In sum, 48 students from a software company in Germany recorded 240 diary entries during five working days. The data was analysed using multilevel analysis.

Results revealed that asking others and using information from the internet are positive predictors of self-perceived learning from a software-related problem, while experimenting, which was the most common activity, had a negative effect on learning. Guilt about the problem was positively related to learning while working in the office (as opposed to remote work), and feeling irritated/annoyed/angry showed a negative effect. Surprisingly, psychological safety had a negative effect on perceived learning.

Major limitations of the study concern the convenience sample and the disregard for the sequence of the activities.

This study contributes to the limited empirical evidence on employees’ problem-solving activities and informal workplace learning in the software context. To overcome the shortcomings of previous studies using retrospective assessments and in-lab observations, this study uses the diary method to investigate in situ.

Software defect prediction (SDP) is a critical aspect of software quality assurance, aiming to identify and manage potential defects in software systems. In this paper, we have proposed a novel hybrid approach that combines Gray Wolf Optimization with Feature Selection (GWOFS) and multilayer perceptron (MLP) for SDP. The GWOFS-MLP hybrid model is designed to optimize feature selection, ultimately enhancing the accuracy and efficiency of SDP. Gray Wolf Optimization, inspired by the social hierarchy and hunting behavior of gray wolves, is employed to select a subset of relevant features from an extensive pool of potential predictors. This study investigates the key challenges that traditional SDP approaches encounter and proposes promising solutions to overcome time complexity and the curse of the dimensionality reduction problem.

The integration of GWOFS and MLP results in a robust hybrid model that can adapt to diverse software datasets. This feature selection process harnesses the cooperative hunting behavior of wolves, allowing for the exploration of critical feature combinations. The selected features are then fed into an MLP, a powerful artificial neural network (ANN) known for its capability to learn intricate patterns within software metrics. MLP serves as the predictive engine, utilizing the curated feature set to model and classify software defects accurately.

The performance evaluation of the GWOFS-MLP hybrid model on a real-world software defect dataset demonstrates its effectiveness. The model achieves a remarkable training accuracy of 97.69% and a testing accuracy of 97.99%. Additionally, the receiver operating characteristic area under the curve (ROC-AUC) score of 0.89 highlights the model’s ability to discriminate between defective and defect-free software components.

Experimental implementations using machine learning-based techniques with feature reduction are conducted to validate the proposed solutions. The goal is to enhance SDP’s accuracy, relevance and efficiency, ultimately improving software quality assurance processes. The confusion matrix further illustrates the model’s performance, with only a small number of false positives and false negatives.

Agile principles have been widely used in software development team practice since the creation of the Agile Manifesto. Studies have examined variables related to agile principles without systematically considering the relationships among key team, agile methodology, and process variables underlying the agile principles and how these variables jointly influence the achievement of software development agility. In this study, the authors tested a team/methodology–process–agility model that links team variables (team autonomy and team competence) and methodological variable (iterative development) to process variables (communication and collaborative decision-making), which are in turn linked to software development agility (ability to sense, respond and learn).

Survey data from one hundred and sixty software development professionals were analyzed using structural equation modeling methods.

The results support the team/methodology–process–agility model. Process variables (communication and collaborative decision-making) mediated the effects of team (autonomy and competence) and methodological (iterative development) variables on software development agility. In addition, team, methodology and process variables had different effects on the three dimensions of software development agility.

The results contribute to the literature on organizational IT management by establishing a team/methodology–process–agility model that can serve as a basis for developing a core theoretical foundation underlying agile principles and practices. The results also have practical implications for organizations in understanding and managing holistically the different roles that agile methodological, team and process factors play in achieving software development agility.

The applications of Artificial Intelligence (AI) in various areas of professional and knowledge work are growing. Emotions play an important role in how users incorporate a technology into their work practices. The current study draws on work in the areas of AI-powered technologies adaptation, emotions, and the future of work, to investigate how knowledge workers feel about adopting AI in their work.

We gathered 107,111 tweets about the new AI programmer, GitHub Copilot, launched by GitHub and analysed the data in three stages. First, after cleaning and filtering the data, we applied the topic modelling method to analyse 16,130 tweets posted by 10,301 software programmers to identify the emotions they expressed. Then, we analysed the outcome topics qualitatively to understand the stimulus characteristics driving those emotions. Finally, we analysed a sample of tweets to explore how emotional responses changed over time.

We found six categories of emotions among software programmers: challenge, achievement, loss, deterrence, scepticism, and apathy. In addition, we found these emotions were driven by four stimulus characteristics: AI development, AI functionality, identity work, and AI engagement. We also examined the change in emotions over time. The results indicate that negative emotions changed to more positive emotions once software programmers redirected their attention to the AI programmer's capabilities and functionalities, and related that to their identity work.

Overall, as organisations start adopting AI-powered technologies in their software development practices, our research offers practical guidance to managers by identifying factors that can change negative emotions to positive emotions.

Our study makes a timely contribution to the discussions on AI and the future of work through the lens of emotions. In contrast to nascent discussions on the role of AI in high-skilled jobs that show knowledge workers' general ambivalence towards AI, we find knowledge workers show more positive emotions over time and as they engage more with AI. In addition, this study unveils the role of professional identity in leading to more positive emotions towards AI, as knowledge workers view such technology as a means of expanding their identity rather than as a threat to it.

Algorithm bias refers to repetitive computer program errors that give some users more weight than others. The aim of this article is to provide a deeper insight of algorithm bias in AI-enabled ERP software customization. Although algorithmic bias in machine learning models has uneven, unfair and unjust impacts, research on it is mostly anecdotal and scattered.

As guided by the previous research (Akter et al., 2022), this study presents the possible design bias (model, data and method) one may experience with enterprise resource planning (ERP) software customization algorithm. This study then presents the artificial intelligence (AI) version of ERP customization algorithm using k-nearest neighbours algorithm.

This study illustrates the possible bias when the prioritized requirements customization estimation (PRCE) algorithm available in the ERP literature is executed without any AI. Then, the authors present their newly developed AI version of the PRCE algorithm that uses ML techniques. The authors then discuss its adjoining algorithmic bias with an illustration. Further, the authors also draw a roadmap for managing algorithmic bias during ERP customization in practice.

To the best of the authors’ knowledge, no prior research has attempted to understand the algorithmic bias that occurs during the execution of the ERP customization algorithm (with or without AI).

This study aims to investigate the effects of organizational culture factors on the selection of software process development models and develops a conceptual model for selecting and adopting process development models with an organizational culture approach, using 12 criteria and their sub-criteria defined in Fey and Denison’s model (12 criteria).

The research hypotheses were investigated using statistical analysis, and then the criteria and sub-criteria were selected based on Fey and Denison’s model and the experts’ viewpoints. Afterward, the organizational culture of the selected company was measured using the data from 2016 and 2017, based on Fey and Denison’s questionnaire. Due to the correlation between the criteria, using the decision-making trial and evaluation technique, the correlation between sub-criteria were determined, and by analytical network process method and using Super-Decision software, the process development model was preferred to the 12 common models in information systems development.

Results indicated a significant and positive effect of organizational culture factors (except the core values factor) on the selection of development models. Also, by changing the value of organizational culture, the selected process development model changed either. Sensitivity analysis performed on the sub-criteria implied that by changing and improving some sub-criteria, the organization will be ready and willing to use the agile or risk-based models such as spiral and win-win models. Concerning units where the mentioned indicators were at moderate and low limits, models such as waterfall, V-shaped and incremental worked more appropriately.

While many studies were performed in comparing development models and investigating their strengths and weaknesses, and the impact of organizational culture on the success of information technology projects, literature indicated that the impact of organizational sub-culture prevailing in the selection of development process models has not been investigated. In this study, new factors and indicators were addressed affecting the selection of development models with a focus on organizational culture. Correlation among the factors and indicators was also investigated and, finally, a conceptual model was proposed for proper adoption of the models and methodologies of system development.

This research aims to investigate the process of value creation, value delivery, and value capture in project-based companies. Most previous research focused on companies that operate regularly and offer manufactured products or services. This research used companies in the field of information technology that developed software to explain how value creation, value delivery, and value capture occurred. A case study with qualitative research was applied to analyze between cases. Empirical findings showed that companies carry out six activities to ensure that value creation, value delivery, and value capture can be realized in the software development process. The six activities were iterative and not a rigid sequence. This research was limited to the software industry, and further research can test the results of this study by using a survey to increase the generalizability theory developed in this study.

This study aims to investigate the factors associated with the intention to use information technology in audit (ITIA) in Iraq.

The study uses a quantitative approach based on a questionnaire survey of 186 respondents. The study population includes respondents who are board members, senior executives, internal auditors and information technology (IT) assistants in various Iraqi organizations from different sectors. Structural equation modeling has been used to estimate the results.

The findings exhibit that most auditors in Iraq use basic IT software. However, among several specialized and advanced IT audit software packages, only generalized audit software is used by about 20%. The results also indicate that social factors significantly and positively impact auditors’ and practitioners’ perceptions of ITIA use. Moreover, the results reveal that companies and auditors who use or audit complex accounting systems perceive higher benefits and intent to adopt ITIA. However, the results report that organizational support, professional support, competency and IT education have an insignificant effect on ITIA adoption.

The originality of the present research lies in several aspects. First, the research study focuses specifically on Iraq, which is an emerging and less developed country influenced by social and economic. This research context provides a unique perspective and contributes to the understanding of ITIA adoption in less developed countries. The study investigates how external factors, including social and external pressure and the support of government professional bodies, affect the adoption of ITIA. Further, it assesses the influence of firms’ specific factors such as management support, level of competency and complexity of accounting information systems. Second, the study uses a quantitative approach with a questionnaire survey from various Iraqi organizations and sectors. The specific sample composition adds originality by capturing insights from different levels of organizational hierarchy and diverse professional backgrounds. Third, the findings shed light on the current IT usage in auditing practices in Iraq, highlighting that most auditors use basic IT software and the limited adoption of specialized IT audit software packages. Finally, the study’s originality is also reflected in its contribution to expanding knowledge on the perceived benefits and challenges associated with ITIA adoption in less developed countries. By emphasizing the need for broader awareness of emerging technology-enabled auditing software and considering the unique characteristics of less developed countries, the research provides valuable insights and implications for practitioners, policymakers and researchers.