Search results

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.

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 paper is 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 so as to reduce project cost and improve schedule in a global software development (GSD) environment for software development project.

This study employs system dynamics simulation approach to study software project characteristics in both co-located and distributed development environments. The authors consulted 14 experts from Indian software outsourcing industry during our model construction and validation.

The study results show that there is a drop in 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.

The implication of the study is that the project management team should be careful not to keep high percentage of manpower at offshore location in distributed software environment. A large offshore team can increase project cost and schedule due to higher training overhead, lower productivity and higher error proneness. In GSD, the management effort should be to keep requirement analysis and design work at onsite location and involves the offshore team in coding and testing work.

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.

The study is novel as there is little attempt at finding the team distribution between onsite and offshore location in GSD environment.

The purpose of this paper is to present the findings of Phase 1 of the research and to identify Australian agile software development organizations having such coexistence of agile and software configuration management (SCM) practices. This study employed “organization size” variable to study the phenomenon and used theory of Lean Thinking as a lens to analyse implementation variations of agile and SCM practices.

For this study, the research design was comprised of three phases. In Phase 1, a quantitative study using an online survey was performed to answer RQ using various statistical techniques. In Phase 2, an initial conceptual model based on a literature review was developed, and then a qualitative study was performed using one longitudinal case study. In Phase 3, another online survey was performed using various parametric statistical techniques to validate and generalize the findings of Phase 1 and 2 and the proposed SLAM traceability model. The scope of this paper is to discuss only Phase 1 and its associated findings.

The results of the analysis indicated that organizations, regardless of their size, frequently use agile practices for their software development operations. On the other hand, larger organizations use SCM practices comparatively more than medium and small organizations. However, traces of customized SCM process were found in most of the respondent (large, medium, and small) organizations, which indicates the coexistence of agile and SCM practices.

As there is no known listing or database available for such specialized criteria, a non-probabilistic sampling method was used, in the sense that the selection of members of the sample was arbitrary and subjective instead of a non-random selection from the pool of all agile practitioners in the field.

By using the quantitative method approach, this study aims to generate empirical evidence to contribute to the body of knowledge in the relevant areas. On the practical side, this research can also provide support to IT businesses in general, and software development organizations in particular, with the streamlining of the internal operational environment for the facilitation of an adaptable process and the resulting coexistence of value-added agile and SCM practices.

The paper has three purposes: the first is to provide a deeper understanding of the ideology and work practices of free and open source software development, the second to characterize the free software movement as a new type of computerization movement and the third to present a conceptual diagram and framework with an analysis showing how the free software computerization movement has evolved into an occupational community.

Qualitative data were collected over a four year period using a virtual ethnography in a study of free and open source software development and, in particular, a study of a free software community, GNUenterprise, located at www.gnuenterprise.org, which has the goal of developing a free enterprise resource planning software system.

It is concluded that the ideology of the free software movement continues to be one of the factors which mobilize people to contribute to free and open source software development. This movement represents a new type of computerization movement which promotes the investment of time in learning a new software development process instead of investment of money in the acquisition and use of new technology.

The research findings are limited by a detailed study of only one free software development project.

This paper is of significance to software developers and managers of firms who wish to incorporate free and open source software into their companies.

This research presents an original conceptual diagram and framework for how computerization movements have emerged into an occupational community.

Connected Health is an emerging and rapidly developing field never before witnessed across the healthcare sector. It has the potential to transform healthcare service systems by increasing its safety, quality and overall efficiency. However, as healthcare technologies or medical devices continuously rely more on software development, one of the core challenges is examining how Connected Health is regulated – often impacting Connected Health innovation. The purpose of this paper is to present an understanding of how Connected Health is regulated. Many of these regulatory developments fall under “medical devices”, giving rise to Software-as-a-Medical Device (SaaMD).

Through an extensive literature review, this paper demystifies Connected Health regulation. It presents the outcome of expert discussions which explore the key regulatory developments in the context of Connected Health to provide a practical guide to understanding how regulation can potentially shape healthcare innovation.

