Improving communication in scrum teams

Marvin Wyrich, Ivan Bogicevic, Stefan Wagner

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

2 Scopus citations

Abstract

Communication in teams is an important but difficult issue. In a Scrum development process, we use meetings like the Daily Scrum to inform others about important problems, news and events in the project. When persons are absent due to holiday, illness or travel, they miss relevant information because there is no guarantee that the content of these meetings is documented. We present a concept and a Twitter-like tool to improve communication in a Scrum development process. We take advantage out of the observation that many people do not like to create documentation, but they do like to share what they did. We used the tool in industrial practice and observed an improvement in communication.

Original languageEnglish
Title of host publicationProduct-Focused Software Process Improvement -18th International Conference, PROFES 2017, Proceedings
EditorsBurak Turhan, Dietmar Winkler, Federica Sarro, Marcos Kalinowski, Daniel Mendez Fernandez, Michael Felderer
PublisherSpringer Verlag
Pages602-605
Number of pages4
ISBN (Print)9783319699257
DOIs
StatePublished - 2017
Externally publishedYes
Event18th International Conference on Product-Focused Software Process Improvement, PROFES 2017 - Innsbruck, Austria
Duration: 29 Nov 20171 Dec 2017

Publication series

NameLecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
Volume10611 LNCS
ISSN (Print)0302-9743
ISSN (Electronic)1611-3349

Conference

Conference18th International Conference on Product-Focused Software Process Improvement, PROFES 2017
Country/TerritoryAustria
CityInnsbruck
Period29/11/171/12/17

Keywords

  • Activity tracking
  • Agile communication
  • Scrum

Fingerprint

Dive into the research topics of 'Improving communication in scrum teams'. Together they form a unique fingerprint.

Cite this