Details
| Original language | English |
|---|---|
| Title of host publication | Proceedings - 2018 ACM/IEEE 3rd International Workshop on Emotion Awareness in Software Engineering, SEmotion 2018 |
| Pages | 25-31 |
| Number of pages | 7 |
| ISBN (electronic) | 9781450357517 |
| Publication status | Published - 2 Jun 2018 |
Publication series
| Name | Proceedings - International Conference on Software Engineering |
|---|---|
| ISSN (Print) | 0270-5257 |
Abstract
In software projects, a continuous exchange of information among team members is necessary to ensure a successful project. Meetings support this information exchange because they enable team members to share information simultaneously with all other team members. However, teams often get lost in endless discussions or developers do not gain a real benefit from a meeting. Consequently, participants are often frustrated by meetings. This leads to a negative mood and the project is endangered. To ensure the quality of information exchange and to prevent frustrated developers, meetings have to be assessed periodically. We ask the participants about their perception during a meeting because participants' satisfaction with the outcome is essential for project success. Hence, the definition of a good meeting bases on effectiveness, efficiency, and satisfaction. In order to measure perceived meeting success, we developed a feedback method and a tool applying it. To validate the method, we conducted a case study during two meetings and compared our results to an objective analysis. During the case study, our feedback method showed the advantages over the compared behavior-based approach. Using our method, teams can easily gather feedback about their meeting and decide whether future meetings need an improvement or can be abandoned. So the method helps teams to find the right manner of communication in meetings and to reduce the developers' frustration.
Keywords
- Communication, Human factors, Meeting success, Software development teams
ASJC Scopus subject areas
- Computer Science(all)
- Software
Cite this
- Standard
- Harvard
- Apa
- Vancouver
- BibTeX
- RIS
Proceedings - 2018 ACM/IEEE 3rd International Workshop on Emotion Awareness in Software Engineering, SEmotion 2018. 2018. p. 25-31 (Proceedings - International Conference on Software Engineering).
Research output: Chapter in book/report/conference proceeding › Conference contribution › Research › peer review
}
TY - GEN
T1 - Making meeting success measurable by participants' feedback
AU - Prenner, Nils
AU - Klünder, Jil
AU - Schneider, Kurt
N1 - DBLP's bibliographic metadata records provided through http://dblp.org/search/publ/api are distributed under a Creative Commons CC0 1.0 Universal Public Domain Dedication. Although the bibliographic metadata records are provided consistent with CC0 1.0 Dedication, the content described by the metadata records is not. Content may be subject to copyright, rights of privacy, rights of publicity and other restrictions. Publisher Copyright: © 2018 ACM. Copyright: Copyright 2018 Elsevier B.V., All rights reserved.
PY - 2018/6/2
Y1 - 2018/6/2
N2 - In software projects, a continuous exchange of information among team members is necessary to ensure a successful project. Meetings support this information exchange because they enable team members to share information simultaneously with all other team members. However, teams often get lost in endless discussions or developers do not gain a real benefit from a meeting. Consequently, participants are often frustrated by meetings. This leads to a negative mood and the project is endangered. To ensure the quality of information exchange and to prevent frustrated developers, meetings have to be assessed periodically. We ask the participants about their perception during a meeting because participants' satisfaction with the outcome is essential for project success. Hence, the definition of a good meeting bases on effectiveness, efficiency, and satisfaction. In order to measure perceived meeting success, we developed a feedback method and a tool applying it. To validate the method, we conducted a case study during two meetings and compared our results to an objective analysis. During the case study, our feedback method showed the advantages over the compared behavior-based approach. Using our method, teams can easily gather feedback about their meeting and decide whether future meetings need an improvement or can be abandoned. So the method helps teams to find the right manner of communication in meetings and to reduce the developers' frustration.
AB - In software projects, a continuous exchange of information among team members is necessary to ensure a successful project. Meetings support this information exchange because they enable team members to share information simultaneously with all other team members. However, teams often get lost in endless discussions or developers do not gain a real benefit from a meeting. Consequently, participants are often frustrated by meetings. This leads to a negative mood and the project is endangered. To ensure the quality of information exchange and to prevent frustrated developers, meetings have to be assessed periodically. We ask the participants about their perception during a meeting because participants' satisfaction with the outcome is essential for project success. Hence, the definition of a good meeting bases on effectiveness, efficiency, and satisfaction. In order to measure perceived meeting success, we developed a feedback method and a tool applying it. To validate the method, we conducted a case study during two meetings and compared our results to an objective analysis. During the case study, our feedback method showed the advantages over the compared behavior-based approach. Using our method, teams can easily gather feedback about their meeting and decide whether future meetings need an improvement or can be abandoned. So the method helps teams to find the right manner of communication in meetings and to reduce the developers' frustration.
KW - Communication
KW - Human factors
KW - Meeting success
KW - Software development teams
UR - http://www.scopus.com/inward/record.url?scp=85051144188&partnerID=8YFLogxK
U2 - 10.1145/3194932.3194933
DO - 10.1145/3194932.3194933
M3 - Conference contribution
T3 - Proceedings - International Conference on Software Engineering
SP - 25
EP - 31
BT - Proceedings - 2018 ACM/IEEE 3rd International Workshop on Emotion Awareness in Software Engineering, SEmotion 2018
ER -