Authors: John Noll, Sarah Beecham , and I ta Richardson Pr e se - - PowerPoint PPT Presentation

authors
SMART_READER_LITE
LIVE PREVIEW

Authors: John Noll, Sarah Beecham , and I ta Richardson Pr e se - - PowerPoint PPT Presentation

Global software Development and Collaboration: Barriers and Solutions Authors: John Noll, Sarah Beecham , and I ta Richardson Pr e se nte r : Kasahun Abdisa IT Doc tor al pr ogr am Addis Ababa University e-mail:


slide-1
SLIDE 1

1

“Global software Development and Collaboration: Barriers

and Solutions”

Authors:

John Noll, Sarah Beecham , and I ta Richardson

Pr e se nte r : Kasahun Abdisa IT Doc tor al pr

  • gr

am

Addis Ababa University

e-mail: kasabd97@gmail.com

slide-2
SLIDE 2

Outlines

 Overview  Introduction  Purpose of the paper  Research questions  Context  Research Method  Result of the study  Limitation of the study  Conclusion  Future Direction

2

slide-3
SLIDE 3

3

Overview

 Global Software Development (GSD): is the

process of developing software in globally distributed environment

 GSD has various advantages to organizations  Currently, it is common for developers to

collaborate from various sites while developing a software systems.

 However, this collaboration is accompanied by

various challenges mainly:

 collaboration barriers experienced by stakeholders of that

  • rganization participating in the system development
slide-4
SLIDE 4

4

Purpose of the study

 To clearly understand potential barriers to

collaboration in GSD

 to pin point specific practices that show how

  • rganizations can overcome these barriers

 To contributes to the GSD body of knowledge

 by refining empirical findings  in identifying the best ways to address the problems in

GSD

slide-5
SLIDE 5

5

Introduction

 Current global economy demands software

engineers to operate in a globally distributed environment.

 Distributed environment is characterized by

different

geographic, temporal, cultural and linguistic difference

 Limited developers physical interaction  Limited shared understanding among the developers

 The existing CMMI process models can not address this GSD

challenges

slide-6
SLIDE 6

Introduction…..cont

 Four practices associated with GSD collaboration;

 These are collaboratively :

  • 1. Identify common goals, objectives and rewards.
  • 2. Establish and maintain the work product ownership,

boundaries among interfacing locations.

  • 3. Establish and maintain interfaces and processes for the

exchange of inputs, outputs, or work products.

  • 4. Develop, communicate and distribute among interfacing

teams the commitment lists and work plans that are related to the work product or team interfaces.

  • However, there are ,many factors that impede
  • rganizations to implement these four practices in

GSD

6

slide-7
SLIDE 7

Introduction…..cont

 But why GSD? what drives it?  GSD choice is attributed to:

 highly skilled software engineers in low cost

locations

 Bringing software development close to

emerging markets(consumers)

7

slide-8
SLIDE 8

8

Research questions

 The aim of the study is to better

understand barriers and solutions to GSD

 In doing so, the paper undertook survey

  • f the GSD literature that addresses two

research questions:

 What barriers prevent software development

teams from effectively collaborating in a global environment?

 And, what solutions address these barriers to

collaboration?

slide-9
SLIDE 9

9

Context of the problem

 The study was conducted within the context of virtual teams

and virtual organization

 When we talk about virtual organizations we refer to Virtual

team Virtual Team s VS Traditional Team

 Traditional team

 group of individuals who are collocated and interdependent in their

tasks

 Coordinate activity and share responsibility to achieve goal

 Virtual teams

 Same as traditional team  But operate across different

  • geographic, temporal, organizational
  • multicultural, multilingual environment boundaries .
slide-10
SLIDE 10

10

Context…

I m plem entation of a virtual team strategy

The center of the strategy is “cost-based decision”

Aims at linking technical skills and experience of staff located in a high-cost centre with engineers in a low-cost location.

 short-term strategy

 used simply as a knowledge transfer exercise(training, experience

sharing)

 long-term objective

 sustained support will be required for team members at all locations

Factors that dictate choice of remote site

access to local knowledge

 or proximity to the customer base 

Virtual team

 geographically distributed teams with task interdependence . 

