The Role of the Retrospective Meetings in Detecting, Refactoring and Monitoring Community Smells

arXiv:2502.18662 · cs.SE · Submitted 2025-02-25 · Read on arXiv

Listen

Radio episode about this paper

Transcript

Introduction to the show: ident: Computer Science. The day in computer science: software, systems and theory on arXiv.

Tom: I'm Tom.

Jane: And I'm Jane, here with Lu, Meng and our in-house large language model, Lalam.

Tom: We're looking at the paper: "The Role of the Retrospective Meetings in Detecting, Refactoring and Monitoring Community Smells".

Jane: Here's the gist of the paper. The study investigates how retrospective meetings in agile development address social debt by examining their role in detecting, refactoring, and monitoring Community Smells This research offers valuable insights to practitioners and researchers, highlighting the importance of addressing social debt issues in software development within agile practices Identification of Core Community Smells The findings indicate that retrospective meetings indeed enable the identification of core Community Smells This detection was triggered by the negative impacts of Community Smells on individual or team performance, prompting discussions and the need for improvement The study focused specifically on four core Community Smells commonly cited in the literature: Lone Wolf, Organizational Silo, Radio Silence, and Black Cloud In general, those smells are detected in retrospective meetings when the situation is highlighted as a problem or bottleneck by at least one of the team members The emphasis on these situations is driven by the individual perceptions of the members due to the impacts of the effects caused by the Community Smells on individual and/or team work Strategies for Refactoring and Monitoring While strategies for refactoring are often formulated, their implementation and monitoring remain inconsistent The research addresses several key questions regarding the process of addressing these smells Key findings include: 1.

Tom: Strategies are defined by the proposition and discussion of actions by members during the retrospective meeting.

Tom: Some situations characterized as Lone Wolf are brought up in the Retrospective, but no action plan is defined, remaining merely as a notice to the team.

Title and authors: Tom: So we've seen the title and who wrote it. It’s clear that they’re not just talking about technical debt anymore; they are looking at the social side of software development through these retrospective meetings.

Jane: Exactly. The paper is exploring how these meetings function as a way to identify, fix, and monitor Community Smells because existing research hasn't really focused on the strategies for refactoring or monitoring these specific types of smells.

Lu: The authors are using a qualitative study based on interviews with fifteen practitioners to answer four main research questions about whether these retrospective meetings help detect smells, define refactoring strategies, monitor those actions, and what the benefits are.

Meng: So the core question is if these meetings are just chat sessions that lead nowhere, or if they actually drive concrete action toward fixing things? That’s where I want to see the evidence.

Lalam: The paper sets up a clear structure around these four questions, but the real meat is how they connect the identified smells to actual actions taken in subsequent iterations.

Tom: It sounds like it’s moving beyond just identifying a problem and trying to map out a concrete process for addressing that problem within the agile cycle.

The paper's summary: Jane: Okay, so what the paper summarizes is that retrospective meetings are important because they allow teams to reflect on past work and address social aspects like team dynamics and individual performance.

Tom: They argue that these meetings are more comprehensive than daily standups or reviews because they focus on continuous improvement by the whole team, not just the immediate task at hand.

Lu: The study looks at how specific situations cataloged as Community Smells, like Lone Wolf or Organizational Silo, get highlighted during these meetings and if they can actually be identified.

Meng: So it’s checking if a situation is just an anecdotal complaint, or if the meeting structure forces the team to see it as a problem needing refactoring.

Lalam: The paper finds that these specific smells are detected when at least one team member highlights a situation as a problem or bottleneck during the retrospective discussion.

Tom: That makes sense from a practical standpoint. It’s not just passively acknowledging something is wrong; someone has to bring it up and make it part of the discussion.

The paper's improvements: Jane: Now let’s talk about what the authors suggest improves things, because they don't just stop at detection. They look at strategies for refactoring these Community Smells and how to monitor those actions.

Lu: One finding is that strategies for refactoring are defined by what members propose and discuss during the retrospective meeting, which is a key mechanism for addressing the question of whether action plans are actually being created.

Tom: That’s interesting because in practice, we often see strategy formulation happen, but then nothing gets tracked or implemented later on.

Meng: And they point out that some situations like Lone Wolf get brought up, but sometimes there isn't an actual action plan defined; it just stays as a notice to the team. That’s a gap we see constantly in production environments.

Lalam: They also mention that for things like Radio Silence, some strategies are associated with external stakeholders and other teams, which shows how social debt can be distributed across different groups.

Conclusion: Jane: So to wrap up, the paper suggests that focusing on positive aspects during these meetings might help prevent smells by linking positive team factors to the causes and effects of those bad patterns.

Tom: That’s a bit of a counter-intuitive point—using good stuff to stop bad stuff—but it makes sense if you think about generating positive emotions in the team, which can naturally avoid those dysfunctional situations.

Lu: The main implication is that we need to move beyond just identifying smells; we have to develop concrete action plans and actively monitor their effectiveness over subsequent iterations.

Meng: I agree with Lu. If the actions aren't monitored, they just become another item on the backlog instead of actually fixing the underlying social issue in the team structure.

Lalam: The paper points out a barrier: low psychological safety can really inhibit members from participating and contributing to defining those refactoring strategies. That’s a crucial constraint for any implementation.

Tom: So it’s not just about having a good meeting; it’s about creating the right environment where people feel safe enough to actually talk about these social issues and commit to fixing them.

Jane: Yeah, so the message for us is that these meetings are powerful tools, but their success depends heavily on creating psychological safety so the team can actually use them to tackle those deep social debts we accumulate.

Carlos Dantas, Tiago Massoni, Camila Sarmento, Rayana Rocha, Danielly Gualberto

Federal Institute of Rio Grande do Norte · Federal University of Campina Grande

cs.SE

Submitted: 2025-02-25

Updated: 2025-02-25

Journal ref: 18th International Conference on Cooperative and Human Aspects of Software Engineering (CHASE 2025)

