Advertisement

Improving Communication in Scrum Teams

  • Marvin WyrichEmail author
  • Ivan BogicevicEmail author
  • Stefan Wagner
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 10611)

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.

Keywords

Scrum Agile communication Activity tracking 

Notes

Acknowledgements

We want to thank AEB GmbH who made this work possible and who provided the persons for the tool evaluation. We also thank Fujitsu Next who supported this work with a 5.000 Euro grant and the first prize of its Agile IT-Award 2016.

References

  1. 1.
    Dingsøyr, T., Moe, N.B.: Research challenges in large-scale agile software development. SIGSOFT Softw. Eng. Notes 38(5), 38–39 (2013)CrossRefGoogle Scholar
  2. 2.
    Ratanotayanon, S., Kotak, J., Sim, S.E.: After the Scrum: twenty years of working without documentation. In: Eighteenth International Conference on Software Engineering and Knowledge Engineering (SEKE), 5–7 July 2006, San Francisco, CA, USA (2006) 200–205Google Scholar
  3. 3.
    Visconti, M., Cook, C.R.: An overview of industrial software documentation practice. In: Proceedings of the XII International Conference of the Chilean Computer Science Society, SCCC 2002, pp. 179–186 (2002)Google Scholar
  4. 4.
    Forward, A., Lethbridge, T.C.: A survey. In: Proceedings of the 2002 ACM Symposium on Document Engineering, DocEng 2002, NY, USA, pp. 26–33Google Scholar
  5. 5.
    Lethbridge, T.C., Singer, J., Forward, A.: The state of the practice. IEEE Softw. 20(6), 35–39 (2003)CrossRefGoogle Scholar
  6. 6.
    Park, S.: A daily Scrum meeting summarizer for agile software development teams. Master thesis. University of Calgary, Canada, August 2007Google Scholar

Copyright information

© Springer International Publishing AG 2017

Authors and Affiliations

  1. 1.AEB GmbHStuttgartGermany
  2. 2.Institute of Software TechnologyUniversity of StuttgartStuttgartGermany

Personalised recommendations