Distributed team

 geographically distributed teams but with no task interdependence

slide-11
SLIDE 11

11

The Global Teaming Model(GTM)

 successful software project management is a function of:  effective planning, organizing, staffing, leading, controlling

coordinating and day-to-day management of the project

 Is constrained by factors like

 available resources(financial and technological)  management  personnel and technical capabilities

 Project management becomes more complex in GSD due to  Management of virtual team across the site  coordinating their task 

language, culture

project coordination , control and visibility problems

GSD challenges cannot be dealt with structured process models like CMMI

slide-12
SLIDE 12

12

GTM……cont

Introduced to provide process guidance to organizations embarking

  • n a GSD effort and fill the gap of CMMI

has two specific goals:

 “Define Global Project Management” and

“Define Management Between Locations.”

slide-13
SLIDE 13

13

Research Methods

 The study employed Systematic review using

B.Kitchenham guidelines with the following steps

1.

Identify the need for a systematic literature review

2.

Carry out a search for relevant studies

3.

Formulate review research question(s)

4.

Assess and record the quality of included studies

5.

Classify data needed to answer the research question(s)

6.

Extract data from each included study

7.

Summarize and synthesize study results (meta-analysis)

8.

Interpret results to determine their applicability

9.

Write-up study as a report

slide-14
SLIDE 14

14

Research method….cont

I tem s Description Need for the review

No comprehensive survey so far in software engineering literature that address the research questions

Research Questions

RQ1: What are the barriers that prevent software development teams from collaborating in a global environment? RQ2: What solutions are there to addressing the barriers to collaboration, as identified in the literature?

Search

String: “Global Software Development” AND “Collaboration” Boolean search

Source : …

IEEEXplore bibliographic database

Result: 32 references returned ; 6 non relevant; hence 26 final list

Docum ent Selection

The follow ing inclusion and exclusion criteria used to filter paper for analysis

  • 1. Directly answ er either ( or both) of our research questions
  • 2. W ere published betw een January, 2000 and October, 2009
  • 3. W ere em pirical studies
  • 4. W ere full research papers published in a journal or conference

proceedings

slide-15
SLIDE 15

15

Research method….cont

I tem s Description Data Extraction, Meta-analysis, and Interpretation

Each paper is examined to extract :

  • Study aims or research question
  • Identified barriers to collaboration
  • Identified solutions to the barriers
  • Other results relevant to the study
  • Potential themes emerging from the study’s

conclusions

Results

Analysis of 26 papers revealed various barriers to GSD and various solutions to overcome

slide-16
SLIDE 16

16

Result

 Analyzed 26 selected papers and spotted both barriers and

solution to GSD

  • 1. Barriers

 The study reported Eight basic barrier category to the four

collaboration practices enumerated in GTM as follows:

 geographic distance  temporal distance (different time zones )  differences in language and culture 

fear and trust

 problems stemming from organizational structure,  process issues 

infrastructure barrier

product architecture barrier.

slide-17
SLIDE 17

17

Result…(Barrier )….cont

Barrier Description

Geographic Distance

No informal contact No personal relationships  no “awareness” of remote teams participating on Global project Affect shared understanding about issues like requirements Also increases organizational complexity

Temporal Distance

different time zones Result in fewer hours of work day for synchronous meeting delay in response to asynchronous communication Result in mean delay of 2.5 times that of collocated[ 21]

Culture and Language

Teams not confident in language prefer instant message than interacting directly with users over phone or others Instant message: No visual (auditory)interaction to understand each Limit teams idea expression Feel being dominated Shift to asynchronous Language interpretation problem(eg polite) due to culture affects interpretation of requirements(domain context)

Fear and Trust

lack of informal face-to-face Result in no personal relationship Leads to lack of trust fearful of their job security Mistrust of management motives a negative impression of the remote team’s competence when something misses or is late

slide-18
SLIDE 18

18

Result…(Barrier) ….cont

Barrier Description Organization, Process, and Managem ent

Lack of informal communication about process changes change management might be applied differently at some sites I ncompatible process at different sites

I nfrastructure

