Search results

As the novel coronavirus 2019 (COVID-19) impacts the world, software practitioners are collaboratively working remotely from home. The pandemic has disrupted software practitioners’ productivity forcing changes to agile methodology adopted by software practitioners in software organizations. Therefore, this study aims to provide implication on the issues and recommendations for improving software practitioners’ productivity and also examine the impact of the COVID-19 pandemic on agile software development.

This paper adopts a narrative literature review to provide early assessment based on secondary data from the literature and available document reports from studies published from 2019 to 2022 to explore software practitioners’ productivity and agile software development during the working from home directive amidst the COVID-19 pandemic. A total of 60 sources which met the inclusion criteria were used to provide preliminary evidence grounded on secondary data from the literature. Descriptive analysis was used to provide qualitative findings from the literature.

Findings from this study present the significance of working from home directive on agile software development and software practitioners’ productivity. More importantly, findings from the secondary data shed light on software practitioners’ productivity adopting agile software development amidst the COVID-19 pandemic. Additionally, the findings present virtual collaborative platforms used by software practitioners, technical and social barriers of agile software development during the pandemic and recommendations for remote agile software development.

This study explores the significance of working from home directive on software practitioners’ productivity during COVID-19 pandemic and further investigates how are software practitioners’ productivity adopting agile software development practices amidst the COVID-19 pandemic. Besides, this study discusses the challenges software practitioners currently face and offers some strategies to bridge the gaps in agile software development to help software practitioners, system developers, software managers and software organizations adapt to the changes caused by the pandemic.

The purpose of this study is to examine the state of the literature on knowledge sharing in open source software (OSS) development communities by examining the existing research and identifying the knowledge gaps and opportunities that can inform areas for future research.

A systematic literature review was conducted of literature published between January 2011 and February 2023. A total of 24 papers were identified and reviewed.

The findings reveal that the literature on knowledge sharing in OSS development communities from developing countries are limited. Additionally, there exists a limited focus on the development of frameworks to support knowledge sharing in OSS communities. The transient nature of OSS development contributors’ results in knowledge loss; thus, knowledge retention needs further investigation.

This study only included papers whose titles, keywords or abstracts included the search keywords “knowledge sharing” and “Open Source Software”. While the keywords were carefully applied, when applying the search, it cannot be ruled that some relevant studies might have been missed. The study was also limited to conferences and journal papers published in English. Despite the limitations, the study provides a systematic review of knowledge sharing in OSS communities and presents findings that can be useful to researchers and practitioners interested in this area.

The study provides a systematic literature review of published papers and identifies themes and future research areas on knowledge sharing in OSS communities. Additionally, this review offers insights into future research avenues for theory, content and context on knowledge sharing in OSS development communities.

This study aims to develop a model for coordination and communication overhead in distributed software development through case study analysis in the Indian outsourcing software industry. The model is based on business knowledge, which can be classified as domain, regulatory, strategic, business process and operation process knowledge as per existing literature.

Double case study method was used to verify an existing knowledge–management framework of software development from the literature. The stakeholders of both the cases were interviewed, and project documents were verified to reach conclusions.

The findings supported the business knowledge classification from the literature. The concept can be used to analyze the software project in a distributed environment.

The research work findings are based only on two case studies. The study findings cannot be generalized and should be used as a learning tool. There can be large variations of project characteristics with differences in business knowledge requirements. The research shows the importance of business knowledge transfer in global software development.

Projects managers in the distributed software development environment can use the findings in project planning and work allocation for better control over cost and schedule, etc.

There is little research works attempted to study the business knowledge classification in the global software industry making the research novel.

Managing project completion within the stipulated time is significant to all firms' sustainability. Especially for software start-up firms, it is of utmost importance. For any schedule variation, these firms must spend 25 to 40 percent of the development cost reworking quality defects. Significantly, the existing literature does not support defect rework opportunities under quality aspects among Indian IT start-ups. The present study aims to fill this niche by proposing a unique mathematical model of the defect rework aligned with the Six Sigma quality approach.

An optimization model was formulated, comprising the two objectives: rework “time” and rework “cost.” A case study was developed in relevance, and for the model solution, we used MATLAB and an elitist, Nondominated Sorting Genetic Algorithm (NSGA-II).

The output of the proposed approach reduced the “time” by 31 percent at a minimum “cost”. The derived “Pareto Optimal” front can be used to estimate the “cost” for a pre-determined rework “time” and vice versa, thus adding value to the existing literature.