DOI: 10.1109/CHASE66643.2025.00021

License: http://creativecommons.org/licenses/by-nc-sa/4.0/

Importance score: 67/100

The gist: The study investigates how retrospective meetings in agile development address social debt by examining their role in detecting, refactoring…

Key concepts

Community Smells
These are negative social issues in software development, like 'Lone Wolf' or 'Organizational Silo,' that cause team performance problems. They represent a form of social debt that needs fixing through team discussions.
Retrospective Meetings
These are regular team meetings used to reflect on the past sprint or work period. The study found they are crucial for detecting these smells because members bring up problems and bottlenecks during these sessions.
Refactoring Strategies
These are the specific actions or plans a team discusses in retrospectives to fix identified Community Smells. The research noted that while strategies are often discussed, their actual implementation and tracking remain inconsistent.
Positive Aspects
These are positive elements highlighted during meetings, such as team unity or collaboration. Focusing on these aspects can help prevent negative smells by generating positive emotions and reinforcing healthy team dynamics.

Terminology

Summary

The study investigates how retrospective meetings in agile development address social debt by examining their role in detecting, refactoring, and monitoring Community Smells This research offers valuable insights to practitioners and researchers, highlighting the importance of addressing social debt issues in software development within agile practices

Identification of Core Community Smells

The findings indicate that retrospective meetings indeed enable the identification of core Community Smells This detection was triggered by the negative impacts of Community Smells on individual or team performance, prompting discussions and the need for improvement The study focused specifically on four core Community Smells commonly cited in the literature: Lone Wolf, Organizational Silo, Radio Silence, and Black Cloud In general, those smells are detected in retrospective meetings when the situation is highlighted as a problem or bottleneck by at least one of the team members The emphasis on these situations is driven by the individual perceptions of the members due to the impacts of the effects caused by the Community Smells on individual and/or team work

Strategies for Refactoring and Monitoring

While strategies for refactoring are often formulated, their implementation and monitoring remain inconsistent The research addresses several key questions regarding the process of addressing these smells Key findings include:

  1. Strategies are defined by the proposition and discussion of actions by members during the retrospective meeting. p. 5

    Where the paper says it

    As illustrated in Fig. 3, the definition of strategies generally occurs through the proposition and discussion of actions by members during the retrospective meeting.

  2. Some situations characterized as Lone Wolf are brought up in the Retrospective, but no action plan is defined, remaining merely as a notice to the team. p. 5

    Where the paper says it

    Table III presents the strategies identified by the participants, among them, strategies present in the literature, such as team restructuring, the definition of communication plan, and mentoring of team members. In general, refactoring strategy is defined (as action plan), however, some situations characterized as Lone Wolf are brought up in the Retrospective, but no action plan is defined, remaining merely as a notice to the team, as reported by participant P10: “Some things, indeed, we establish an action plan.

  3. For Radio Silence, some strategies are associated with stakeholders and other external teams. p. 5

    Where the paper says it

    ] So, no, we didn’t put any action in place. ” In cases of Radio Silence, it was found that some strategies are associated with stakeholders and other external teams.

Benefits of Positive Aspects in Prevention

The study found that an emphasis on positive aspects during these meetings may help in preventing Community Smells Positive aspects can be linked to critical factors for team effectiveness, which are associated with both the causes and effects of Community Smells Specifically, highlighting these aspects as positive in the retrospective meetings can indicate health concerning the circumstances of Community Smells These positive aspects can generate positive emotions in team members, contributing to avoiding Community Smells situations

Implications for Practice and Future Research

For practitioners, the study emphasizes the importance of not only identifying Community Smells but also developing concrete action plans and monitoring their effectiveness Barriers such as low psychological safety can inhibit member participation and reduce contributions in defining refactoring strategies For researchers, new research may investigate the effectiveness of strategies defined in retrospective meetings or deepen the insights on the impact of positive aspects in preventing Community Smells. Future research could explore the role of Retrospective Meetings in specific operational contexts, such as DevOps teams, to highlight detection and respective refactoring strategies The study contributes to the understanding of addressing social debt issues in software engineering, specifically Community Smells in agile teams. p. 1

Where the paper says it

However, few studies focus on strategies for dealing with such circumstances or use retrospective meetings to investigate social debt in agile teams. This exploratory study aims to examine the role of retrospective meetings in detecting, refactoring, monitoring, and preventing Community Smells.

REFERENCES

[1] D. A. Tamburri, P. Kruchten, P. Lago, and H. van Vliet, “What is social debt in software engineering? p. 0

Where the paper says it

Index Terms—Human Aspects, Social-Debt, Community Smell, Retrospective Meeting, Agile Software Development I. INTRODUCTION In Software Engineering, the term Social-Debt describes unforeseen project costs, which are related to the non-ideal conditions of the software development team [1].

” in 2013 6th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE), May 2013, pp. p. 0
Where the paper says it

Index Terms—Human Aspects, Social-Debt, Community Smell, Retrospective Meeting, Agile Software Development I. INTRODUCTION In Software Engineering, the term Social-Debt describes unforeseen project costs, which are related to the non-ideal conditions of the software development team [1].

93–96

[2] G. Catolino, F. Palomba, D. A. Tamburri, A. Serebrenik, and F. Ferrucci, “Refactoring community smells in the wild: The practitioner’s field manual,” in Proceedings of the ACM/IEEE 42nd International Conference on Software Engineering: Software Engineering in Society, ser. p. 1

Where the paper says it

Despite the challenges in consistently addressing Community Smells, the study also found that retrospective meetings could contribute to their prevention. The findings have a number of consequences for both researchers and practitioners in the field of software engineering.

p. 1
Where the paper says it

Despite the challenges in consistently addressing Community Smells, the study also found that retrospective meetings could contribute to their prevention. The findings have a number of consequences for both researchers and practitioners in the field of software engineering.

ICSE-SEIS ’20. New York, NY, USA: Association for Computing Machinery, Oct 2020, Conference paper, p. p. 8
Where the paper says it