I nstant failure of infrastructures are consequential E.g. disruption of telephone,internet,video conference weak knowledge management infrastructure problem I ncompatible data repositories (risk of data loss when data moves from one source to the other)

Product Architecture

Architecture that changes frequently and not communicated Lead to system integration problem at the end Some times ownership competition may happen among teams(for high visible systems)

slide-19
SLIDE 19

19

Result…solution…cont

2.Solution

 The survey also proposed solutions to the identified barriers  Classified into the following solution areas as:

 address language and cultural differences;  promoting trust and overcoming fear;  improving communication infrastructure;  management interventions;  Organizational structures;  addressing distributed development process

issues;

 appropriate product architecture

slide-20
SLIDE 20

20

Result…(solution)…cont

Barrier Solution Culture and Language

native speakers should help in reviewing docs written by non native speakers of shared language I nvest in shared organizational culture (shared vision, process) Encourage understanding of different cultures Mixing Cultural ambassadors from site to site

I nfrastructure

Choose synchronous communication for issues that need discussion for agreement Consider culture, language and cognitive learning skills when choosing communication

Managem ent

Should make strategic decision in GSD Should workout the Cost benefit analysis Barriers are risks hence demands management to make careful balance of decisions in GSD

Organization

Should reduce communication complexities among sites Choose responsibility in the way it reduce communication b/ n sites Assign tasks that demand few communication with main development t activity Make the sites near to independent if possible Choose site in the same time zone to solve temporal issue

slide-21
SLIDE 21

21

Result…(solution)…cont

Barrier Solution Fear and Trust arrange face-to-face meetings Built personal relationship Share what various teams are doing to the

  • thers using different platforms

Product Architecture Implement modular product structure Identify functionality that can be developed at single site Try stable architecture as it enhances clear task allocation, responsibility and integration Process All sites should follow shared and agreed on process Also use specific process to handle temporal delays Eg process that respond immediately to specific enquiries Introduce process that frequently iterate and get updated

slide-22
SLIDE 22

22

Discussion

 This paper started the discussion by pin pointing four

practice that are the core of the GSD

  • 1. I dentifying common goals, objectives, and rewards
  • 2. Collaboratively establish product ownership
  • 3. Collaboratively establish interfaces and processes
  • 4. Collaboratively develop work plans

 Each of these practice is highly dependent on communication

among the sites :

For shared understanding among the teams

to achieve goal

Establish trust

slide-23
SLIDE 23

23

Discussion…

 Issues that arise in relation to these four practice in the paper

are

Geographic and temporal distance

Cultural differences

Temporal distance

 Problems associated with these issues in GSD will result in

Delays

lack of trust

lack of shared understanding

I ncompatible process

 Which ultimately impact the actual and perceived

performance of the GSD activities

slide-24
SLIDE 24

Limitation of the study

 The researchers are not sure whether some of

the papers used in this study undergo external validity

 The papers included for this study are case study

papers

but depended on one or two case study for their finding

 The way the search key constructed might have

limited number of papers to be included in the study

 Used only one library(IEEEXplore) as a metadata

24

slide-25
SLIDE 25

25

Conclusion

 This study used GTM collaboration as a basic of

its discussion

 The paper posed two research questions from the

  • utset

 Employed SLR to answer Research question and

figured out both barriers and solution from literature

 For the first research question “RQ1: What are the barriers that prevent software development teams from collaborating in a global environment?”  Identified eight categories of barriers

slide-26
SLIDE 26

26

Conclusion…..

 For the second research question

“ RQ2 : W hat solutions are there to addressing the barriers to collaboration, as identified in the literature?

 Seven categories of answers indentified  They are solution to the first identified barriers

slide-27
SLIDE 27

Lesson Learned

 How to pose research questions  How to undertake SLR to match the

research question

 How to set criteria to filter quality papers

that match our research question

 How to analyze and synthesize literatures

in SLR

27

slide-28
SLIDE 28

28

Future Directions

 The study recommends to apply the” global

software development model of open source software projects “ to this conventional GSD

 The researcher hints that

“understanding open source projects’ organizational, process,

and infrastructure will be useful to develop mature Process Model to solve conventional GSD”

slide-29
SLIDE 29

29