This work has deployed a decision tree for defect prediction, but it is often criticized for overfitting. This is one of the limitations of this paper. Apart from this, comparing the predicted defect count with other prediction models hasn’t been attempted. NSGA-II has been applied to solve the optimization problem; however, the optimal results obtained have yet to be compared with other algorithms. Further study is envisaged.

The Pareto front provides an effective visual aid for managers to compare multiple strategies to decide the best possible rework “cost” and “time” for their projects. It is beneficial for cost-sensitive start-ups to estimate the rework “cost” and “time” to negotiate with their customers effectively.

This paper proposes a novel quality management framework under the Six Sigma approach, which integrates optimization of critical metrics. As part of this study, a unique mathematical model of the software defect rework process was developed (combined with the proposed framework) to obtain the optimal solution for the perennial problem of schedule slippage in the rework process of software development.

The relationship between the various existing smell taxonomies and the smell impacting factors has been established. The ideology is to identify the most critical smell influencing factors in the vicinity of various software development environments.

To fulfill the said task, the utilization of the amalgamation of two multicriteria decision-making techniques, namely, Entropy method and CODAS method, is presented.

Through this article, the most critical smell impacting criteria with respect to the smell taxonomies is identified. Furthermore, the behaviour of 4 software development principles was then analysed, and their working state has been successfully assessed.

The ideology to study design-related smells in the software system has been studied by a lot of researchers. Some of them have worked upon their detection and the corresponding refactoration process with the help of several algorithms like machine learning and artificial intelligence. But how and to what extent these design-related smells impact the software development environment has remained out of the limelight till now. Through this article, this research gap has been identified, and an attempt to fill it has been made.

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.

Recently, the popularity of software has grown significantly in the market. Enhancement of software is needed to decrease the burden of getting high-quality and reliable software. To achieve this, the software is upgraded by adding new features to the previous version. Therefore, adding new features in the last version to be consistent with the earlier version is challenging. This paper aims to discuss the optimal software enhancement and customer growth model.

This paper discusses a model when new features are added to the software, and the customers' adoption of the software is presented as a customer growth model. An optimal control problem is introduced to maximize the profit obtained from the software system over the system's lifetime period. Total gain is calculated by the value generated from selling the software over the total expenditure during the software development process. The closed-form solution and some theoretical results are presented using the optimal control-theoretic approach. The theoretical results are supported by a numerical example.

This paper gives several substantive insights during sensitivity analysis and provides essential results. The results discussed here are compatible with the actual scenario and useful in software enhancement.

The authors have proposed a new feature growth and customer growth model to maximize the total profit using optimal control theory.

The purpose of this study is to investigate the barriers that prevent workers in the software industry from experiencing flow in their work.

This study was conducted by using a qualitative critical incident technique-inspired questionnaire.

The findings suggest that workers in the software industry perceive that the most obvious obstacles to experiencing flow are related to work not presenting enough cognitive challenges and situational barriers related to the characteristics of the job (e.g. workdays having too many interruptions and distractions, timetables often being considered too tight for creative exploration and problem solving and having negative user experiences with development tools).

The findings provide insights into flow barriers, specifically barriers that prevent workers in the software industry from experiencing flow.

Project-based learning is one of the most effective methods of transferring academic knowledge and skills to real-world situations in higher education. However, its effectiveness is not much investigated focusing on the students' narrative. This study aims at evaluating the students' experience and perspective on adopting project-based learning in master by research and doctoral programmes for proactive skills development.

This study evaluates the self-reflection of 10 postgraduate students and their supervisor who have participated in developing a software tool for solar photovoltaics (PV) integrated building envelope design, management and the related education.

Findings reveal that the students have effectively improved their knowledge on the subject via collaborating with the industry, self-learning/observation, peer learning, problem-solving and teamwork. Dividing the project into student-led tasks has improved the decision-making and leadership skills, risks identification, planning and time management skills. The overall experience has (1) built up confidence in students, (2) enhanced their creativity and critical thinking and (3) improved their proactive skills and context knowledge.

A clear research gap can be seen in exploring the effectiveness of project-based learning for master by research and doctoral programmes, which mainly focus on extensive research. These programmes do not necessarily focus on developing students' proactive skills, which is the main requirement if they intend to work in the construction industry. This paper addresses the above research gap by demonstrating the effectiveness of project-based learning for developing the proactive skills in a research-intensive learning environment.

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.