Therefore, highlighting these aspects as positive in the retrospective meetings can indicate health (absence of causes and/or effects) concerning the circumstances of Community Smells. 6 illustrates the association between the positive aspects identified in the research and the critical factors for team effectiveness – which are associated with the causes and effects of the Community Smells addressed in this research.

p. 8
Where the paper says it

Therefore, highlighting these aspects as positive in the retrospective meetings can indicate health (absence of causes and/or effects) concerning the circumstances of Community Smells. 6 illustrates the association between the positive aspects identified in the research and the critical factors for team effectiveness – which are associated with the causes and effects of the Community Smells addressed in this research.

25–34

[3] D. A. Tamburri, P. Kruchten, P. Lago, and H. v. Vliet, “Social debt in software engineering: insights from industry,” Journal of Internet Services and Applications, vol. p. 0

Where the paper says it

Conclusion. This study offers valuable insights to practitioners and researchers, highlighting the importance of addressing social debt in software development within agile practices.

p. 0
Where the paper says it

Conclusion. This study offers valuable insights to practitioners and researchers, highlighting the importance of addressing social debt in software development within agile practices.

p. 0
Where the paper says it

Conclusion. This study offers valuable insights to practitioners and researchers, highlighting the importance of addressing social debt in software development within agile practices.

p. 0
Where the paper says it

Conclusion. This study offers valuable insights to practitioners and researchers, highlighting the importance of addressing social debt in software development within agile practices.

6, no. 1, p. 10, 2015

[4] D. A. Tamburri, F. Palomba, and R. Kazman, “Exploring community smells in open-source: An automated approach,” IEEE Transactions on Software Engineering, vol. p. 0

Where the paper says it

Index Terms—Human Aspects, Social-Debt, Community Smell, Retrospective Meeting, Agile Software Development I. INTRODUCTION In Software Engineering, the term Social-Debt describes unforeseen project costs, which are related to the non-ideal conditions of the software development team [1].

p. 0
Where the paper says it

Index Terms—Human Aspects, Social-Debt, Community Smell, Retrospective Meeting, Agile Software Development I. INTRODUCTION In Software Engineering, the term Social-Debt describes unforeseen project costs, which are related to the non-ideal conditions of the software development team [1].

p. 0
Where the paper says it

Index Terms—Human Aspects, Social-Debt, Community Smell, Retrospective Meeting, Agile Software Development I. INTRODUCTION In Software Engineering, the term Social-Debt describes unforeseen project costs, which are related to the non-ideal conditions of the software development team [1].

p. 0
Where the paper says it

Index Terms—Human Aspects, Social-Debt, Community Smell, Retrospective Meeting, Agile Software Development I. INTRODUCTION In Software Engineering, the term Social-Debt describes unforeseen project costs, which are related to the non-ideal conditions of the software development team [1].

p. 1
Where the paper says it

In this context, retrospective meetings are highlighted as a data source for investigating different aspects of software development. Unlike such works [14], [20]–[23], this study has a specific focus on the practice of retrospective meetings and their role in refactoring social debt, particularly in the circumstances known as Community Smells, showing how these smells are highlighted, what strategies are defined and which monitoring and prevention are carried out through the retrospective meetings.

p. 1
Where the paper says it

In this context, retrospective meetings are highlighted as a data source for investigating different aspects of software development. Unlike such works [14], [20]–[23], this study has a specific focus on the practice of retrospective meetings and their role in refactoring social debt, particularly in the circumstances known as Community Smells, showing how these smells are highlighted, what strategies are defined and which monitoring and prevention are carried out through the retrospective meetings.

p. 1
Where the paper says it

In this context, retrospective meetings are highlighted as a data source for investigating different aspects of software development. Unlike such works [14], [20]–[23], this study has a specific focus on the practice of retrospective meetings and their role in refactoring social debt, particularly in the circumstances known as Community Smells, showing how these smells are highlighted, what strategies are defined and which monitoring and prevention are carried out through the retrospective meetings.

p. 1
Where the paper says it

In this context, retrospective meetings are highlighted as a data source for investigating different aspects of software development. Unlike such works [14], [20]–[23], this study has a specific focus on the practice of retrospective meetings and their role in refactoring social debt, particularly in the circumstances known as Community Smells, showing how these smells are highlighted, what strategies are defined and which monitoring and prevention are carried out through the retrospective meetings.

47, no. 3, pp. 630–652, March 2021

[5] F. Palomba, D. Andrew Tamburri, F. Arcelli Fontana, R. Oliveto, A. Zaidman, and A. Serebrenik, “Beyond technical aspects: How do community smells influence the intensity of code smells? p. 8

Where the paper says it

