Intercultural Collaboration in the ICT Sector

2010 ◽  
pp. 1617-1647
Author(s):  
Martina Maletzky
Keyword(s):  
Software Development ◽  
Global Sourcing ◽  
Intercultural Collaboration ◽  
Work Atmosphere ◽  
Different Types

In the context of global sourcing in, and internationalization of, the ICT sector, intercultural collaboration is for many ICT workers a daily affair. Especially in the field of software development, where the needs for communication are high, intercultural collaboration poses a particular challenge. Misunderstandings and an unproductive work atmosphere may result in hidden costs for the companies. This chapter highlights the different types of intercultural collaboration in the ICT sector, identifying the special challenges that occur and suggesting ways in which companies may minimize such challenges of intercultural collaboration.

Intercultural Collaboration in the ICT Sector

2011 ◽  
pp. 167-194 ◽  
Author(s):  
Martina Maletzky
Keyword(s):  
Software Development ◽  
Global Sourcing ◽  
Intercultural Collaboration ◽  
Work Atmosphere ◽  
Different Types

In the context of global sourcing in, and internationalization of, the ICT sector, intercultural collaboration is for many ICT workers a daily affair. Especially in the field of software development, where the needs for communication are high, intercultural collaboration poses a particular challenge. Misunderstandings and an unproductive work atmosphere may result in hidden costs for the companies. This chapter highlights the different types of intercultural collaboration in the ICT sector, identifying the special challenges that occur and suggesting ways in which companies may minimize such challenges of intercultural collaboration.

Offshore Vendors’ Software Development Team Configurations

2011 ◽  
Vol 19 (3) ◽  
pp. 1-29
Author(s):  
Suranjan Chakraborty ◽  
Saonee Sarker ◽  
Sudhanshu Rai ◽  
Suprateek Sarker ◽  
Ranganadhan Nadadhur
Keyword(s):  
Software Development ◽  
Distributed Teams ◽  
Team Members ◽  
Development Team ◽  
Configuration Theory ◽  
Home Location ◽  
Distributed Team ◽  
Different Types ◽  
The One ◽  
Off Shoring

This research uses configuration theory and data collected from a major IT vendor organization to examine primary configurations of distributed teams in a global off-shoring context. The study indicates that off-shoring vendor organizations typically deploy three different types of configurations, which the authors term as thin-at-client, thick-at-client, and hybrid. These configurations differ in terms of the size of the sub-teams in the different distributed locations and the nature of the ISD-related tasks performed by the distributed team members. In addition, the different configurations were compared on their inherent process-related and resource-related flexibilities. The thick-at-client configuration emerged as the one that offers superior flexibility (in all dimensions).However, additional analysis also revealed contingencies apart from flexibility that may influence the appropriateness of the distributed ISD team configuration, including the volatility of the client organization’s environment and the extent to which the ISD tasks can be effortlessly moved to the vendor’s home location.

scholarly journals Converting Feature Types in Analysis of Different Types of Data

2020 ◽  
Vol 9 (4) ◽  
pp. 421-426 ◽  
Keyword(s):  
Pattern Recognition ◽  
Factor Analysis ◽  
Data Analysis ◽  
Software Development ◽  
Full Range ◽  
Source Information ◽  
Independent Task ◽  
Different Types ◽  
Integrated Software ◽  
Regression Correlation

Today there are the large number of methods of data analysis for solving problems of pattern recognition of regression, correlation and factor analysis, which are not applicable in the case of different types of features in the source information. In this paper we propose an approach to solving this problem, named the conversion of feature types. The conversion of feature types is considered as an independent task that allows you to make the transition from non-quantitative features to quantitative ones and in further processing to apply the full range of classical methods of data analysis. The proposed algorithm is implemented in Delphi 10 Seattle the integrated software development sphere. The result of the study was tested when solving the task of recognition of several sets of known data.

Offshore Vendors’ Software Development Team Configurations

2012 ◽  
pp. 176-204
Author(s):  
Suranjan Chakraborty ◽  
Saonee Sarker ◽  
Sudhanshu Rai ◽  
Suprateek Sarker ◽  
Ranganadhan Nadadhur
Keyword(s):  
Software Development ◽  
Distributed Teams ◽  
Team Members ◽  
Development Team ◽  
Configuration Theory ◽  
Home Location ◽  
Distributed Team ◽  
Different Types ◽  
The One ◽  
Off Shoring

This research uses configuration theory and data collected from a major IT vendor organization to examine primary configurations of distributed teams in a global off-shoring context. The study indicates that off-shoring vendor organizations typically deploy three different types of configurations, which the authors term as thin-at-client, thick-at-client, and hybrid. These configurations differ in terms of the size of the sub-teams in the different distributed locations and the nature of the ISD-related tasks performed by the distributed team members. In addition, the different configurations were compared on their inherent process-related and resource-related flexibilities. The thick-at-client configuration emerged as the one that offers superior flexibility (in all dimensions).However, additional analysis also revealed contingencies apart from flexibility that may influence the appropriateness of the distributed ISD team configuration, including the volatility of the client organization’s environment and the extent to which the ISD tasks can be effortlessly moved to the vendor’s home location.

scholarly journals “Standard Bibles” and Mediators as a Way of Software Development Organizations to Cope with the Multiplicity and Plurality of Standards

2014 ◽  
Vol 12 (2) ◽  
pp. 57-77
Author(s):  
Ronny Gey ◽  
Andrea Fried
Keyword(s):  
Software Development ◽  
Single Case ◽  
Internal Standard ◽  
Working Environment ◽  
Single Case Study ◽  
Environmental Challenges ◽  
Development Organizations ◽  
Different Types ◽  
Increasing Demand

