Search results

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.

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 purpose of this study is to investigate the factors facilitating and influencing the adoption of DevOps practices specifically tailored to mobile software development, with a focus on understanding the influence of mobile-specific requirements on DevOps integration.

The study employs a qualitative methodology, including a literature review, exploratory case research and partial quantitative assessments through DORA metrics and survey applications. This approach, guided by the Technology-Organization-Environment (TOE) framework, prioritizes in-depth insights into the adoption of DevOps practices and explores strategies for integrating DevOps in mobile software development.

The research identifies several key themes specific to Mobile DevOps adoption, including tool integration issues, testing complexities, deployment challenges and security concerns. These findings underscore the necessity for tailored DevOps solutions that can effectively address the unique demands of mobile software development. The study also proposes actionable strategies to overcome these challenges, thereby enhancing the efficiency, quality and security of mobile applications.

The insights gained from this study provide valuable guidance for practitioners in the mobile software development sector. By understanding and addressing the specific challenges of Mobile DevOps, organizations can improve their DevOps practices and achieve better outcomes in terms of project delivery speed, quality and security. For example, implementing robust testing strategies, investing in compatible tools and developing well-defined rollback procedures can significantly enhance Mobile DevOps effectiveness. Furthermore, incorporating continuous security measures and improving cross-functional collaboration can lead to more secure and efficient mobile application deployments.

This study offers valuable starting points for researching Mobile DevOps in real-world settings, based on insights from practical DevOps implementations in a single-case organization. Organizations can use this information to compare their own DevOps approaches with those of the studied organization, and can facilitate self-assessment and improvement.

This study contributes to the limited literature on Mobile DevOps adoption and proposing actionable strategies. By incorporating the TOE framework, it provides a comprehensive guide that enhances understanding and management of DevOps practices throughout the mobile application development lifecycle and offers significant value to practitioners and researchers alike.

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.

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.

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.

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.

This paper aims to close the gap between the generic concept of knowledge activities (KAs) and implementing them in the context of software engineering organisations concentrating on the non-technical aspects, such as team organisation and practices.

This qualitative research used a questionnaire with practitioners such as software developers and team leads who were asked to provide feedback on a set of team practices and measures typically used in software engineering projects and assess their relation to the activities of acquiring, codifying, storing, maintaining, transferring and creating knowledge. The obtained results were analysed using frequency analysis and further descriptive statistics yielding a matrix linking the investigated team practices and measures to KAs.

Team practices and measures commonly applied in software engineering can be facilitated to trigger particular KAs. While most of these team practices and measures originate from agile methods, they are not restricted to these. A purposeful composition can help in assembling a balanced set of KAs aimed at fostering given knowledge goals in software engineering organisations.

By bridging the communication and terminology gap between knowledge management research and software engineering practitioners, this work lays the foundation for assessing software teams’ knowledge profiles more easily and creating prerequisites for implementing knowledge management by facilitating common practices and measures often already part of their daily work. Hence, overhead can be avoided when implementing knowledge management.

To the best of the authors’ knowledge, this is the first study investigating application and relevance of KAs in the software industry by linking them to practices and measures well-accepted in software engineering, thus providing the necessary vocabulary for the implementation of knowledge management in software development teams.

The purpose of this paper is to integrate job demands–resources theory with core self-evaluation theory to examine how and when sustainable project leadership stimulates sustainable project performance. Psychological empowerment is used as a mechanism between sustainable project leadership and sustainable project performance, whereas core self-evaluation acts as a moderator between sustainable project leadership and psychological empowerment.

This study adopts a time-lagged two-phase approach to collecting data from 257 software engineers working in medium-sized and large companies in the Polish financial sector.

This study reveals the direct and indirect (through psychological empowerment) effects of sustainable project leadership on sustainable project performance. It also confirms that the “sustainable project leadership–psychological empowerment” relationship strengthens with increasing level of project team members’ core self-evaluation.

This article explores a unique research framework. It significantly enriches the literature on sustainable project management, increasing the understanding of effective leadership practices that address the needs of software engineering teams to support sustainable project performance.

Security in large-scale agile is a crucial aspect that should be carefully addressed to ensure the protection of sensitive data, systems and user privacy. This study aims to identify and characterize the security practices that can be applied in managing large-scale agile projects.

A qualitative study is carried out through 18 interviews with 6 software development companies based in Portugal. Professionals who play the roles of Product Owner, Scrum Master and Scrum Member were interviewed. A thematic analysis was applied to identify deductive and inductive security practices.

The findings identified a total of 15 security practices, of which 8 are deductive themes and 7 are inductive. Most common security practices in large-scale agile include penetration testing, sensitive data management, automated testing, threat modeling and the implementation of a DevSecOps approach.

The results of this study extend the knowledge about large-scale security practices and offer relevant practical contributions for organizations that are migrating to large-scale agile environments. By incorporating security practices at every stage of the agile development lifecycle and fostering a security-conscious culture, organizations can effectively address security challenges in large-scale agile environments.