Paper

{
  "raw_xml": "<entry>\n    <id>http://arxiv.org/abs/2603.10864v1</id>\n    <title>Exploring Indicators of Developers' Sentiment Perceptions in Student Software Projects</title>\n    <updated>2026-03-11T15:16:58Z</updated>\n    <link href='https://arxiv.org/abs/2603.10864v1' rel='alternate' type='text/html'/>\n    <link href='https://arxiv.org/pdf/2603.10864v1' rel='related' title='pdf' type='application/pdf'/>\n    <summary>Communication is a crucial social factor in the success of software projects, as positively or negatively perceived statements can influence how recipients feel and affect team collaboration through emotional contagion. Whether a developer perceives a written message as positive, negative, or neutral is likely shaped by multiple factors.\n  In this paper, we investigate how mood traits and states, life circumstances, project phases, and group dynamics relate to the perception of text-based messages in software development. We conducted a four-round survey study with 81 students in team-based software projects. Across rounds, participants reported these factors and labeled 30 decontextualized statements for sentiment, including meta-data on labeling rationale and uncertainty.\n  Our results show: (1) Sentiment perception is only moderately stable within individuals, and label changes concentrate on ambiguity-prone statements; (2) Correlation-level signals are small and do not survive global multiple-testing correction; (3) In statement-level repeated-measures models (GEE), higher mood trait and reactivity are associated with more positive (and less neutral) labeling, while predictors of negative labeling are weaker and at most trend-level (e.g., task conflict); (4) We find no clear evidence of systematic project-phase effects. Overall, sentiment perception varies within persons and is strongly statement-dependent.\n  Although our study was conducted in an academic setting, the observed variability and ambiguity effects suggest caution when interpreting sentiment analysis outputs and motivate future work with contextualized, in-project communication.</summary>\n    <category scheme='http://arxiv.org/schemas/atom' term='cs.SE'/>\n    <published>2026-03-11T15:16:58Z</published>\n    <arxiv:comment>This paper has been accepted for publication in the Journal of Software: Evolution and Process (JSEP)</arxiv:comment>\n    <arxiv:primary_category term='cs.SE'/>\n    <author>\n      <name>Martin Obaidi</name>\n    </author>\n    <author>\n      <name>Marc Herrmann</name>\n    </author>\n    <author>\n      <name>Jendrik Martensen</name>\n    </author>\n    <author>\n      <name>Jil Klünder</name>\n    </author>\n    <author>\n      <name>Kurt Schneider</name>\n    </author>\n  </entry>"
}