{"title":"Some Reasons Why Actual Cross-Fertilization in Cross-Functional Agile Teams Is Difficult","authors":"Helena Barke, L. Prechelt","doi":"10.1145/3195836.3195839","DOIUrl":"https://doi.org/10.1145/3195836.3195839","url":null,"abstract":"Background: Agile teams are supposed to be cross-functional in order to be complete (so they can work without external help). Cross-functionality is also supposed to produce cross-fertilization: Better ideas and solutions, problems prevented or detected earlier, etc. Question: What is motivating or demotivating team members to work in a cross-functional manner? Method: We conceptualize observations from five agile teams (work observations, interviews, group discussion) and from interviews with five agile consultants/ coaches by applying Grounded Theory Methodology. Results: The inclination to interact cross functionally is moderated by at least six factors such as perceived inefficiency, a sense of responsibility for one's own functional domain, or the difficulty to find a level of detail that is suitable for the collaboration. Conclusion: Cross-fertilization is harder to get than one might expect and teams need to develop good judgment to succeed at it.","PeriodicalId":295164,"journal":{"name":"2018 IEEE/ACM 11th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)","volume":"2 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-05-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128279137","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}
{"title":"On Gender, Ethnicity, and Culture in Empirical Software Engineering Research","authors":"Lucas Gren","doi":"10.1145/3195836.3195837","DOIUrl":"https://doi.org/10.1145/3195836.3195837","url":null,"abstract":"This note highlights the importance of investigating diversity aspects in combination in empirical research. It draws on the psychological discourse and suggests why and how software engineering scholars can use the aspect of diversity in all their research endeavors.","PeriodicalId":295164,"journal":{"name":"2018 IEEE/ACM 11th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)","volume":"23 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-05-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129008234","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}
E. Bjarnason, Baldvin Gislason Bern, Linda Svedberg
{"title":"A Case Study of Distances in a Large Co-Located Software Development Organisation","authors":"E. Bjarnason, Baldvin Gislason Bern, Linda Svedberg","doi":"10.1145/3195836.3195846","DOIUrl":"https://doi.org/10.1145/3195836.3195846","url":null,"abstract":"Communication and collaboration is a major challenge for large-scale software development. Cognitive and psychological distance between individuals and teams affect this collaboration and can cause communications gaps. We propose a novel method for assessing distance between teams, and explore potential explanations for these distances. In an exploratory case study of the quality assurance department at Axis Communications, we used interactive posters to collect data and obtained a 52% response rate from the 175 test engineers. We identified low psychological distance as an indicator of a company culture with open and frequent communication, and of a team with good social networking skills and well-functioning points of contact. We found that low cognitive distance is an indicator of differences regarding the responsibilities of a team; within the same system and between different types of systems. We also found correlations between psychological and cognitive distance. Large organisations may apply our concept to assess distance between teams, and our finding can be useful in interpreting these distances. Furthermore, our results provide a basis for further research on how the concept of distances can be used to assess collaboration within large organisations.","PeriodicalId":295164,"journal":{"name":"2018 IEEE/ACM 11th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)","volume":"72 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-05-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126304393","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}
Souti Chattopadhyay, Nicholas Nelson, Thien Nam, McKenzie Calvert, A. Sarma
{"title":"Context in Programming: An Investigation of How Programmers Create Context","authors":"Souti Chattopadhyay, Nicholas Nelson, Thien Nam, McKenzie Calvert, A. Sarma","doi":"10.1145/3195836.3195861","DOIUrl":"https://doi.org/10.1145/3195836.3195861","url":null,"abstract":"A programming context can be defined as all the relevant information that a developer needs to complete a task. Context comprises information from different sources and programmers interpret the same information differently based on their programming goal. In fact, the same artifact may create a different context when revisited. Context, therefore, by its very nature is a \"slippery notion.\" To understand how people create context we observed six programmers engaged in exploratory programming and performed a qualitative analysis of their activities. We observe that the interactions with artifacts and a mapping of meaning from those artifacts for a programming activity determines how one creates context.","PeriodicalId":295164,"journal":{"name":"2018 IEEE/ACM 11th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)","volume":"31 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-05-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115422614","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}
{"title":"Leveraging Motivational Theories for Designing Gamification for RE","authors":"Naomi Unkelos-Shpigel, I. Hadar","doi":"10.1145/3195836.3195843","DOIUrl":"https://doi.org/10.1145/3195836.3195843","url":null,"abstract":"Requirement engineering (RE) presents several challenges stemming from the required collaboration and knowledge transfer between analysists, developers and customers. Motivation theories have been used occasionally to analyze and encourage motivation and engagement of stakeholders in RE tasks. In recent years, gamification techniques have been used in software engineering tasks, and in some cases, in RE tasks in order to promote stakeholder engagement. This paper presents a preliminary literature review that was conducted in order to model correlations documented in literature between RE tasks, stakeholder motivation and engagement, and gamification. The preliminary findings show promise for conducting a full systematic literature review (SLR) in order to complete modeling existing evidence-based literature. The SLR and the emergent model will set the grounds for a research agenda toward an exhaustive model that will offer guidance for designing gamified environments for different RE tasks, based on motivational and behavioral factors.","PeriodicalId":295164,"journal":{"name":"2018 IEEE/ACM 11th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)","volume":"45 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-05-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114214410","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}
{"title":"Diversity in Software Engineering","authors":"Álvaro Menezes, R. Prikladnicki","doi":"10.1145/3195836.3195857","DOIUrl":"https://doi.org/10.1145/3195836.3195857","url":null,"abstract":"Studies about diversity in Software Engineering (SE) are important to understand the disparity occurring nowadays at information technology workplaces. The goal of this work is to analyze the characteristics of diversity in SE and how to adapt SE practices when we have teams with diversity characteristics. We collected data by conducting a Systematic Literature Review (SLR) and semi-structured interviews aiming to identify what impacts of diversity can be observed in software development teams. We found that there are several challenges and barriers encountered in the work environment, and that inclusion and diversity can affect the software development teams positively.","PeriodicalId":295164,"journal":{"name":"2018 IEEE/ACM 11th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)","volume":"5 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-05-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116166103","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}
{"title":"Code Review for Newcomers: Is It Different?","authors":"V. Kovalenko, Alberto Bacchelli","doi":"10.1145/3195836.3195842","DOIUrl":"https://doi.org/10.1145/3195836.3195842","url":null,"abstract":"Onboarding is a critical stage in the tenure of software developers with a project, because meaningful contribution requires familiarity with the codebase. Some software teams employ practices, such as mentoring, to help new developers get accustomed faster. Code review, i.e., the manual inspection of code changes, is an opportunity for sharing knowledge and helping with onboarding. In this study, we investigate whether and how contributions from developers with low experience in a project do receive a different treatment during code review. We compare reviewers' experience, metrics of reviewers' attention, and change merge rate between changes from newcomers and from more experienced authors in 60 active open source projects. We find that the only phenomenon that is consistent across the vast majority of projects is a lower merge rate for newcomers' changes.","PeriodicalId":295164,"journal":{"name":"2018 IEEE/ACM 11th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)","volume":"44 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-05-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121967315","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}
{"title":"MyAgile: Sociological and Cultural Effects of Agile on Teams and Their Members","authors":"R. Biddle, Andreas Meier, Martin Kropp, C. Anslow","doi":"10.1145/3195836.3195845","DOIUrl":"https://doi.org/10.1145/3195836.3195845","url":null,"abstract":"Two main concepts in Agile software development are self-organized teams and direct contact with the customer or Product Owner. Additionally, constant feedback on different levels is considered to be of high importance. With constant feedback, transparency goes hand-in-hand. Compared to traditional software development, Agile approaches have much higher transparency, and this might be a problem for some people. What does it feel like to work in such an Agile team or organization for the individual? How do the software developers, testers or other team members experience this environment of high transparency and continuous feedback? In this paper we focus on a subset of the third Swiss Agile Study from 2016, a nationwide survey about software development, to shed some light on the sociological, cultural and cognitive aspects of Agile teams and their individual member. We found that despite the increased transparency, the majority of the participants reported working in an Agile environment, both on the individual and on the team level, as positive and satisfying. The analysis shows these positive influences have some strong correlations with certain Agile practices and with innovation and business aspects.","PeriodicalId":295164,"journal":{"name":"2018 IEEE/ACM 11th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)","volume":"77 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-05-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134236385","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}
{"title":"A Framework for Understanding Chatbots and Their Future","authors":"Elahe Paikari, A. Hoek","doi":"10.1145/3195836.3195859","DOIUrl":"https://doi.org/10.1145/3195836.3195859","url":null,"abstract":"Chatbots have rapidly become a mainstay in software development. A range of chatbots contribute regularly to the creation of actual production software. It is somewhat difficult, however, to precisely delineate hype from reality. Questions arise as to what distinguishes a chatbot from an ordinary software tool, what might be desirable properties of chatbots, and where their future may lie. This position paper introduces a starting framework through which we examine the current state of chatbots and identify directions for future work.","PeriodicalId":295164,"journal":{"name":"2018 IEEE/ACM 11th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)","volume":"78 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-05-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116535624","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}
{"title":"Sketching with a Purpose: Moving from Supporting Modeling to Supporting Software Engineering Activities","authors":"Matthias Book, A. Hoek","doi":"10.1145/3195836.3195854","DOIUrl":"https://doi.org/10.1145/3195836.3195854","url":null,"abstract":"With the advent of large interactive displays and the increasing ubiquity of touch-enabled devices, digital sketching tools are becoming viable alternatives to classic whiteboards for the design and engineering of software systems. In this paper, we argue that current sketching tools still focus largely on creating sketches as artifacts (mostly, models), rather than recognizing sketches as byproducts of engineers' thought processes as they tackle a broad variety of complex engineering activities. We therefore advocate a more activity-than artifact-oriented view of sketching and propose research on a number of ways in which digital sketching can support cognitively demanding software engineering activities more directly.","PeriodicalId":295164,"journal":{"name":"2018 IEEE/ACM 11th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-05-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131081992","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}