Search results
1 – 10 of over 32000Joanna F. DeFranco and Phillip Laplante
The purpose of this mapping study has been performed to identify, critically analyze and synthesize research performed in the area of software engineering teams. Teams, in a…
Abstract
Purpose
The purpose of this mapping study has been performed to identify, critically analyze and synthesize research performed in the area of software engineering teams. Teams, in a general sense, have been studied extensively. But the distinctive processes that need to be executed effectively and efficiently in software engineering require a better understanding of current software engineering team research.
Design/methodology/approach
In this work, software engineering team publications were analyzed and the key findings of each paper that met our search inclusion criteria were synthesized. In addition, a keyword content analysis was performed to create a taxonomy to categorize each paper and evaluate the state of software engineering team research.
Findings
In software engineering team research, the resulting areas that are the most active are teamwork/collaboration, process/design and coordination. Clear themes of analysis have been determined to help understand how team members collaborate, factors affecting their success and interactions among all project stakeholders. In addition, themes related to tools to support team collaboration, improve the effectiveness of software engineering processes and support team coordination have been found. However, the research gaps determined from the content analysis point toward a need for more research in the area of communication and tools.
Originality/value
The goal of this work is to define the span of previous research in this area, create a taxonomy to categorize such research and identify open research areas to provide a clear road map for future research in the area of software engineering teams. These results, along with the key finding themes presented, will help guide future research in an area that touches all parts of the software engineering and development processes.
Details
Keywords
Oliver K. Burmeister and John Weckert
It has been argued that it is in the best interests of IT professionals, to adopt and enforce professional codes in the work place. But there is no code for usability engineers…
Abstract
It has been argued that it is in the best interests of IT professionals, to adopt and enforce professional codes in the work place. But there is no code for usability engineers, unless one accepts that it is a branch of software engineering. The new joint ACM/IEEE‐CS Software Engineering Code of Ethics is applied to actual usability cases. This enables usability engineers to interpret this code in their profession. This is achieved by utilizing four case studies both directly in terms of the ethical issues involved and in the light of the code. Also examined are the short‐comings of the code for the domain of usability engineering, and suggestions are made for enhancements for future revisions of the code.
Details
Keywords
RamKaran Yadav, M.L. Mittal and Rakesh Jain
The purpose of this paper is to gain insights about the applicability of Lean principles in software industry along with the Lean implementation issues.
Abstract
Purpose
The purpose of this paper is to gain insights about the applicability of Lean principles in software industry along with the Lean implementation issues.
Design/methodology/approach
Exploratory case studies have been carried out in five software companies. Data were collected by observation and semi-structured interviews with project managers. In this paper, case organizations are categorized as product vs project software development (SD) organization.
Findings
It is found that although Lean principles are being adopted in SD projects, application of all Lean principles is not visible. This research reveals that value and flow are more relevant in SD organizations, while value stream, pull and perfection are not conspicuous.
Originality/value
This paper would prove invaluable to lean practitioners and researchers to gain knowledge in lean SD. The paper puts forward the key issues that should be addressed for successful adoption of lean in SD. This study set out to determine the practitioners’ perception of the applicability of lean principles in SD projects. It provides a sound basis for further empirical research on adoption of lean principles in SD organizations.
Details
Keywords
Dindin Wahyudin, Khabib Mustofa, Alexander Schatten, Stefan Biffl and A. Min Tjoa
In response to the increasing number of open‐source software (OSS) project initiatives and the increasing demand of OSS products as alternative solutions by industries, it is…
Abstract
Purpose
In response to the increasing number of open‐source software (OSS) project initiatives and the increasing demand of OSS products as alternative solutions by industries, it is important for particular stakeholders such as the project host/supporter project‐leading teams, and prospective customers to determine whether a project initiative is likely to be sustainable and is worth supporting. This paper aims to propose a concept of “health” indicators and an evaluation process that can help to get a status overview of OSS projects in a timely fashion and predict project survivability based on the project data available on web repositories.
Design/methodology/approach
For initial empirical evaluation of the concept, the indicators are applied to well‐known web‐based OSS projects (Apache Tomcat and Apache HTTP Server) and the results are compared with challenged projects (Apache Xindice and Apache Slide). The results are discussed with OSS experts to investigate the external validity of the indicators.
Findings
From a software project management point of view, a typical web‐based OSS project can be viewed as a web‐engineering process, since most OSS projects exploit the benefits of a web platform and enable the project community to collaborate using web‐based project tools and repositories such as mailing lists, bug trackers, and versioning systems (CVS/SVN) to deliver web systems and applications. These repositories can provide rich collections of process data, and artifacts which can be analyzed to better understand the project status.
Originality/value
The paper provides information of value about open‐source solutions.
Details
Keywords
Andrey Maglyas, Uolevi Nikula, Kari Smolander and Samuel A. Fricker
Software product management (SPM) unites disciplines related to product strategy, planning, development, and release. There are many organizational activities addressing…
Abstract
Purpose
Software product management (SPM) unites disciplines related to product strategy, planning, development, and release. There are many organizational activities addressing technical, social, and market issues when releasing a software product. Owing to the high number of activities involved, SPM remains a complex discipline to adopt. The purpose of this paper is to understand what are the core and supporting SPM activities.
Design/methodology/approach
The authors adopted the research method of meta-ethnography to present a set of techniques for synthesizing individual qualitative studies to increase the degree of conceptualization. The results obtained from three empirical studies were synthesized using the meta-ethnography approach to enhance, rethink, and create a higher level abstraction of the findings.
Findings
The results show that the study has both theoretical and practical contribution. As the meta-ethnography synthesis has not been widely applied in software engineering, the authors illustrate how to use this research method in the practice of software engineering research. The practical contribution of the study is in the identification of five core and six supporting SPM activities.
Originality/value
The practical value of this paper is in the identification of core SPM activities that should be present in any company practicing SPM. The list of supporting SPM consists of activities that are not reported to product manager but affect the product success.
Details
Keywords
Mitali Chugh, Nitin Chanderwal, Amar Kumar Mishra and Devendra Kumar Punia
This study aims to present insights on the relationship between perceived software process improvement (PSPI) and information technology (IT)-enabled knowledge management (KM)…
Abstract
Purpose
This study aims to present insights on the relationship between perceived software process improvement (PSPI) and information technology (IT)-enabled knowledge management (KM). Moreover, the study provides an understanding of the mediating effect of critical success factors (CSFs) for effective IT-enabled KM on the previously mentioned relationship.
Design/methodology/approach
The respondents in the study involved employees in the software engineering (SE) organizations in national capital region in India. The structured equation modeling technique carried out through IBM.SPSS.Amos.v21-EQUiNOX was used to develop and evaluate the proposed framework. The proposed hypothesis testing has been carried out by path analysis using SPSS process macro.
Findings
The findings of the empirical study reveal that a significant relationship exists between the variables under investigation. Moreover, it was observed that CSFs act as a mediator between PSPI and IT-enabled KM. The identified factors are associated with various aspects as managerial, infrastructure, financial, systems and processes for IT-enabled KM. IT acts as a moderator between KM and PSPI and facilitate the various phases of KM as knowledge creation, storage and retrieval, sharing and application of knowledge.
Practical implications
The present study introduces a framework for identifying and applying the CSFs that influence the KM initiatives for PSPI in an SE organization. The practitioners can use the CSFs for assessing the performance (strengths and weaknesses) in process of software development and KM practices. Researchers can use the resultant framework proposed in the empirical study for PSPI, IT-enabled KM, and in academia, the framework supports to organize the study of IT-enabled KM for PSPI.
Originality/value
The general comprehension of the relationship between IT-enabled KM and PSPI for Indian SE organizations is scarce in the literature. Following, the analysis expands the earlier research by exploring the mediating role of the CSFs and the moderating effect of IT for KM and PSPI relationship.
Details
Keywords
Debasisha Mishra and Biswajit Mahanty
The aim of this paper is to make an attempt to find good values of onsite–offshore team strength; number of hours of communication between business users and onsite team and…
Abstract
Purpose
The aim of this paper is to make an attempt to find good values of onsite–offshore team strength; number of hours of communication between business users and onsite team and between onsite and offshore team to reduce cost and improve schedule for re-engineering projects in global software development environment.
Design/methodology/approach
The system dynamics technique is used for simulation model construction and policy run experimentation. The experts from Indian software outsourcing industry were consulted for model construction, validation and analysis of policy run results in both co-located and distributed software development environment.
Findings
The study results show that there is a drop in the overall team productivity in outsourcing environment by considering the offshore options. But the project cost can be reduced by employing the offshore team for coding and testing work only with minimal training for imparting business knowledge. The research results show that there is a potential to save project cost by being flexible in project schedule.
Research limitations/implications
The study found that there could be substantial cost saving for re-engineering projects with a loss of project schedule when an appropriate onsite–offshore combination is used. The quality and productivity drop, however, were rather small for such combinations. The cost savings are high when re-engineering work is sent to offshore location entirely after completion of requirement analysis work at onsite location and providing training to offshore team in business knowledge The research findings show that there is potential to make large cost savings by being flexible in project schedule for re-engineering projects.
Practical implications
The software project manager can use the model results to divide the software team between onsite and offshore location during various phases of software development in distributed environment.
Originality/value
The study is novel as there is little attempt at finding the team distribution between onsite and offshore location in global software development environment.
Details
Keywords
Constantin Bratianu, Alexeis Garcia-Perez, Francesca Dal Mas and Denise Bedford
Arshad Ahmad, Chong Feng, Shi Ge and Abdallah Yousif
Software developers extensively use stack overflow (SO) for knowledge sharing on software development. Thus, software engineering researchers have started mining the…
Abstract
Purpose
Software developers extensively use stack overflow (SO) for knowledge sharing on software development. Thus, software engineering researchers have started mining the structured/unstructured data present in certain software repositories including the Q&A software developer community SO, with the aim to improve software development. The purpose of this paper is show that how academics/practitioners can get benefit from the valuable user-generated content shared on various online social networks, specifically from Q&A community SO for software development.
Design/methodology/approach
A comprehensive literature review was conducted and 166 research papers on SO were categorized about software development from the inception of SO till June 2016.
Findings
Most of the studies revolve around a limited number of software development tasks; approximately 70 percent of the papers used millions of posts data, applied basic machine learning methods, and conducted investigations semi-automatically and quantitative studies. Thus, future research should focus on the overcoming existing identified challenges and gaps.
Practical implications
The work on SO is classified into two main categories; “SO design and usage” and “SO content applications.” These categories not only give insights to Q&A forum providers about the shortcomings in design and usage of such forums but also provide ways to overcome them in future. It also enables software developers to exploit such forums for the identified under-utilized tasks of software development.
Originality/value
The study is the first of its kind to explore the work on SO about software development and makes an original contribution by presenting a comprehensive review, design/usage shortcomings of Q&A sites, and future research challenges.
Details
Keywords
Martin Dietze and Marion Kahrens
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…
Abstract
Purpose
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.
Design/methodology/approach
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.
Findings
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.
Practical implications
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.
Originality/value
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.
Details