Several key issues are identified, and the authors present a comprehensive overview of regulatory developments relating to Connected Health with a view to support the continued growth of IT-enabled healthcare service models. The authors also identify the key challenges in Connected Health and identify areas for future research.

A key outcome of this research is a clearer understanding of the opportunities and challenges that regulation and standards present to Connected Health. Furthermore, this research is of critical importance in a first attempt towards recognising the impact of regulation and standards compliance in Connected Health.

The purpose of this paper is to present a model of the 24‐h software development process to help software project managers assess the profitability of a 24‐h development configuration and to select the optimal partnering sites. The model also helps the customer‐support divisions of software firms to decide which customer requests need to be performed using the 24‐h development mode.

This paper presents a graphical representation of the 24‐h software development process. Highlighting the importance of interaction times between two sites and the role of product‐, process‐, and site‐related factors that influence its value, the paper adopts the method of pair‐wise comparison of factors as done in the case of analytical hierarchy process and proposes a multiplicative model for its estimation. The software development time and cost are thereafter estimated by using site‐specific values of work hours, compensation package, and productivity. The approach is used to determine the economic viability of 24‐h development and make optimum site selection for a number of decision‐making situations.

The results obtained from applying the models to hypothetical, but realistic problems, with different values for site‐ and personnel‐specific factors to prove the ability of the model to be used in real‐life situations.

The proposed model does not consider effects of factors like multiple interactions, reworks, and errors in communication.

A circular representation of the 24‐h software development process, the multiplicative model for estimating the length of interaction time, and the time and cost of development in such a process are the main contributions of the paper.

The purpose of this paper is to classify the factors affecting the performance of software development teams and stress the soft (non‐technical) factors affecting the performance of software development teams.

This paper is based on the thorough secondary research and literature review of the past empirical studies published in reputed journals. The methodology followed is the secondary research based on extensive literature review of empirical studies done and analysis of the findings of those studies and categorization of the factors affecting the software development team performance. Literature review and analysis were carried out between March 2010 and March 2011.

It was found that the soft factors such as team climate, team diversity, team innovation, team member competencies and characteristics, top management support and team leader behavior, have an effect on software development team performance. Mutual trust and communication effectiveness are found to be the prioritized factors affecting the software development team performance.

The conclusions made are based on the past empirical studies found in the literature. A primary research can be done by taking these soft factors into consideration and implications or observations can be found on the software development team's performance.

The original contribution of this paper is the classification of factors affecting the performance of software development teams. This contribution also highlights the soft factors such as team climate, which was not discussed much in the literature. It also highlights trust and communication, for example, as leading factors affecting the software development team performance.

This paper aims to explore the expertise level required in various kinds of business knowledge such as regulatory, domain, strategic, operation process and, business process to execute globally distributed software projects for development, re-engineering and maintenance projects in the Indian outsourcing software industry.

This study adopted a questionnaire survey method to collect the expert responses for a knowledge management framework which is suggested in the literature for software development work. The questionnaire survey findings were verified by expert interviews.

The research shows that there is a lot of similarity between re-engineering and maintenance projects for different kinds of business knowledge expertise requirements for execution. The development projects require higher expertise in all the business knowledge for execution.

The research work studies the business knowledge required for the execution of development, re-engineering and maintenance projects in Indian outsourcing software projects. However, the project’s characteristics can vary drastically for a single kind of project. So the study cannot be generalized and instead should be used as a tool for learning.

The research findings can be used by software project managers to get insight into project planning, which can help the division of work between the onsite, offshore team and individual work allocation.

The research is novel as there are very few previous attempts to find the business expertise needed to execute various kinds of software projects in the Indian outsourcing industry.

Software development activities have been identified as a ‘window of opportunity’ for latecomer companies. Based on a critical literature review, this paper argues that studies are yet to scrutinise the exact nature and extent of the capabilities, which the latecomer companies have been able to develop. The main proposition advanced by this research is that the analyses need to investigate the technological capabilities, which the latecomer companies have been able to accumulate. This study outlines the specifics in analysing technological capabilities in latecomer software companies and improves our understanding about the complexity in developing software industries in latecomer context.