Data collection in global software engineering research: learning from past experience

Prikladnicki, Rafael; Boden, Alexander; Avram, Gabriela; Souza, Cleidson R. B. de; Wulf, Volker

doi:10.1007/s10664-012-9240-x

Cited by 11 publications

(8 citation statements)

References 51 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Investigating GSD work practices, we took seriously the many challenges that research in distributed software development poses [26], and we conducted extensive fieldwork at the two sites involved. We studied the IT division in a Danish financial enterprise that employs more than 20,000 people in northern Europe.…”

Section: Methodsmentioning

confidence: 99%

"Figure out how to code with the hands of others"

Matthiesen

Bjørn

Petersen

2014

Proceedings of the 17th ACM Conference on Computer Supported Cooperative Work &Amp; Social Computing

View full text Add to dashboard Cite

We report on an ethnographic study of an outsourcing global software development (GSD) setup between an Indian IT vendor and an IT development division of a Danish bank. We investigate how the local IT development work is shaped by the global setup in GSD and argue that the bank had cultural blind spots toward the changes in Denmark. Three critical issues were neglected due to the cultural blind spots: 1) increased number of interruptions, 2) lack of translucence of remote colleagues' work, and 3) the re-definition of boundaries between work and articulation work. The implications of these findings include considerations for how to organize GSD practices and prepare the organizational changes that occur when moving from a co-located software development organization to an inter-organizational geographically distributed organization. Also, our findings open up discussions about the professional identity of IT developers within GSD, including extending the qualifications for IT developers.

show abstract

Section: Methodsmentioning

confidence: 99%

"Figure out how to code with the hands of others"

Matthiesen

Bjørn

Petersen

2014

Proceedings of the 17th ACM Conference on Computer Supported Cooperative Work &Amp; Social Computing

View full text Add to dashboard Cite

show abstract

“…Focusing on the collaborative work practices I will conduct work place studies (Luff, Hindmarsh et al, 2000) and apply ethnographical approaches (Randall, Harper et al, 2010) when following one or more GSD projects from multiple locations (Prikladnicki, Boden et al, 2013). Various ethnographic data gathering techniques will be applied e.g.…”

Section: Methodsmentioning

confidence: 99%

ECSCW 2013 Adjunct Proceedings The 13th European Conference on Computer Supported Cooperative Work 21 - 25. September 2013, Paphos, Cyprus

Korn¹,

Colombino²,

Lewkowicz³

2013

DPB

View full text Add to dashboard Cite

