Since the world was taken over by the coronavirus pandemic, professionals from all areas have had to adapt to the changes imposed by health measures, in a sudden process, which points to permanent changes in the forms of consumption and work. In the present study, we aimed to document the main practical challenges faced by agile software development teams in this adaptation process. We conducted an interview based qualitative study, using techniques from Grounded Theory, and collected data on the experience of five agile software development teams, in three different countries. Besides bringing a rich description of the journeys of the studied teams, our results highlighted four main challenges in the adaptation processes: (1) the full digitization of agile ceremonies, (2) a loss of project awareness, (3) the administration of work-life balance, and (4) the self-management transition in less mature teams. Overall, the participants reported increased levels of perceived productivity, and we share along practices and recommendations that may be useful for other teams facing similar challenges.
{"title":"Pandemic Agility: Towards a theory on adapting to working from home","authors":"Jonas Matos, C. França","doi":"10.1145/3528579.3529184","DOIUrl":"https://doi.org/10.1145/3528579.3529184","url":null,"abstract":"Since the world was taken over by the coronavirus pandemic, professionals from all areas have had to adapt to the changes imposed by health measures, in a sudden process, which points to permanent changes in the forms of consumption and work. In the present study, we aimed to document the main practical challenges faced by agile software development teams in this adaptation process. We conducted an interview based qualitative study, using techniques from Grounded Theory, and collected data on the experience of five agile software development teams, in three different countries. Besides bringing a rich description of the journeys of the studied teams, our results highlighted four main challenges in the adaptation processes: (1) the full digitization of agile ceremonies, (2) a loss of project awareness, (3) the administration of work-life balance, and (4) the self-management transition in less mature teams. Overall, the participants reported increased levels of perceived productivity, and we share along practices and recommendations that may be useful for other teams facing similar challenges.","PeriodicalId":418063,"journal":{"name":"2022 IEEE/ACM 15th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)","volume":"46 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121246115","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}
As a result of the COVID-19 pandemic, more software teams than ever find themselves working in a remote model with team members separated by location, timezone, and working hours. This working model is expected to persist post-pandemic as companies explore the benefits of hybrid working. Software teams have always been reliant on tools to help them build software. Now they find themselves wholly reliant on tools to help them collaborate online. Surprisingly, there has been little research to date on which collaboration tools are used, how they are chosen, how they are used, and what challenges are faced when using such tools. This short paper offers emerging findings from an ongoing study in which we are interviewing software professionals about these questions. The insights are preliminary in that we are still conducting additional interviews beyond the ones reported here, yet some common themes are already emerging. Among others, we highlight the following: choice of tools made by the teams is opportunistic; teams adapt existing collaboration practices to utilize the tools better when working remotely; and a persistent problem exists of being unable to find information across chats, emails, and documents.
{"title":"Collaboration Tool Choices and Use in Remote Software Teams: Emerging Results from an Ongoing Study","authors":"Victoria Jackson, A. Hoek, R. Prikladnicki","doi":"10.1145/3528579.3529171","DOIUrl":"https://doi.org/10.1145/3528579.3529171","url":null,"abstract":"As a result of the COVID-19 pandemic, more software teams than ever find themselves working in a remote model with team members separated by location, timezone, and working hours. This working model is expected to persist post-pandemic as companies explore the benefits of hybrid working. Software teams have always been reliant on tools to help them build software. Now they find themselves wholly reliant on tools to help them collaborate online. Surprisingly, there has been little research to date on which collaboration tools are used, how they are chosen, how they are used, and what challenges are faced when using such tools. This short paper offers emerging findings from an ongoing study in which we are interviewing software professionals about these questions. The insights are preliminary in that we are still conducting additional interviews beyond the ones reported here, yet some common themes are already emerging. Among others, we highlight the following: choice of tools made by the teams is opportunistic; teams adapt existing collaboration practices to utilize the tools better when working remotely; and a persistent problem exists of being unable to find information across chats, emails, and documents.","PeriodicalId":418063,"journal":{"name":"2022 IEEE/ACM 15th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)","volume":"31 9 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128096669","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}
Crismerlyn Pereira, Angelica Santos, L. Machado, L. Zaina
Virtual kanban board is a tool widely used by software teams. The board provides a rich source of information about the teams' work and the project work-in-progress. Software startups often work with small teams with few resources and under constant time pressure. In this fast-paced environment of startups, the virtual kanban boards are helpful to improve communication keeping the whole organization members informed about the workflow and the allocation of tasks. However, startup software professionals often have little experience, and consequently, they can have difficulties maximizing the benefits of the virtual kanban to manage their work. In this paper, we present an empirical study with software startup professionals in which we analyzed qualitative data using the developer experience framework. This framework allows us to find out how development-related professionals perceive the resources of the virtual kanban tools and feel and see the board's contribution to the activities of their daily work. Our results revealed that the participants agreed that the virtual kanban boards are essential to tracking ongoing software projects and performing their work. However, they reported difficulties handling the tools, which can cause the professionals frustration. Besides, our findings showed that the participants saw the kanban virtual boards as a stimulus for their autonomy in routine activities. As the main contribution, our work provides a set of startup-related recommendations that can help startup teams better use virtual kanban board resources and, consequently, impact the software professionals' experience.
{"title":"How developers feel about tools: an investigation on software startup professionals experience with virtual kanban boards","authors":"Crismerlyn Pereira, Angelica Santos, L. Machado, L. Zaina","doi":"10.1145/3528579.3529172","DOIUrl":"https://doi.org/10.1145/3528579.3529172","url":null,"abstract":"Virtual kanban board is a tool widely used by software teams. The board provides a rich source of information about the teams' work and the project work-in-progress. Software startups often work with small teams with few resources and under constant time pressure. In this fast-paced environment of startups, the virtual kanban boards are helpful to improve communication keeping the whole organization members informed about the workflow and the allocation of tasks. However, startup software professionals often have little experience, and consequently, they can have difficulties maximizing the benefits of the virtual kanban to manage their work. In this paper, we present an empirical study with software startup professionals in which we analyzed qualitative data using the developer experience framework. This framework allows us to find out how development-related professionals perceive the resources of the virtual kanban tools and feel and see the board's contribution to the activities of their daily work. Our results revealed that the participants agreed that the virtual kanban boards are essential to tracking ongoing software projects and performing their work. However, they reported difficulties handling the tools, which can cause the professionals frustration. Besides, our findings showed that the participants saw the kanban virtual boards as a stimulus for their autonomy in routine activities. As the main contribution, our work provides a set of startup-related recommendations that can help startup teams better use virtual kanban board resources and, consequently, impact the software professionals' experience.","PeriodicalId":418063,"journal":{"name":"2022 IEEE/ACM 15th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)","volume":"25 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123884044","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}
Devender Goyal, Renato Cortinovis, Luiz Fernando Capretz
Software and information technologies are becoming increasingly integrated and pervasive in human society, and range from automated decision making to running critical infrastructure like utilities and financial institutions. There is also a growing awareness of the need to develop leaders who will harness these technologies in fair and inclusive ways. Many academic and industry researchers are advocating for the responsible use of information technologies and some academic and research institutions such as IEEE and ACM have published codes of ethics to spread awareness about these issues. In this regard, a number of academic researchers, including the authors of this paper, have expressed the need to teach students computer and information ethics as well as professional and leadership skills. In this paper, we propose an approach that is potentially effective in helping students develop leadership and communication skills as well as learn broader skills of professional responsibility. The proposed approach is modeled after Toastmasters, a very successful association present in over 140 countries with almost 350,000 members across more than 16,000 clubs. We describe our goal and give a general description of a Toastmasters club and how it is conducted. Further, we describe some activities and projects having CS/SE context that can be done by students as part of a relevant class. Finally, we briefly describe the approach that we are undertaking in our first pilot activities and their integration with additional synergetic strategies.
{"title":"A Framework for Class Activities to Cultivate Responsible Leadership in Software Engineering Students","authors":"Devender Goyal, Renato Cortinovis, Luiz Fernando Capretz","doi":"10.1145/3528579.3529167","DOIUrl":"https://doi.org/10.1145/3528579.3529167","url":null,"abstract":"Software and information technologies are becoming increasingly integrated and pervasive in human society, and range from automated decision making to running critical infrastructure like utilities and financial institutions. There is also a growing awareness of the need to develop leaders who will harness these technologies in fair and inclusive ways. Many academic and industry researchers are advocating for the responsible use of information technologies and some academic and research institutions such as IEEE and ACM have published codes of ethics to spread awareness about these issues. In this regard, a number of academic researchers, including the authors of this paper, have expressed the need to teach students computer and information ethics as well as professional and leadership skills. In this paper, we propose an approach that is potentially effective in helping students develop leadership and communication skills as well as learn broader skills of professional responsibility. The proposed approach is modeled after Toastmasters, a very successful association present in over 140 countries with almost 350,000 members across more than 16,000 clubs. We describe our goal and give a general description of a Toastmasters club and how it is conducted. Further, we describe some activities and projects having CS/SE context that can be done by students as part of a relevant class. Finally, we briefly describe the approach that we are undertaking in our first pilot activities and their integration with additional synergetic strategies.","PeriodicalId":418063,"journal":{"name":"2022 IEEE/ACM 15th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)","volume":"25 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124103439","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}
Due to the proliferation of disruptive technologies such as AI into almost every aspect of modern society, software systems increasingly affect the lives of people who do not directly use these systems -with potentially serious and harmful consequences. However, current software development practices do not yet account for this trend sufficiently well and frequently overlook indirect stakeholders. This paper presents the results of a preliminary interview-based study of software professionals aimed at understanding the state-of-practice of indirect stakeholder identification in the software industry. Our initial findings confirm that indirect stakeholders are often overlooked due to customer expectations, project constraints, the prevailing technology-centric software engineering culture and a lack of practical methods and tools. Based on these findings, we outline a roadmap for the investigation of methods and tools for the effective and efficient identification of indirect stakeholders.
{"title":"So who is impacted anyway - a preliminary study of indirect stakeholder identification in practice","authors":"Ingo Müller, Waqar Hussain, John C. Grundy","doi":"10.1145/3528579.3529168","DOIUrl":"https://doi.org/10.1145/3528579.3529168","url":null,"abstract":"Due to the proliferation of disruptive technologies such as AI into almost every aspect of modern society, software systems increasingly affect the lives of people who do not directly use these systems -with potentially serious and harmful consequences. However, current software development practices do not yet account for this trend sufficiently well and frequently overlook indirect stakeholders. This paper presents the results of a preliminary interview-based study of software professionals aimed at understanding the state-of-practice of indirect stakeholder identification in the software industry. Our initial findings confirm that indirect stakeholders are often overlooked due to customer expectations, project constraints, the prevailing technology-centric software engineering culture and a lack of practical methods and tools. Based on these findings, we outline a roadmap for the investigation of methods and tools for the effective and efficient identification of indirect stakeholders.","PeriodicalId":418063,"journal":{"name":"2022 IEEE/ACM 15th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)","volume":"8 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114951693","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}
Background: Prior research indicates that software developers experience serious levels of anxiety and stress, a form of suffering, due to a highly time-bound and technology-focused job environment. Such suffering affects their emotional well-being, professional productivity, and the software products they develop. Information, Idea, Arguments: Compassion arises when a person is confronted with another human's suffering and feels motivated to relieve that suffering. We want to explore how increasing compassion in software developers can positively impact the software development process. Vote: Is “compassionate software development” a topic worth researching?
{"title":"Vote Item: Is “Compassionate Software Development” a Topic Worth Researching?","authors":"Mary-Luz Sánchez-Gordón, Sandra Sanchez-Gordon, Ricardo Colomo Palacios","doi":"10.1145/3528579.3529176","DOIUrl":"https://doi.org/10.1145/3528579.3529176","url":null,"abstract":"Background: Prior research indicates that software developers experience serious levels of anxiety and stress, a form of suffering, due to a highly time-bound and technology-focused job environment. Such suffering affects their emotional well-being, professional productivity, and the software products they develop. Information, Idea, Arguments: Compassion arises when a person is confronted with another human's suffering and feels motivated to relieve that suffering. We want to explore how increasing compassion in software developers can positively impact the software development process. Vote: Is “compassionate software development” a topic worth researching?","PeriodicalId":418063,"journal":{"name":"2022 IEEE/ACM 15th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)","volume":"36 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133717063","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}
I. Rauf, Tamara Lopez, Helen Sharp, M. Petre, T. Tun, Mark Levine, J. Towse, D. Linden, A. Rashid, B. Nuseibeh
Background: Recent studies show that secure coding is about not only technical requirements but also developers' behaviour. Objective: To understand the influence of socio-technical contexts on how developers attend to and engage with security in code, software engineering researchers collaborated with social psychologists on a psychologically-informed study. Method: In a preregistered, between-group, controlled experiment, 124 developers from multiple freelance communities, were primed toward one of three identities, following which they completed code review tasks with open-ended responses. Qualitative analysis of the rich data focused on the attitudes and reasoning that shaped their identification of security issues within code. Results: Overall, attention to code security was intermittent and heterogeneous in focus. Although social identity priming did not significantly change the code review, qualitative analysis revealed that developers varied in how they noticed issues in code, how they addressed them, and how they justified their choices. Conclusion: We found that many developers do think about security – but differently from one another. Hence, effective interventions to promote secure coding must be appropriate to the individual development context. Data is uploaded at: https://osf.io/3jvrk
{"title":"Influences of developers' perspectives on their engagement with security in code","authors":"I. Rauf, Tamara Lopez, Helen Sharp, M. Petre, T. Tun, Mark Levine, J. Towse, D. Linden, A. Rashid, B. Nuseibeh","doi":"10.1145/3528579.3529180","DOIUrl":"https://doi.org/10.1145/3528579.3529180","url":null,"abstract":"Background: Recent studies show that secure coding is about not only technical requirements but also developers' behaviour. Objective: To understand the influence of socio-technical contexts on how developers attend to and engage with security in code, software engineering researchers collaborated with social psychologists on a psychologically-informed study. Method: In a preregistered, between-group, controlled experiment, 124 developers from multiple freelance communities, were primed toward one of three identities, following which they completed code review tasks with open-ended responses. Qualitative analysis of the rich data focused on the attitudes and reasoning that shaped their identification of security issues within code. Results: Overall, attention to code security was intermittent and heterogeneous in focus. Although social identity priming did not significantly change the code review, qualitative analysis revealed that developers varied in how they noticed issues in code, how they addressed them, and how they justified their choices. Conclusion: We found that many developers do think about security – but differently from one another. Hence, effective interventions to promote secure coding must be appropriate to the individual development context. Data is uploaded at: https://osf.io/3jvrk","PeriodicalId":418063,"journal":{"name":"2022 IEEE/ACM 15th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)","volume":"42 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125956322","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}
The problem of low gender diversity in open-source software (OSS) has been reported and studied in recent years. However, prior studies found that gender bias theories in social sciences cannot help us effectively identify gender bias effects in OSS. Our study takes the first step toward finding new measures for gender bias in OSS. This paper attempts to employ linguistic theories to identify different collaboration patterns between different genders. Our contributions are two-fold: we review linguistic literature on diversity and online collaboration, then we apply linguistic theories from our literature reviews to a random sample of code review conversations on GitHub.
{"title":"Seeking New Measures for Gender Bias Effects in Open-Source Software","authors":"Huilian Sophie Qiu, Moira Connell","doi":"10.1145/3528579.3529169","DOIUrl":"https://doi.org/10.1145/3528579.3529169","url":null,"abstract":"The problem of low gender diversity in open-source software (OSS) has been reported and studied in recent years. However, prior studies found that gender bias theories in social sciences cannot help us effectively identify gender bias effects in OSS. Our study takes the first step toward finding new measures for gender bias in OSS. This paper attempts to employ linguistic theories to identify different collaboration patterns between different genders. Our contributions are two-fold: we review linguistic literature on diversity and online collaboration, then we apply linguistic theories from our literature reviews to a random sample of code review conversations on GitHub.","PeriodicalId":418063,"journal":{"name":"2022 IEEE/ACM 15th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)","volume":"9 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122742293","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}
Rand Alchokr, J. Krüger, Yusra Shakeel, G. Saake, Thomas Leich
Background: Physical aspects are essential human factors that play a key role in a researcher's career and development. Aging is one of the most important physical aspects that can impact the productivity of a researcher (e.g., in terms of publications). In parallel, aging adds experience and proficiency on the scientific research work, such as assuring the quality and reliability of research. Objective: We aim to understand the impact of aging and the academic age on research publications productivity of research software engineers - the people actively developing software or conducting research in an academic research environment - and explore their Golden Age aspect. Method: We performed a first study on the age distribution of researchers who have published at three famous and prestigious software-engineering conferences: ASE, ESEC/FSE, and ICSE, including 4,620 research-track papers and their 7,337 authors. Results: The results suggest that the academic productivity is maximized at year 15 (Golden Age) and it is held roughly constant for further 15 years before it declines. The results also find, that half authors disappear after their first publication year, reflecting dropout rates that academia suffers from. Conclusion: Through this pilot study, we share insights on the age distribution, and thus representation, of software-engineering researchers at major conferences and try to understand whether certain groups of researchers are over- or underrepresented.
{"title":"On Academic Age Aspect and Discovering the Golden Age in Software Engineering","authors":"Rand Alchokr, J. Krüger, Yusra Shakeel, G. Saake, Thomas Leich","doi":"10.1145/3528579.3529175","DOIUrl":"https://doi.org/10.1145/3528579.3529175","url":null,"abstract":"Background: Physical aspects are essential human factors that play a key role in a researcher's career and development. Aging is one of the most important physical aspects that can impact the productivity of a researcher (e.g., in terms of publications). In parallel, aging adds experience and proficiency on the scientific research work, such as assuring the quality and reliability of research. Objective: We aim to understand the impact of aging and the academic age on research publications productivity of research software engineers - the people actively developing software or conducting research in an academic research environment - and explore their Golden Age aspect. Method: We performed a first study on the age distribution of researchers who have published at three famous and prestigious software-engineering conferences: ASE, ESEC/FSE, and ICSE, including 4,620 research-track papers and their 7,337 authors. Results: The results suggest that the academic productivity is maximized at year 15 (Golden Age) and it is held roughly constant for further 15 years before it declines. The results also find, that half authors disappear after their first publication year, reflecting dropout rates that academia suffers from. Conclusion: Through this pilot study, we share insights on the age distribution, and thus representation, of software-engineering researchers at major conferences and try to understand whether certain groups of researchers are over- or underrepresented.","PeriodicalId":418063,"journal":{"name":"2022 IEEE/ACM 15th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)","volume":"71 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132526810","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}
Background: Stories and story-work (in the fuller sense of those words) are recognised as a legitimate focus of study in other scientific disciplines. Information, Idea, Arguments: We are considering forming an inter-disciplinary research programme to explore how story-work can contribute to human-centric software engineering. Vote: What should we focus on to help ensure the proposed programme produces scientifically-valid, impactful research?
{"title":"Voting Item: Story-work in human-centric software engineering","authors":"A. Rainer, C. Menon","doi":"10.1145/3528579.3529170","DOIUrl":"https://doi.org/10.1145/3528579.3529170","url":null,"abstract":"Background: Stories and story-work (in the fuller sense of those words) are recognised as a legitimate focus of study in other scientific disciplines. Information, Idea, Arguments: We are considering forming an inter-disciplinary research programme to explore how story-work can contribute to human-centric software engineering. Vote: What should we focus on to help ensure the proposed programme produces scientifically-valid, impactful research?","PeriodicalId":418063,"journal":{"name":"2022 IEEE/ACM 15th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)","volume":"315 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132018574","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
扫码关注我们
求助内容：
应助结果提醒方式：