In [6], a set of critical factors for team effectiveness [33] [34] was used, relating them to the causes of Community Smells, as well as highlighting the influence flow of the effects of Community Smells on these factors7 . Similarly, using the critical factors as codes, associating the identified positive aspects with the critical factors for team effectiveness, we can observe that the positive aspects highlighted in the retrospective meetings align with the most frequent factors causing Community Smells according to [6, p.

p. 8
Where the paper says it

In [6], a set of critical factors for team effectiveness [33] [34] was used, relating them to the causes of Community Smells, as well as highlighting the influence flow of the effects of Community Smells on these factors7 . Similarly, using the critical factors as codes, associating the identified positive aspects with the critical factors for team effectiveness, we can observe that the positive aspects highlighted in the retrospective meetings align with the most frequent factors causing Community Smells according to [6, p.

p. 8
Where the paper says it

In [6], a set of critical factors for team effectiveness [33] [34] was used, relating them to the causes of Community Smells, as well as highlighting the influence flow of the effects of Community Smells on these factors7 . Similarly, using the critical factors as codes, associating the identified positive aspects with the critical factors for team effectiveness, we can observe that the positive aspects highlighted in the retrospective meetings align with the most frequent factors causing Community Smells according to [6, p.

p. 8
Where the paper says it

In [6], a set of critical factors for team effectiveness [33] [34] was used, relating them to the causes of Community Smells, as well as highlighting the influence flow of the effects of Community Smells on these factors7 . Similarly, using the critical factors as codes, associating the identified positive aspects with the critical factors for team effectiveness, we can observe that the positive aspects highlighted in the retrospective meetings align with the most frequent factors causing Community Smells according to [6, p.

” IEEE Transactions on Software Engineering, vol. 47, no. 1, pp. 108–129, 2021

[6] E. Caballero-Espinosa, J. p. 1

Where the paper says it

However, despite the presence of these refactoring strategies, several challenges remain. For instance, Caballero-Espinosa, Carver, and Stowers [6] highlighted in a systematic literature review the existence of Community Smells without indication of refactoring strategies, strategies with unproven or partially proven effectiveness, and a lack of details about the strategies indicated in the literature.

p. 1
Where the paper says it

However, despite the presence of these refactoring strategies, several challenges remain. For instance, Caballero-Espinosa, Carver, and Stowers [6] highlighted in a systematic literature review the existence of Community Smells without indication of refactoring strategies, strategies with unproven or partially proven effectiveness, and a lack of details about the strategies indicated in the literature.

p. 1
Where the paper says it

However, despite the presence of these refactoring strategies, several challenges remain. For instance, Caballero-Espinosa, Carver, and Stowers [6] highlighted in a systematic literature review the existence of Community Smells without indication of refactoring strategies, strategies with unproven or partially proven effectiveness, and a lack of details about the strategies indicated in the literature.

p. 1
Where the paper says it

However, despite the presence of these refactoring strategies, several challenges remain. For instance, Caballero-Espinosa, Carver, and Stowers [6] highlighted in a systematic literature review the existence of Community Smells without indication of refactoring strategies, strategies with unproven or partially proven effectiveness, and a lack of details about the strategies indicated in the literature.

C. Carver, and K. p. 1
Where the paper says it

However, despite the presence of these refactoring strategies, several challenges remain. For instance, Caballero-Espinosa, Carver, and Stowers [6] highlighted in a systematic literature review the existence of Community Smells without indication of refactoring strategies, strategies with unproven or partially proven effectiveness, and a lack of details about the strategies indicated in the literature.

p. 1
Where the paper says it

However, despite the presence of these refactoring strategies, several challenges remain. For instance, Caballero-Espinosa, Carver, and Stowers [6] highlighted in a systematic literature review the existence of Community Smells without indication of refactoring strategies, strategies with unproven or partially proven effectiveness, and a lack of details about the strategies indicated in the literature.

p. 1
Where the paper says it

However, despite the presence of these refactoring strategies, several challenges remain. For instance, Caballero-Espinosa, Carver, and Stowers [6] highlighted in a systematic literature review the existence of Community Smells without indication of refactoring strategies, strategies with unproven or partially proven effectiveness, and a lack of details about the strategies indicated in the literature.

p. 1
Where the paper says it

However, despite the presence of these refactoring strategies, several challenges remain. For instance, Caballero-Espinosa, Carver, and Stowers [6] highlighted in a systematic literature review the existence of Community Smells without indication of refactoring strategies, strategies with unproven or partially proven effectiveness, and a lack of details about the strategies indicated in the literature.

Stowers, “Community smells—the sources of social debt: A systematic literature review,” Information and Software Technology, vol. p. 1
Where the paper says it

However, despite the presence of these refactoring strategies, several challenges remain. For instance, Caballero-Espinosa, Carver, and Stowers [6] highlighted in a systematic literature review the existence of Community Smells without indication of refactoring strategies, strategies with unproven or partially proven effectiveness, and a lack of details about the strategies indicated in the literature.

p. 1
Where the paper says it

However, despite the presence of these refactoring strategies, several challenges remain. For instance, Caballero-Espinosa, Carver, and Stowers [6] highlighted in a systematic literature review the existence of Community Smells without indication of refactoring strategies, strategies with unproven or partially proven effectiveness, and a lack of details about the strategies indicated in the literature.

p. 1
Where the paper says it

However, despite the presence of these refactoring strategies, several challenges remain. For instance, Caballero-Espinosa, Carver, and Stowers [6] highlighted in a systematic literature review the existence of Community Smells without indication of refactoring strategies, strategies with unproven or partially proven effectiveness, and a lack of details about the strategies indicated in the literature.

p. 1
Where the paper says it

However, despite the presence of these refactoring strategies, several challenges remain. For instance, Caballero-Espinosa, Carver, and Stowers [6] highlighted in a systematic literature review the existence of Community Smells without indication of refactoring strategies, strategies with unproven or partially proven effectiveness, and a lack of details about the strategies indicated in the literature.

153, p. 107078, 2023

[7] A. Alliance, Agile Practice Guide, Project Management Institute, 2017: Agile Practice Guide

[8] H. Kniberg, Scrum and XP from the Trenches. p. 1

Where the paper says it

technologies, process, team, and individuals stand out, making the retrospective meeting the most comprehensive and focused on continuous improvement by the team compared to the other meetings in the agile Scrum methodology [7], [8], [14], [15]. Given the focus on reflection and improvement, retrospective meetings present a potential opportunity for teams to identify and address Community Smells more than other meetings in Scrum, such as Dailies and Reviews.

p. 1
Where the paper says it

technologies, process, team, and individuals stand out, making the retrospective meeting the most comprehensive and focused on continuous improvement by the team compared to the other meetings in the agile Scrum methodology [7], [8], [14], [15]. Given the focus on reflection and improvement, retrospective meetings present a potential opportunity for teams to identify and address Community Smells more than other meetings in Scrum, such as Dailies and Reviews.

p. 1
Where the paper says it

technologies, process, team, and individuals stand out, making the retrospective meeting the most comprehensive and focused on continuous improvement by the team compared to the other meetings in the agile Scrum methodology [7], [8], [14], [15]. Given the focus on reflection and improvement, retrospective meetings present a potential opportunity for teams to identify and address Community Smells more than other meetings in Scrum, such as Dailies and Reviews.

p. 1
Where the paper says it

technologies, process, team, and individuals stand out, making the retrospective meeting the most comprehensive and focused on continuous improvement by the team compared to the other meetings in the agile Scrum methodology [7], [8], [14], [15]. Given the focus on reflection and improvement, retrospective meetings present a potential opportunity for teams to identify and address Community Smells more than other meetings in Scrum, such as Dailies and Reviews.

Lulu. com, 2015

[9] V. One, “11th state of agile report,” Version One, Tech. p. 4

Where the paper says it

” In the interview with P10 (Product Owner), who, in some of their team’s retrospective meetings, also acts as a facilitator, they expressed difficulties with communication among some team members, which characterized certain isolation and delayed the handling of development issues, leading to delays and even non-delivery of features defined for the sprint. Participant P10 described their perception and the report of the highlighted situation in the team’s retrospective meeting: “One person and another, I perceive that [.

p. 4
Where the paper says it

” In the interview with P10 (Product Owner), who, in some of their team’s retrospective meetings, also acts as a facilitator, they expressed difficulties with communication among some team members, which characterized certain isolation and delayed the handling of development issues, leading to delays and even non-delivery of features defined for the sprint. Participant P10 described their perception and the report of the highlighted situation in the team’s retrospective meeting: “One person and another, I perceive that [.

p. 4
Where the paper says it

” In the interview with P10 (Product Owner), who, in some of their team’s retrospective meetings, also acts as a facilitator, they expressed difficulties with communication among some team members, which characterized certain isolation and delayed the handling of development issues, leading to delays and even non-delivery of features defined for the sprint. Participant P10 described their perception and the report of the highlighted situation in the team’s retrospective meeting: “One person and another, I perceive that [.

p. 4
Where the paper says it

” In the interview with P10 (Product Owner), who, in some of their team’s retrospective meetings, also acts as a facilitator, they expressed difficulties with communication among some team members, which characterized certain isolation and delayed the handling of development issues, leading to delays and even non-delivery of features defined for the sprint. Participant P10 described their perception and the report of the highlighted situation in the team’s retrospective meeting: “One person and another, I perceive that [.

Rep., 2016

[10] K. Schwaber and J. Sutherland, “Scrum guide,” Scrumguides. p. 1

Where the paper says it

technologies, process, team, and individuals stand out, making the retrospective meeting the most comprehensive and focused on continuous improvement by the team compared to the other meetings in the agile Scrum methodology [7], [8], [14], [15]. Given the focus on reflection and improvement, retrospective meetings present a potential opportunity for teams to identify and address Community Smells more than other meetings in Scrum, such as Dailies and Reviews.

p. 1
Where the paper says it

technologies, process, team, and individuals stand out, making the retrospective meeting the most comprehensive and focused on continuous improvement by the team compared to the other meetings in the agile Scrum methodology [7], [8], [14], [15]. Given the focus on reflection and improvement, retrospective meetings present a potential opportunity for teams to identify and address Community Smells more than other meetings in Scrum, such as Dailies and Reviews.

p. 1
Where the paper says it

technologies, process, team, and individuals stand out, making the retrospective meeting the most comprehensive and focused on continuous improvement by the team compared to the other meetings in the agile Scrum methodology [7], [8], [14], [15]. Given the focus on reflection and improvement, retrospective meetings present a potential opportunity for teams to identify and address Community Smells more than other meetings in Scrum, such as Dailies and Reviews.

p. 1
Where the paper says it

technologies, process, team, and individuals stand out, making the retrospective meeting the most comprehensive and focused on continuous improvement by the team compared to the other meetings in the agile Scrum methodology [7], [8], [14], [15]. Given the focus on reflection and improvement, retrospective meetings present a potential opportunity for teams to identify and address Community Smells more than other meetings in Scrum, such as Dailies and Reviews.

org, 11 2020

[11] P. Kua, The Retrospective Handbook. p. 0

Where the paper says it

The Role of the Retrospective Meetings in Detecting, Refactoring and Monitoring Community Smells A Qualitative Study Carlos Dantas Federal Institute of Rio Grande do Norte Apodi, Brazil carlos. dantas@ifrn.

Leanpub, 2013

[13] P. Caroli and T. C. Coimbra, FunRetrospectives: activities and Ideas for making agile retrospectives more engaging. p. 8

Where the paper says it

, reducing downtime or making the review process more thorough. In another empirical study [37], the internal consequences for software developers and external consequences of happiness and unhappiness are observed to understand the impact on software engineering activities.

Editora Caroli, 2020

[14] A. Martini, V. p. 1

Where the paper says it

However, while many of these points were categorized under “People and Relationships”, this category received limited attention in the final analysis because the authors evaluated theses as less related to how the large-scale agile development methodology influences teams. Similarly, Martini, Stray, and Moe [14] conducted a study to characterize the issues identified in retrospective meetings of large-scale agile development teams.

p. 1
Where the paper says it

However, while many of these points were categorized under “People and Relationships”, this category received limited attention in the final analysis because the authors evaluated theses as less related to how the large-scale agile development methodology influences teams. Similarly, Martini, Stray, and Moe [14] conducted a study to characterize the issues identified in retrospective meetings of large-scale agile development teams.

p. 1
Where the paper says it

However, while many of these points were categorized under “People and Relationships”, this category received limited attention in the final analysis because the authors evaluated theses as less related to how the large-scale agile development methodology influences teams. Similarly, Martini, Stray, and Moe [14] conducted a study to characterize the issues identified in retrospective meetings of large-scale agile development teams.

p. 1
Where the paper says it

However, while many of these points were categorized under “People and Relationships”, this category received limited attention in the final analysis because the authors evaluated theses as less related to how the large-scale agile development methodology influences teams. Similarly, Martini, Stray, and Moe [14] conducted a study to characterize the issues identified in retrospective meetings of large-scale agile development teams.

Stray, and N. p. 1
Where the paper says it

However, while many of these points were categorized under “People and Relationships”, this category received limited attention in the final analysis because the authors evaluated theses as less related to how the large-scale agile development methodology influences teams. Similarly, Martini, Stray, and Moe [14] conducted a study to characterize the issues identified in retrospective meetings of large-scale agile development teams.

p. 1
Where the paper says it

However, while many of these points were categorized under “People and Relationships”, this category received limited attention in the final analysis because the authors evaluated theses as less related to how the large-scale agile development methodology influences teams. Similarly, Martini, Stray, and Moe [14] conducted a study to characterize the issues identified in retrospective meetings of large-scale agile development teams.

p. 1
Where the paper says it

However, while many of these points were categorized under “People and Relationships”, this category received limited attention in the final analysis because the authors evaluated theses as less related to how the large-scale agile development methodology influences teams. Similarly, Martini, Stray, and Moe [14] conducted a study to characterize the issues identified in retrospective meetings of large-scale agile development teams.

p. 1
Where the paper says it

However, while many of these points were categorized under “People and Relationships”, this category received limited attention in the final analysis because the authors evaluated theses as less related to how the large-scale agile development methodology influences teams. Similarly, Martini, Stray, and Moe [14] conducted a study to characterize the issues identified in retrospective meetings of large-scale agile development teams.

B. Moe, “Technical-, social- and process debt in large-scale agile: An exploratory case-study,” in Agile Processes in Software Engineering and Extreme Programming – Workshops, R. p. 1
Where the paper says it

Similarly, Martini, Stray, and Moe [14] conducted a study to characterize the issues identified in retrospective meetings of large-scale agile development teams. The case study consisted of interviews, observations, and document analysis to investigate what teams discuss in intra-team and interteam retrospective meetings concerning technical debt, social debt, and process debt.

p. 1
Where the paper says it

Similarly, Martini, Stray, and Moe [14] conducted a study to characterize the issues identified in retrospective meetings of large-scale agile development teams. The case study consisted of interviews, observations, and document analysis to investigate what teams discuss in intra-team and interteam retrospective meetings concerning technical debt, social debt, and process debt.

p. 1
Where the paper says it

Similarly, Martini, Stray, and Moe [14] conducted a study to characterize the issues identified in retrospective meetings of large-scale agile development teams. The case study consisted of interviews, observations, and document analysis to investigate what teams discuss in intra-team and interteam retrospective meetings concerning technical debt, social debt, and process debt.

p. 1
Where the paper says it

Similarly, Martini, Stray, and Moe [14] conducted a study to characterize the issues identified in retrospective meetings of large-scale agile development teams. The case study consisted of interviews, observations, and document analysis to investigate what teams discuss in intra-team and interteam retrospective meetings concerning technical debt, social debt, and process debt.

Hoda, Ed. Cham: Springer International Publishing, 2019, pp. 112–119

[15] SCRUMStudy, A Guide to the Scrum Body of Knowledge (SBOK® Guide) – Fourth edition. Scrumstudy, A Brand Of Vmedu, Inc, 2022

[16] D. A. Tamburri, R. Kazman, and W.-J. van den Heuvel, “Splicing community and software architecture smells in agile teams: An industrial study,” in Hawaii International Conference on System Sciences, 2019

[17] K. Charmaz, A construc¸ao da teoria fundamentada: Guia Pr ˜ atico para ´ Analise Qualitativa ´, ser. Metodos de Pesquisa. Penso, 2009

[18] C. Sarmento, T. p. 0

Where the paper says it

br Tiago Massoni Federal University of Campina Grande Campina Grande, Brazil massoni@computacao. br Camila Sarmento Federal University of Campina Grande Campina Grande, Brazil camilasarmento@copin.

p. 0
Where the paper says it

br Tiago Massoni Federal University of Campina Grande Campina Grande, Brazil massoni@computacao. br Camila Sarmento Federal University of Campina Grande Campina Grande, Brazil camilasarmento@copin.

p. 0
Where the paper says it

br Tiago Massoni Federal University of Campina Grande Campina Grande, Brazil massoni@computacao. br Camila Sarmento Federal University of Campina Grande Campina Grande, Brazil camilasarmento@copin.

Massoni, A. p. 0
Where the paper says it

dantas@ifrn. br Tiago Massoni Federal University of Campina Grande Campina Grande, Brazil massoni@computacao.

p. 0
Where the paper says it

dantas@ifrn. br Tiago Massoni Federal University of Campina Grande Campina Grande, Brazil massoni@computacao.

p. 0
Where the paper says it

dantas@ifrn. br Tiago Massoni Federal University of Campina Grande Campina Grande, Brazil massoni@computacao.

Serebrenik, G. Catolino, D. Tamburri, and F. Palomba, “Gender diversity and community smells: A double-replication study on brazilian software teams,” in 2022 IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER). p. 3
Where the paper says it

RESULTS Fifteen practitioners from different agile software development teams working in various organizations were interviewed. Table I presents the distribution of the participants by gender, role, leader function (team leader, tech lead, quality lead) and years of professional experience in software development teams, split by interview-analysis cycle.

p. 3
Where the paper says it

RESULTS Fifteen practitioners from different agile software development teams working in various organizations were interviewed. Table I presents the distribution of the participants by gender, role, leader function (team leader, tech lead, quality lead) and years of professional experience in software development teams, split by interview-analysis cycle.

p. 3
Where the paper says it

RESULTS Fifteen practitioners from different agile software development teams working in various organizations were interviewed. Table I presents the distribution of the participants by gender, role, leader function (team leader, tech lead, quality lead) and years of professional experience in software development teams, split by interview-analysis cycle.

Institute of Electrical and Electronics Engineers Inc. p. 0
Where the paper says it

The Role of the Retrospective Meetings in Detecting, Refactoring and Monitoring Community Smells A Qualitative Study Carlos Dantas Federal Institute of Rio Grande do Norte Apodi, Brazil carlos. dantas@ifrn.

p. 0
Where the paper says it

The Role of the Retrospective Meetings in Detecting, Refactoring and Monitoring Community Smells A Qualitative Study Carlos Dantas Federal Institute of Rio Grande do Norte Apodi, Brazil carlos. dantas@ifrn.

p. 0
Where the paper says it

The Role of the Retrospective Meetings in Detecting, Refactoring and Monitoring Community Smells A Qualitative Study Carlos Dantas Federal Institute of Rio Grande do Norte Apodi, Brazil carlos. dantas@ifrn.

, March 2022, Conference paper, pp. 273–283

[19] N. Tahsin and K. Sakib, “Refactoring community smells: An empirical study on the software practitioners of bangladesh,” in 2022 29th Asia-Pacific Software Engineering Conference (APSEC), vol. p. 1

Where the paper says it

Despite the challenges in consistently addressing Community Smells, the study also found that retrospective meetings could contribute to their prevention. The findings have a number of consequences for both researchers and practitioners in the field of software engineering.

p. 1
Where the paper says it

Despite the challenges in consistently addressing Community Smells, the study also found that retrospective meetings could contribute to their prevention. The findings have a number of consequences for both researchers and practitioners in the field of software engineering.

p. 1
Where the paper says it

Despite the challenges in consistently addressing Community Smells, the study also found that retrospective meetings could contribute to their prevention. The findings have a number of consequences for both researchers and practitioners in the field of software engineering.

2022-December. IEEE Computer Society, Dec 2022, Conference paper, pp. 421–43

[2] G. Catolino, F. Palomba, D. A. Tamburri, A. Serebrenik, and F. Ferrucci, “Refactoring community smells in the wild: The practitioner’s field manual,” in Proceedings of the ACM/IEEE 42nd International Conference on Software Engineering: Software Engineering in Society, ser. ICSE-SEIS ’20. New York, NY, USA: Association for Computing Machinery, Oct 2020, Conference paper, p. 25–34

[3] D. A. Tamburri, P. Kruchten, P. Lago, and H. v. Vliet, “Social debt in software engineering: insights from industry,” Journal of Internet Services and Applications, vol. 6, no. 1, p. 10, 2015

[4] D. A. Tamburri, F. Palomba, and R. Kazman, “Exploring community smells in open-source: An automated approach,” IEEE Transactions on Software Engineering, vol. 47, no. 3, pp. 630–652, March 2021

[5] F. Palomba, D. Andrew Tamburri, F. Arcelli Fontana, R. Oliveto, A. Zaidman, and A. Serebrenik, “Beyond technical aspects: How do community smells influence the intensity of code smells?” IEEE Transactions on Software Engineering, vol. 47, no. 1, pp. 108–129, 2021

[6] E. Caballero-Espinosa, J. C. Carver, and K. Stowers, “Community smells—the sources of social debt: A systematic literature review,” Information and Software Technology, vol. 153, p. 107078, 2023

[7] A. Alliance, Agile Practice Guide, Project Management Institute, 2017: Agile Practice Guide

[8] H. Kniberg, Scrum and XP from the Trenches. Lulu. com, 2015

[9] V. One, “11th state of agile report,” Version One, Tech. Rep., 2016

[10] K. Schwaber and J. Sutherland, “Scrum guide,” Scrumguides.org, 11 2020

[14] A. Martini, V. Stray, and N. B. Moe, “Technical-, social- and process debt in large-scale agile: An exploratory case-study,” in Agile Processes in Software Engineering and Extreme Programming – Workshops, R. Hoda, Ed. Cham: Springer International Publishing, 2019

[15] SCRUMStudy, A Guide to the Scrum Body of Knowledge (SBOK® Guide) – Fourth edition. Scrumstudy, A Brand Of Vmedu, Inc, 2022

[16] D. A. Tamburri, R. Kazman, and W.-J. van den Heuvel, “Splicing community and software architecture smells in agile teams: An industrial study,” in Hawaii International Conference on System Sciences, 2019

[17] K. Charmaz, A construc¸ao da teoria fundamentada: Guia Pr ˜ atico para ´ Analise Qualitativa ´, ser. Metodos de Pesquisa. Penso, 2009

[18] C. Sarmento, T. Massoni, A. Serebrenik, G. Catolino, D. Tamburri, and F. Palomba, “Gender diversity and community smells: A double-replication study on brazilian software teams,” in 2022 IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER). Institute of Electrical and Electronics Engineers Inc., March 2022, Conference paper, pp. 273–283

[19] N. Tahsin and K. Sakib, “Refactoring community smells: An empirical study on the software practitioners of bangladesh,” in 2022 29th Asia-Pacific Software Engineering Conference (APSEC), vol. 2022-December. IEEE Computer Society, Dec 2021, Conference paper, pp. 43

[3] D. A. Tamburri, P. Kruchten, P. Lago, and H. v. Vliet, “Social debt in software engineering: insights from industry,” Journal of Internet Services and Applications, vol. 6, no. 1, p. 10, 2015

[4] D. A. Tamburri, F. Palomba, and R. Kazman, “Exploring community smells in open-source: An automated approach,” IEEE Transactions on Software Engineering, vol. 47, no. 3, pp. 630–652, March 2021

[5] F. Palomba, D. Andrew Tamburri, F. Arcelli Fontana, R. Oliveto, A. Zaidman, and A. Serebrenik, “Beyond technical aspects: How do community smells influence the intensity of code smells?” IEEE Transactions on Software Engineering, vol. 47, no. 1, pp. 108–129, 2021

[6] E. Caballero-Espinosa, J. C. Carver, and K. Stowers, “Community smells—the sources of social debt: A systematic literature review,” Information and Software Technology, vol. 153, p. 107078, 2023

[7] A. Alliance, Agile Practice Guide, Project Management Institute, 2017: Agile Practice Guide

[8] H. Kniberg, Scrum and XP from the Trenches. Lulu. com, 2015

[9] V. One, “11th state of agile report,” Version One, Tech. Rep., 2016

[10] K. Schwaber and J. Sutherland, “Scrum guide,” Scrumguides.org, 11 2020

[14] A. Martini, V. Stray, and N. B. Moe, “Technical-, social- and process debt in large-scale agile: An exploratory case-study,” in Agile Processes in Software Engineering and Extreme Programming – Workshops, R. Hoda, Ed. Cham: Springer International Publishing, 2019

[15] SCRUMStudy, A Guide to the Scrum Body of Knowledge (SBOK® Guide) – Fourth edition. Scrumstudy, A Brand Of Vmedu, Inc, 2022

[16] D. A. Tamburri, R. Kazman, and W.-J. van den Heuvel, “Splicing community and software architecture smells in agile teams: An industrial study,” in Hawaii International Conference on System Sciences, 2019

[17] K. Charmaz, A construc¸ao da teoria fundamentada: Guia Pr ˜ atico para ´ Analise Qualitativa ´, ser. Metodos de Pesquisa. Penso, 2009

[18] C. Sarmento, T. Massoni, A. Serebrenik, G. Catolino, D. Tamburri, and F. Palomba, “Gender diversity and community smells: A double-replication study on brazilian software teams,” in 2022 IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER). Institute of Electrical and Electronics Engineers Inc., March 2022, Conference paper, pp. 273–283

[19] N. Tahsin and K. Sakib, “Refactoring community smells: An empirical study on the software practitioners of bangladesh,” in 2022 29th Asia-Pacific Software Engineering Conference (APSEC), vol. 2022-December. IEEE Computer Society, Dec 2019, Conference paper, pp. 43

[3] D. A. Tamburri, P. Kruchten, P. Lago, and H. v. Vliet, “Social debt in software engineering: insights from industry,” Journal of Internet Services and Applications, vol. 6, no. 1, p. 10

[4] D. A. Tamburri, F. Palomba, and R. Kazman, “Exploring community smells in open-source: An automated approach,” IEEE Transactions on Software Engineering, vol. 47, no. 3, pp. 630–652

[5] F. Palomba, D. Andrew Tamburri, F. Arcelli Fontana, R. Oliveto, A. Zaidman, and A. Serebrenik, “Beyond technical aspects: How do community smells influence the intensity of code smells?” IEEE Transactions on Software Engineering, vol. 47, no. 1, pp. 108–129

[6] E. Caballero-Espinosa, J. C. Carver, and K. Stowers, “Community smells—the sources of social debt: A systematic literature review,” Information and Software Technology, vol. 153, p. 107078

[7] A. Alliance, Agile Practice Guide, Project Management Institute, 2017: Agile Practice Guide

[8] H. Kniberg, Scrum and XP from the Trenches. Lulu. com, 2015

[9] V. One, “11th state of agile report,” Version One, Tech. Rep., 2016

[10] K. Schwaber and J. Sutherland, “Scrum guide,” Scrumguides.org, 11 2020

[14] A. Martini, V. Stray, and N. B. Moe, “Technical-, social- and process debt in large-scale agile: An exploratory case-study,” in Agile Processes in Software Engineering and Extreme Programming – Workshops, R. Hoda, Ed.

Green — the paper says it, and the page is printed. Red — no passage carries it, so treat that sentence as unverified. The same check runs on your own text: check a summary against its source, $5.

Improvements for AI systems

  1. Identification of Community Smells in Retrospectives: The improved system can be trained to detect patterns in retrospective discussions that align with known Community Smells, such as Organizational Silo or Lone Wolf, by analyzing member reports using a priori coding techniques.

  2. Strategy Definition and Tracking: The AI can be enhanced to explicitly map defined action plans to the specific Community Smell they are intended to refactor, addressing the finding that while strategies for refactoring are often formulated, their implementation and monitoring remain inconsistent.

  3. Monitoring Effectiveness: The system can be programmed to monitor the effectiveness of past actions by revisiting previous retrospective highlights, as suggested by participant P4's experience: "What we do is, in the following retrospectives, we review the improvements discussed in past retrospectives, we review those improvements and see if they are still having an impact and if we are managing to evolve in some way."

  4. Positive Reinforcement Integration: The AI can be designed to actively identify and prioritize positive aspects highlighted during meetings—such as Team Engagement (unity, commitment, collaboration)—to use them as reinforcement mechanisms for desired behaviors that help avoid Community Smells situations.

Abstract

Retrospective meetings play a vital role in agile development by facilitating team reflection on past work to enhance effectiveness. These meetings address various social aspects, including team dynamics, individual performance, processes, and technologies, ultimately leading to actions for improvement. Despite their importance, limited research has explored how these meetings handle forms of social debt, particularly Community Smells -- recurring dysfunctional patterns in team dynamics, such as poor communication or isolated work practices. This study seeks to understand how retrospective meetings address a few core Community Smells, examining whether these meetings help identify smells, make it possible to formulate refactoring strategies, support the monitoring of refactoring actions, and contribute to preventing the most prominent Community Smells. We conducted semi-structured interviews with 15 practitioners from diverse organizations who regularly participate in retrospective meetings. The interviewees shared their experiences with retrospectives, the challenges discussed, and subsequent improvement actions. The study focused on the four most cited Community Smells in the literature -- Lone Wolf, Organizational Silo, Radio Silence, and Black Cloud. Data was analyzed iteratively using a priori coding to examine Community Smells and inductive open coding inspired by Grounded Theory. The findings indicate that retrospective meetings indeed enable the identification of core Community Smells. However, while strategies for refactoring are often formulated, their implementation and monitoring remain inconsistent. Additionally, an emphasis on positive aspects during these meetings may help in preventing Community Smells. This study offers valuable insights to practitioners and researchers, highlighting the importance of addressing social debt in software development within agile practices.

Related papers