. It comprises of the following categories: Work in Progress, workshops and master classes, demos and videos, the doctoral colloquium, and keynotes.While the proceedings published by Springer Verlag contains the core of the technical program, namely the full papers, the adjunct proceedings includes contributions on ongoing work, thus indicating what our field may become in the future.As a new thing for ECSCW 2013, the Work in Progress category has been introduced. Work in Progress is a peer-reviewed track at the conference that offers a possibility to present and discus ongoing work. Work in Progress sessions provide a unique opportunity for sharing valuable ideas, for getting early feedback on current work and preliminary results, and fostering discussions and collaborations among colleagues. Each Work in Progress submission was reviewed by a minimum of two members of the Program Committee. We were able to accept 11 papers out of a total of 19 submissions. This acceptance rate of approximately 58% acknowledges the early-stage nature of the work.The adjunct proceedings also includes three demonstrations, as well as descriptions of the 6 workshops and one master class. We have also included short descriptions of the 7 Ph.D. projects of the participants accepted for the doctoral colloquium, as well as abstracts of the two keynote lectures. {ivan.breskovic, fabiano.pinatti, susanne.schinkinger, hilda.tellioglu}@tuwien.ac.at Abstract. This paper explores the use of social awareness support as a potential solution to alleviate informal care al, and emotional load habitually associated with their duties. This is a preliminary contribution of the Vienna University of Technology to TOPIC project that is currently under development. In this paper we report on relevant literature, identify and consider technological and interaction challenges, and suggest mobile and ubiquitous computing for ambient solutions. We illustrate our approach by presenting briefly a prototype from our pre-study before concluding the paper. IntroductionIn Europe, as well as in other parts of the world, the number of people in need of special care is increasing (Magnusson et al., 2002). In the majority of the member states of the European Union family carers are responsible for more than 80% of all the care provided. Hence, both elderly and working-age family carers are submitted constantly to heavy physical, psychological, or emotional burden resulting from taking care of someone else. Past research has shown that these people are more susceptible to both psychical and physical morbidity (Chwalisz & 1 Authors are listed in alphabetical order. Kisler, 1995; Coon & Evans, 2009), facing an increased risk of mortality compared to their non-care giving counterparts (Schulz & Beach, 1999).Literature highlights that informal carers often express the need for help, not only in terms of financial assistance, as often proposed by social institutions, but also in regards to social and emotional support (Brownsell et al., 2012; Magnusson et al., 2004; ...

show abstract

“…making decisions regarding requirements are fruitless [28,33], Iss13: Asynchronous correspondence leads to deferment in proliferation and resolution of issues [102], Iss14: If there are synchronous meetings amid the locations which have substantial differences regarding time then participants belonging to some locations are bothered as there are huge differences between the meeting times and their local working times [40,[102][103], Iss15: Shareholders are not able to express in the correspondence language [33], Iss16: Electronic correspondence alike email permits clandestine correspondence that generates complications for settling clashes regarding requirements [33], Iss17: Shareholders don't convey to one another adequately, instead seek to apply force and utilize influence on one another [102], Iss18: To illuminate and resolve the issues, any coworker may correspond with any shareholder that may cause tedious debates and additional controlling endeavors [104], Iss19: Correspondence gaps or postponements amid RE because of individuality conflicts [105], Iss20: Online correspondence to elucidate requirements prompts spiny requirements because resulting requirements are uncertain, alter again and again or are unfinished [106], Iss21: To arrange interviews, acquiring the assent of far off shareholders [107], Iss22: Typically, there is non-recording of the promises that are done amid videoconferencing or discussions on the telephone, consequently such pledges cannot be alluded when needed [Proposed].…”

Section: Plos Onementioning

confidence: 99%

“…requirements as fast as needed [112,116], Iss37: Functioning on the outdated requirements [111,117], Iss38: Hitches in accessibility of the steady data because of the dissemination of sources [118], Iss39: Scarcity of the mindfulness regarding deployment environment may cause ambiguity in requirements [94], Iss40: Unfamiliarity to the background and significance of requirements can cause project postponements and quality tradeoffs [119], Iss41: Requirements illuminations are passed on later than expected time which can cause project postponements [111], Iss42: Incapability to share information or finest practices [28,120] iii. Cultural diversities' issues, Iss47: Detachment leads to cultural variances amongst the different working departments belonging to an organization which produces difficulty in achieving the shared awareness about the requirements [33,102], Iss48: Generating trust amongst the different shareholders is demanding [33,107,[122][123][124][125], Iss49: Upholding trust amongst the different shareholders is demanding [123,125], Iss50: Scarcity of trust amongst the different shareholders [17,93,107,[122][123]126], Iss51: Evasion of the obligations from the different shareholders [94], Iss52: Forfeiture of attachment amongst the shareholders on account of physical dispersal [127], Iss53: Complications in attaining consent on requirements [30,40,94,128], Iss54: Shareholders originate from miscellaneous social backgrounds and own dissimilar moral standards regarding hierarchies, addressing risks, tracking timetables and promptness that can intensify disagreements [94], Iss55: Various cul...…”

Section: Plos Onementioning

confidence: 99%

Requirements engineering issues causing software development outsourcing failure

et al. 2020

View full text Add to dashboard Cite

Software development outsourcing is becoming more and more famous because of the advantages like cost abatement, process enhancement, and coping with the scarcity of needed resources. Studies confirm that unfortunately a large proportion of the software development outsourcing projects fails to realize anticipated benefits. Investigations into the failures of such projects divulge that in several cases software development outsourcing projects are failed because of the issues that are associated with requirements engineering process. The objective of this study is the identification and the ranking of the commonly occurring issues of the requirements engineering process in the case of software development outsourcing. For this purpose, contemporary literature has been assessed rigorously, issues faced by practitioners have been identified and three questionnaire surveys have been organized by involving experienced software development outsourcing practitioners. The Delphi technique, cutoff value method and 50% rule have also been employed. The study explores 150 issues (129 issues from literature and 21 from industry) of requirements engineering process for software development outsourcing, groups the 150 issues into 7 identified categories and then extricates 43 customarily or commonly arising issues from the 150 issues. Founded on 'frequency of occurrence' the 43 customarily arising issues have been ranked with respect to respective categories (category-wise ranking) and with respect to all the categories (overall ranking). Categories of the customarily arising issues have also been ranked. The issues' identification and ranking contribute to design proactive software project management plan for dealing with software development outsourcing failures and attaining conjectured benefits of the software development outsourcing.

show abstract

Data collection in global software engineering research: learning from past experience

Cited by 11 publications

References 51 publications

"Figure out how to code with the hands of others"

"Figure out how to code with the hands of others"

ECSCW 2013 Adjunct Proceedings The 13th European Conference on Computer Supported Cooperative Work 21 - 25. September 2013, Paphos, Cyprus

Requirements engineering issues causing software development outsourcing failure

Contact Info

Product

Resources

About