This paper focuses on the appearance and implementation of process standards in software development organizations. In particular, it shows interest in the way organizations handle the plurality and multitude of process standards they are faced with in a modern working environment. The process how organizations respond to environmental challenges like the increasing demand for process standards we call metastructuring. Based on the metastructuring approach by Orlikowski et al. (1995) it explores the process of internal standard-use mediation by an in-depth single case study. The case company develops step by step a dedicated institutional entity reacting to standard complexity and customer pressure. As a result, mediators shape extensively the standard use of the employees in the case company. They develop a process library which integrates different standards. This work sheds light on how this metastructuring process is accomplished, which areas of metastructuring regarding process standards can be found and explore different types of metastructuring activities by the involved standard-use mediators.

scholarly journals Assessing quality in software development: An agile methodology approach

2015 ◽  
Vol 4 (2) ◽  
pp. 225
Author(s):  
V. Rodríguez-Hernández ◽  
M.C. Espino-Gudiño ◽  
J.L. González-Pérez ◽  
J. Gudiño-Bazaldúa ◽  
Victor Castano
Keyword(s):  
Software Development ◽  
Computer Science ◽  
Software Process ◽  
Field Testing ◽  
Quality Standards ◽  
Quality System ◽  
Extreme Programming ◽  
Personal Software Process ◽  
Agile Methodology ◽  
Different Types

<p>A novel methodology, result of 10 years of in-field testing, which makes possible the convergence of different types of models and quality standards for Engineering and Computer Science Faculties, is presented. Since most software-developing companies are small and medium sized, the projects developed must focuson SCRUM and Extreme Programming (XP), opposed to a RUP, which is quite heavy, as well as on Personal Software Process (PSP) and Team Software Process (TSP), which provide students with competences and a structured framework. ISO 90003:2004 norm is employed to define the processes by means of a quality system without new requirements or changing the existing ones. Also, the model is based on ISO/IEC 25000 (ISO (IEC 9126 – ISO/IEC 14598)) to allow comparing software built by different metrics.</p>

Offshoring in the Pharmaceutical Industry

2011 ◽  
pp. 93-109
Author(s):  
Jason McCoy ◽  
Johannes Sarx
Keyword(s):  
Pharmaceutical Industry ◽  
Software Development ◽  
Information Management ◽  
Financial Services ◽  
Global Sourcing ◽  
Strategic Partnerships ◽  
Pharmaceutical Firms ◽  
Exogenous Factors ◽  
Reducing Costs

Offshoring has been adopted as a tool for reducing costs and for gaining strategic advantages by financial services, software development, and other competitive industries. For a variety of reasons, the pharmaceutical industry has been slow to take advantage of the benefits that offshoring can provide. The purpose of this article is to explore the internal and exogenous factors motivating global pharmaceutical firms to increase and expand their sourcing activities. And, instead of discussing global sourcing in general, India has been analyzed as a unique and explanatory case study for this new, emerging trend. The reasons behind this decision include India’s position as a renowned global IT hub, the country’s “home grown” biotechnology and biopharmaceutical industries, the numerous strategic partnerships and offshoring relationships between global and Indian firms, as well as its significant advances in IT and information management.

Exploration and Exploitation of Developers' Sentimental Variations in Software Engineering

2016 ◽  
Vol 4 (4) ◽  
pp. 35-55 ◽  
Author(s):  
Md Rakibul Islam ◽  
Minhaz F. Zibran
Keyword(s):  
Software Engineering ◽  
Empirical Study ◽  
Software Development ◽  
Open Source ◽  
Emotional Awareness ◽  
Exploration And Exploitation ◽  
Software Artifacts ◽  
Bug Fixing ◽  
Different Types

Software development is highly dependent on human efforts and collaborations, which are immensely affected by emotions. This paper presents a quantitative empirical study of the emotional variations in different types of development activities (e.g., bug-fixing tasks), development periods (i.e., days and times) and in projects of different sizes involving teams of variant sizes. The study also includes an in-depth investigation of emotions' impacts on software artifacts (i.e., commit messages) and exploration of scopes for exploiting emotional variations in software engineering activities. This work is based on careful analyses of emotions in more than 490 thousand commit comments across 50 open-source projects. The findings from this work add to our understanding of the role of emotions in software development, and expose scopes for exploitation of emotional awareness in improved task assignments and collaborations.

scholarly journals Does Technical Debt Lead to the Rejection of Pull Requests?

2016 ◽  
Author(s):  
Marcelino Campos Oliveira Silva ◽  
Marco Tulio Valente ◽  
Ricardo Terra
Keyword(s):  
Software Development ◽  
The Other ◽  
Optimal Solutions ◽  
Technical Debt ◽  
Common Category ◽  
Different Types ◽  
Design Documentation ◽  
Is Design

Technical Debt is a term used to classify non-optimal solutions during software development. These solutions cause several maintenance problems and hence they should be avoided or at least documented. Although there are a considered number of studies that focus on the identification of Technical Debt, we focus on the identification of Technical Debt in pull requests. Specifically, we conduct an investigation to reveal the different types of Technical Debt that can lead to the rejection of pull requests. From the analysis of 1,722 pull requests, we classify Technical Debt in seven categories namely design, documentation, test, build, project convention, performance, or security debt. Our results indicate that the most common category of Technical Debt is design with 39.34%, followed by test with 23.70% and project convention with 15.64%. We also note that the type of Technical Debt influences on the size of push request discussions, e.g., security and project convention debts instigate more discussion than the other types.

Sign in / Sign up

Export Citation Format

Share Document