{"title":"Supporting Emotional Intelligence, Productivity and Team Goals while Handling Software Requirements Changes","authors":"Kashumi Madampe, Rashina Hoda, John Grundy","doi":"10.1145/3664600","DOIUrl":null,"url":null,"abstract":"<p><b>Background:</b>\nResearch shows that <i>emotional intelligence</i> (EI) should be used alongside cognitive intelligence during requirements change (RC) handling in Software Engineering (SE), especially in agile settings. <b>Objective:</b> We wanted to study the role of EI in-depth during RC handling. <b>Method:</b>\nWe conducted a mixed-methods study (an interview study followed by a survey study) with 124 software practitioners. <b>Findings:</b>\nWe found the causal condition, intervening condition and causes lead to key direct consequences of regulating own emotions, managing relationships, and extended consequences of sustaining productivity, setting and sustaining team goals. We found several strategies of supporting EI during RC handling. Further, we found strong correlations between six strategies and one being aware of own emotions, regulating own emotions, sustaining team productivity, and setting and sustaining team goals. <b>Conclusion:</b>\nEmpathising with others and tracking commitments and decisions as a team are key strategies that have strong correlations between managing emotions, between sustaining team productivity, and between setting and sustaining team goals. To the best of our knowledge, the framework we present in this paper is the first theoretical framework on EI in SE research. We provide recommendations for software practitioners to consider during RC handling.</p>","PeriodicalId":50933,"journal":{"name":"ACM Transactions on Software Engineering and Methodology","volume":"11 1","pages":""},"PeriodicalIF":6.6000,"publicationDate":"2024-05-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"ACM Transactions on Software Engineering and Methodology","FirstCategoryId":"94","ListUrlMain":"https://doi.org/10.1145/3664600","RegionNum":2,"RegionCategory":"计算机科学","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"Q1","JCRName":"COMPUTER SCIENCE, SOFTWARE ENGINEERING","Score":null,"Total":0}
引用次数: 0
Abstract
Background:
Research shows that emotional intelligence (EI) should be used alongside cognitive intelligence during requirements change (RC) handling in Software Engineering (SE), especially in agile settings. Objective: We wanted to study the role of EI in-depth during RC handling. Method:
We conducted a mixed-methods study (an interview study followed by a survey study) with 124 software practitioners. Findings:
We found the causal condition, intervening condition and causes lead to key direct consequences of regulating own emotions, managing relationships, and extended consequences of sustaining productivity, setting and sustaining team goals. We found several strategies of supporting EI during RC handling. Further, we found strong correlations between six strategies and one being aware of own emotions, regulating own emotions, sustaining team productivity, and setting and sustaining team goals. Conclusion:
Empathising with others and tracking commitments and decisions as a team are key strategies that have strong correlations between managing emotions, between sustaining team productivity, and between setting and sustaining team goals. To the best of our knowledge, the framework we present in this paper is the first theoretical framework on EI in SE research. We provide recommendations for software practitioners to consider during RC handling.
背景:研究表明,在软件工程(SE)的需求变更(RC)处理过程中,情绪智力(EI)应与认知智力并用,尤其是在敏捷环境中。研究目的我们希望深入研究情商在 RC 处理过程中的作用。方法:我们对 124 名软件从业人员进行了一项混合方法研究(访谈研究和调查研究)。结果:我们发现,因果条件、干预条件和原因导致了调节自身情绪、处理人际关系等关键的直接后果,以及维持生产率、设定和维持团队目标等扩展后果。我们发现了在处理 RC 时支持 EI 的几种策略。此外,我们还发现六种策略与意识到自己的情绪、调节自己的情绪、维持团队工作效率以及制定和维持团队目标之间存在着很强的相关性。结论:与他人共情以及作为一个团队跟踪承诺和决策是关键策略,它们与管理情绪、维持团队生产率以及设定和维持团队目标之间有很强的相关性。据我们所知,我们在本文中提出的框架是 SE 研究中第一个关于 EI 的理论框架。我们为软件从业人员提供了在处理 RC 时应考虑的建议。
期刊介绍:
Designing and building a large, complex software system is a tremendous challenge. ACM Transactions on Software Engineering and Methodology (TOSEM) publishes papers on all aspects of that challenge: specification, design, development and maintenance. It covers tools and methodologies, languages, data structures, and algorithms. TOSEM also reports on successful efforts, noting practical lessons that can be scaled and transferred to other projects, and often looks at applications of innovative technologies. The tone is scholarly but readable; the content is worthy of study; the presentation is effective.