Key challenges of finding right skilled resources and the cost arbitrage factors have made distributed software development indispensable for quite some time now. The success stories of many offshore service providers particularly from India underlines the fact that this is working well in a "hands-free" mode, especially for projects following traditional development life cycles. The recent trend is an increase in the number of organizations adopting agile methodologies to tackle the challenges of requirements volatility and shorter time to market. However, the concept of a collocated team which is central to agile does not easily translate to distributed development. This paper captures our experience at Wipro in handling Distributed Agile projects. We discuss a validated model to make a smooth transition from a collocated to a distributed scenario in agile projects. We also share the lessons learnt and best practices that we have gained in implementing this model.
{"title":"Adopting Agile in Distributed Development","authors":"Kalpana Sureshchandra, J. J. Shrinivasavadhani","doi":"10.1109/ICGSE.2008.25","DOIUrl":"https://doi.org/10.1109/ICGSE.2008.25","url":null,"abstract":"Key challenges of finding right skilled resources and the cost arbitrage factors have made distributed software development indispensable for quite some time now. The success stories of many offshore service providers particularly from India underlines the fact that this is working well in a \"hands-free\" mode, especially for projects following traditional development life cycles. The recent trend is an increase in the number of organizations adopting agile methodologies to tackle the challenges of requirements volatility and shorter time to market. However, the concept of a collocated team which is central to agile does not easily translate to distributed development. This paper captures our experience at Wipro in handling Distributed Agile projects. We discuss a validated model to make a smooth transition from a collocated to a distributed scenario in agile projects. We also share the lessons learnt and best practices that we have gained in implementing this model.","PeriodicalId":340054,"journal":{"name":"2008 IEEE International Conference on Global Software Engineering","volume":"519 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116254326","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Distributing development tasks in the context of global software development bears both many risks and many opportunities. Nowadays, distributed development is often driven by only a few factors or even just a single factor such as workforce costs. Risks and other relevant factors such as workforce capabilities, the innovation potential of different regions, or cultural factors are often not recognized sufficiently. This could be improved by using empirically-based multi-criteria distribution models. Currently, there is a lack of such decision models for distributing software development work. This article focuses on mechanisms for such decision support. First, requirements for a distribution model are formulated based on needs identified from practice. Then, distribution models from different domains are surveyed, compared, and analyzed in terms of suitability. Finally, research questions and directions for future work are given.
{"title":"Towards a Multi-criteria Development Distribution Model: An Analysis of Existing Task Distribution Approaches","authors":"Ansgar Lamersdorf, J. Munch, D. Rombach","doi":"10.1109/ICGSE.2008.15","DOIUrl":"https://doi.org/10.1109/ICGSE.2008.15","url":null,"abstract":"Distributing development tasks in the context of global software development bears both many risks and many opportunities. Nowadays, distributed development is often driven by only a few factors or even just a single factor such as workforce costs. Risks and other relevant factors such as workforce capabilities, the innovation potential of different regions, or cultural factors are often not recognized sufficiently. This could be improved by using empirically-based multi-criteria distribution models. Currently, there is a lack of such decision models for distributing software development work. This article focuses on mechanisms for such decision support. First, requirements for a distribution model are formulated based on needs identified from practice. Then, distribution models from different domains are surveyed, compared, and analyzed in terms of suitability. Finally, research questions and directions for future work are given.","PeriodicalId":340054,"journal":{"name":"2008 IEEE International Conference on Global Software Engineering","volume":"27 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125568652","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Increased popularity of global software engineering (GSE) has resulted in quite a number of research and industrial studies. As the area matures, an increased focus on empirically supported results leads to a greater potential impact on future research and industrial practice. However, since GSE scenarios are diverse, what works in one context might not directly apply in another. Thus it is necessary to understand, how GSE-related empirical findings should be reported to be useful for practitioners and researchers. Furthermore, itdasias important to summarize progress and get the big picture of published research to identify gaps and commonalities. In this paper we analyze differentiating factors of GSE scenarios and offer a classification scheme for describing the context of a GSE study. In addition, we report initial results of a systematic review on GSE-related empirical literature using papers from ICGSE 2006 and 2007, at the same time illustrating and evaluating the proposed scheme.
{"title":"Reporting Empirical Research in Global Software Engineering: A Classification Scheme","authors":"Darja Šmite, C. Wohlin, R. Feldt, T. Gorschek","doi":"10.1109/ICGSE.2008.22","DOIUrl":"https://doi.org/10.1109/ICGSE.2008.22","url":null,"abstract":"Increased popularity of global software engineering (GSE) has resulted in quite a number of research and industrial studies. As the area matures, an increased focus on empirically supported results leads to a greater potential impact on future research and industrial practice. However, since GSE scenarios are diverse, what works in one context might not directly apply in another. Thus it is necessary to understand, how GSE-related empirical findings should be reported to be useful for practitioners and researchers. Furthermore, itdasias important to summarize progress and get the big picture of published research to identify gaps and commonalities. In this paper we analyze differentiating factors of GSE scenarios and offer a classification scheme for describing the context of a GSE study. In addition, we report initial results of a systematic review on GSE-related empirical literature using papers from ICGSE 2006 and 2007, at the same time illustrating and evaluating the proposed scheme.","PeriodicalId":340054,"journal":{"name":"2008 IEEE International Conference on Global Software Engineering","volume":"10 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127071716","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
In this paper, we describe a preliminary capability model that captures patterns of evolution in the practice of distributed software development in internal offshoring projects. In our research we seek to understand how the practices of organizations involved in the internal offshoring of software development evolve over time, from a software engineering perspective, and from the point of view of the subsidiaries. Based on a combination of qualitative and quantitative methods, we propose a capability model that encompasses the evolution of software development activities within and among several subsidiaries owned by an organization.
{"title":"Patterns of Evolution in the Practice of Distributed Software Development in Wholly Owned Subsidiaries: A Preliminary Capability Model","authors":"R. Prikladnicki, D. Damian, J. Audy","doi":"10.1109/ICGSE.2008.36","DOIUrl":"https://doi.org/10.1109/ICGSE.2008.36","url":null,"abstract":"In this paper, we describe a preliminary capability model that captures patterns of evolution in the practice of distributed software development in internal offshoring projects. In our research we seek to understand how the practices of organizations involved in the internal offshoring of software development evolve over time, from a software engineering perspective, and from the point of view of the subsidiaries. Based on a combination of qualitative and quantitative methods, we propose a capability model that encompasses the evolution of software development activities within and among several subsidiaries owned by an organization.","PeriodicalId":340054,"journal":{"name":"2008 IEEE International Conference on Global Software Engineering","volume":"45 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131450192","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
With a very short time frame in mind we were commissioned to build a service solution that encompassed over 430 requirements. Given expertise, skills, time and budget constraints we had to search for resources around the world and assembled a team of more than 40 people in 7 locations across 6 different time zones. We chose state of the art architecture and development paradigms such as Service Oriented Architecture (SOA) and iterative development to facilitate the service capabilities between components and teams and to continuously refine our approach from iteration to iteration. In this paper we identify some of the challenges we faced and describe how we addressed them in subsequent iterations. The aggregate of our improvements constitutes a set of best practices that we recommend for future engagements of this type and suggestions for new tooling to support these activities.
{"title":"Continuous Improvement through Iterative Development in a Multi-Geography","authors":"Jim Laredo, R. Ranjan","doi":"10.1109/ICGSE.2008.13","DOIUrl":"https://doi.org/10.1109/ICGSE.2008.13","url":null,"abstract":"With a very short time frame in mind we were commissioned to build a service solution that encompassed over 430 requirements. Given expertise, skills, time and budget constraints we had to search for resources around the world and assembled a team of more than 40 people in 7 locations across 6 different time zones. We chose state of the art architecture and development paradigms such as Service Oriented Architecture (SOA) and iterative development to facilitate the service capabilities between components and teams and to continuously refine our approach from iteration to iteration. In this paper we identify some of the challenges we faced and describe how we addressed them in subsequent iterations. The aggregate of our improvements constitutes a set of best practices that we recommend for future engagements of this type and suggestions for new tooling to support these activities.","PeriodicalId":340054,"journal":{"name":"2008 IEEE International Conference on Global Software Engineering","volume":"36 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125081478","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Present-day software engineering combines technical and social skills, as well as collaboration among people with different backgrounds (e.g. due to global development and outsourcing). In this paper we address the problem of teaching "globally distributed development", and specifically software design. Our goal is to develop a joint Master course teaching software design in a global setting. To this end, we contribute with a list of characteristics to be developed, in the form of an 'orientation map' for educators. We use this map to build a joint course between two European universities.
{"title":"Developing a Course on Designing Software in Globally Distributed Teams","authors":"P. Lago, H. Muccini, M. Babar","doi":"10.1109/ICGSE.2008.26","DOIUrl":"https://doi.org/10.1109/ICGSE.2008.26","url":null,"abstract":"Present-day software engineering combines technical and social skills, as well as collaboration among people with different backgrounds (e.g. due to global development and outsourcing). In this paper we address the problem of teaching \"globally distributed development\", and specifically software design. Our goal is to develop a joint Master course teaching software design in a global setting. To this end, we contribute with a list of characteristics to be developed, in the form of an 'orientation map' for educators. We use this map to build a joint course between two European universities.","PeriodicalId":340054,"journal":{"name":"2008 IEEE International Conference on Global Software Engineering","volume":"16 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122454261","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Globally distributed software development poses substantial risks to project and product management. Not all eventualities can however be buffered, because in the global economy, developing and implementing products must be fast, cost effective and adaptive to changing needs. Therefore, there is a need to utilize different techniques to effectively and efficiently mitigate risks. This article systematically introduces risk management in global software engineering (GSE) for development projects and product evolution. Methods include using basic project, supplier and quality management techniques, process frameworks (e.g., CMMI), product life-cycle management, effective communication processes, SLA based escalation, competence management, and innovation management. A longitudinal empirical field study over several years from a captive SW center of a worldwide leading ICT company in India provides practical experiences and indicates how to effectively apply GSE risk management practices.
{"title":"Managing Risks in Global Software Engineering: Principles and Practices","authors":"C. Ebert, B. K. Murthy, Namo Narayan Jha","doi":"10.1109/ICGSE.2008.12","DOIUrl":"https://doi.org/10.1109/ICGSE.2008.12","url":null,"abstract":"Globally distributed software development poses substantial risks to project and product management. Not all eventualities can however be buffered, because in the global economy, developing and implementing products must be fast, cost effective and adaptive to changing needs. Therefore, there is a need to utilize different techniques to effectively and efficiently mitigate risks. This article systematically introduces risk management in global software engineering (GSE) for development projects and product evolution. Methods include using basic project, supplier and quality management techniques, process frameworks (e.g., CMMI), product life-cycle management, effective communication processes, SLA based escalation, competence management, and innovation management. A longitudinal empirical field study over several years from a captive SW center of a worldwide leading ICT company in India provides practical experiences and indicates how to effectively apply GSE risk management practices.","PeriodicalId":340054,"journal":{"name":"2008 IEEE International Conference on Global Software Engineering","volume":"174 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123203184","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
In distributed software development, effective reviews of analysis documents lead to increased correctness of analysis results. When managed without tool support, such reviews lead to ineffective usage of time and effort and possibly even delay the project. Also going ahead without reviews completed, implies risks of incorrect or incomplete features. In this paper we contrast the manual process we used to follow to organize distributed software reviews and the process with DOCTOR to show how it greatly improves the process of distributed software reviews. We also attempt to provide a projection in terms of cost of efforts saved and the resultant increase in productivity. We also compare DOCTOR with other Web-based tools and project its advantages and disadvantages. We hope to convince readers who haven't adopted tool based support for distributed reviews by this paper on the clear advantages of the same.
{"title":"Ailments of Distributed Document Reviews and Remedies of DOCTOR (DOCument Tree ORganizer Tool) with Distributed Reviews Support","authors":"T. V. Krishnamurthy, Sapna Subramani","doi":"10.1109/ICGSE.2008.8","DOIUrl":"https://doi.org/10.1109/ICGSE.2008.8","url":null,"abstract":"In distributed software development, effective reviews of analysis documents lead to increased correctness of analysis results. When managed without tool support, such reviews lead to ineffective usage of time and effort and possibly even delay the project. Also going ahead without reviews completed, implies risks of incorrect or incomplete features. In this paper we contrast the manual process we used to follow to organize distributed software reviews and the process with DOCTOR to show how it greatly improves the process of distributed software reviews. We also attempt to provide a projection in terms of cost of efforts saved and the resultant increase in productivity. We also compare DOCTOR with other Web-based tools and project its advantages and disadvantages. We hope to convince readers who haven't adopted tool based support for distributed reviews by this paper on the clear advantages of the same.","PeriodicalId":340054,"journal":{"name":"2008 IEEE International Conference on Global Software Engineering","volume":"148 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128444417","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
O. Gotel, V. Kulkarni, C. Scharff, Long Chrea Neak
Since 2005, Pace University, Delhi University and the Institute of Technology of Cambodia have been partnering to offer students the opportunity to work on globally distributed software development projects. The innovative collaborative model has evolved towards an emphasis on technology mashups for development and communication, mentoring and auditing for assuring quality, and team and software integration for right-sourcing. This paper describes a project where students working in sub-teams were required to integrate their sub-components as a single system for a Cambodian environment. Furthermore, a well-defined design sub-component was subject to a competitive bidding process in an attempt to enhance quality though design diversity. The paper reports on our findings and summarizes the dos and don'ts associated with integration. Both team and software integration needs careful attention from day one on a project, a finding that has repercussions for educational and industrial practice.
{"title":"Integration Starts on Day One in Global Software Development Projects","authors":"O. Gotel, V. Kulkarni, C. Scharff, Long Chrea Neak","doi":"10.1109/ICGSE.2008.10","DOIUrl":"https://doi.org/10.1109/ICGSE.2008.10","url":null,"abstract":"Since 2005, Pace University, Delhi University and the Institute of Technology of Cambodia have been partnering to offer students the opportunity to work on globally distributed software development projects. The innovative collaborative model has evolved towards an emphasis on technology mashups for development and communication, mentoring and auditing for assuring quality, and team and software integration for right-sourcing. This paper describes a project where students working in sub-teams were required to integrate their sub-components as a single system for a Cambodian environment. Furthermore, a well-defined design sub-component was subject to a competitive bidding process in an attempt to enhance quality though design diversity. The paper reports on our findings and summarizes the dos and don'ts associated with integration. Both team and software integration needs careful attention from day one on a project, a finding that has repercussions for educational and industrial practice.","PeriodicalId":340054,"journal":{"name":"2008 IEEE International Conference on Global Software Engineering","volume":"39 2 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130388586","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Globally distributed software development teams face extraordinary communication and coordination problems due to spatial, temporal, and cultural separation between team members. Using the dyadic model of coordination, the paper proposes a coordination index that encapsulates the coordination difficulties in global software development. The coordination index is derived from four other indices-coupling index, need index, effectiveness index, and time-zone index. While a discrete-event simulation model is used to determine the time-zone index for all possible temporal separations, two rounds of questionnaire surveys were administered among researchers and practitioners world-wide to determine the need and the effectiveness indices. The important factors affecting inter-site coordination were short-listed after the first round. In the second round, weights were assigned to the short-listed factors by making a pair-wise comparison between them. The paper also demonstrates how the coordination index, so derived, can be used for a few project planning decisions.
{"title":"Developing an Inter-site Coordination Index for Global Software Development","authors":"P. Mohapatra","doi":"10.1109/ICGSE.2008.30","DOIUrl":"https://doi.org/10.1109/ICGSE.2008.30","url":null,"abstract":"Globally distributed software development teams face extraordinary communication and coordination problems due to spatial, temporal, and cultural separation between team members. Using the dyadic model of coordination, the paper proposes a coordination index that encapsulates the coordination difficulties in global software development. The coordination index is derived from four other indices-coupling index, need index, effectiveness index, and time-zone index. While a discrete-event simulation model is used to determine the time-zone index for all possible temporal separations, two rounds of questionnaire surveys were administered among researchers and practitioners world-wide to determine the need and the effectiveness indices. The important factors affecting inter-site coordination were short-listed after the first round. In the second round, weights were assigned to the short-listed factors by making a pair-wise comparison between them. The paper also demonstrates how the coordination index, so derived, can be used for a few project planning decisions.","PeriodicalId":340054,"journal":{"name":"2008 IEEE International Conference on Global Software Engineering","volume":"33 3 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116148564","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：