Counteracting Agile Retrospective Problems with Retrospective Activities

  • Christoph MatthiesEmail author
  • Franziska Dobrigkeit
  • Alexander Ernst
Conference paper
Part of the Communications in Computer and Information Science book series (CCIS, volume 1060)


Retrospective meetings are a fundamental part of Agile software development methods. Effective retrospectives can positively impact teamwork, productivity, and work satisfaction. In this paper, we focus on problems that commonly occur during these meetings. To address them, we suggest retrospective activities that are already used in practice. These activities provide structure and guide the team through the meeting. We created a mapping between a selection of these activities and the problems they attempt to solve. We evaluated the created mapping through multiple case studies with software development teams in educational and professional contexts. Our results verify the existence of a relationship between specific retrospective activities and connected retrospective problems. Furthermore, using observational studies we could verify parts of the created problem-activity mapping.


Software process improvement SPI Agile software development Retrospective meeting 


  1. 1.
    Amin, H.: Do’s and don’ts of agile retrospectives (2014). Accessed 02 Jan 2018
  2. 2.
    Atherton, R.: Guess Who? (2016). . Accessed 16 Jan 2018
  3. 3.
    Baldauf, C.: Retromat - Run Great Agile Retrospectives!. Leanpub, Layton (2018)Google Scholar
  4. 4.
    Beecham, S., O’Leary, P., Baker, S., Richardson, I., Noll, J.: Making software engineering research relevant. Computer 47(4), 80–83 (2014)CrossRefGoogle Scholar
  5. 5.
    Bowley, R., Linders, B.: Common ailments & cures (2018). Accessed 11 Jan 2019
  6. 6.
    Caroli, P., Caetano, T.: Fun Retrospectives - Activities and Ideas for Making Agile Retrospectives More Engaging. Leanpub, Layton (2015)Google Scholar
  7. 7.
    Cohen, D., Crabtree, B.: Qualitative research guidelines project (2006).
  8. 8.
    De Bono, E.: Six Thinking Hats. Penguin, London (2017)Google Scholar
  9. 9.
    Derby, E., Larsen, D.: Agile Retrospectives: Making Good Teams Great. Pragmatic Bookshelf Series, Pragmatic Bookshelf (2006)Google Scholar
  10. 10.
    Devanbu, P., Zimmermann, T., Bird, C.: Belief & evidence in empirical software engineering. In: Proceedings of the 38th International Conference on Software Engineering - ICSE 2016. pp. 108–119. ACM Press, New York (2016)Google Scholar
  11. 11.
    Dieu, L.: Stages of agile retrospective (2016). Accessed 16 Jan 2019
  12. 12.
    Dobrigkeit, F., de Paula, D., et al.: The best of three worlds-the creation of innodev a software development approach that integrates design thinking, scrum and lean startup. In: DS 87–8 Proceedings of the 21st International Conference on Engineering Design, ICED 2017, vol. 8, pp. 319–328 (2017)Google Scholar
  13. 13.
    Evans, N.: Destroying collaboration and knowledge sharing in the workplace: a reverse brainstorming approach. Knowl. Manag. Res. Pract. 10(2), 175–187 (2012)CrossRefGoogle Scholar
  14. 14.
    Flick, U.: An Introduction to Qualitative Research. Sage Publications Limited, Thousand Oaks (2009)Google Scholar
  15. 15.
    Fowler, M., Highsmith, J.: The agile manifesto. Software Development (2001)Google Scholar
  16. 16.
    Gold, R.L.: Roles in sociological field observations. Soc. Forces 36, 217–223 (1958)CrossRefGoogle Scholar
  17. 17.
    Gonçalves, L.: 9 deadly agile retrospectives antipatterns every scrum master must avoid (2017). Accessed 31 Jan 2019
  18. 18.
    Gonçalves, L., Linders, B.: Getting Value out of Agile Retrospectives - A Toolbox of Retrospective Exercises. Lulu. com (2014)Google Scholar
  19. 19.
    Guest, T.: #tweetmysprint (2019). Accessed 16 Jan 2019
  20. 20.
    Hohmann, L.: Innovation Games: Creating Breakthrough Products Through Collaborative Play. Pearson Education, London (2006)Google Scholar
  21. 21.
    Jovanovic, M., Mesquida, A.-L., Mas, A.: Process improvement with retrospective gaming in agile software development. Systems, Software and Services Process Improvement. CCIS, vol. 543, pp. 287–294. Springer, Cham (2015). Scholar
  22. 22.
    Jovanović, M., Mesquida, A.L., Radaković, N., Mas, A.: Agile retrospective games for different team development phases. J. Univ. Comput. Sci. 22(12), 1489–1508 (2016)Google Scholar
  23. 23.
    Kerth, N.L.: The ritual of retrospectives: how to maximize group learning by understanding past projects. Softw. Test. Qual. Eng. 2(5), 53–57 (2000)Google Scholar
  24. 24.
    Komus, A., Kuberg, M.: Abschlussbericht: Status quo agile 2016/2017. Studie über Erfolg und Anwendungsformen von agilen Methoden (2017)Google Scholar
  25. 25.
    Krivitsky, A.: Agile Retrospective Kickstarter. Leanpub, Layton (2015)Google Scholar
  26. 26.
    Kua, P.: The Retrospective Handbook: A guide for agile teams. CreateSpace Independent Publishing Platform, Scotts Valley (2013)Google Scholar
  27. 27.
    Larsen, D.: Circles and soup (2010). Accessed 16 Jan 2019
  28. 28.
    Larsen, D., Shore, J.: Partnerships and possibilities blog (2019). Accessed 16 Jan 2019
  29. 29.
    Leung, W.C.: How to design a questionnaire. Stud. BMJ 9, 171–216 (2001)Google Scholar
  30. 30.
    Loeffler, M.: Improving Agile Retrospectives: Helping Teams Become More Efficient. Addison-Wesley, Boston (2017)Google Scholar
  31. 31.
    Matthies, C.: Feedback in scrum: data-informed retrospectives. In: Proceedings of the 41st International Conference on Software Engineering: Companion Proceedings, ICSE 2019, pp. 198–201. IEEE Press (2019)Google Scholar
  32. 32.
    Matthies, C., Dobrigkeit, F., Hesse, G.: An additional set of (automated) eyes: chatbots for agile retrospectives. In: 1st International Workshop on Bots in Software Engineering (BotSE) (2019)Google Scholar
  33. 33.
    Matthies, C., Teusner, R., Hesse, G.: Beyond surveys: analyzing software development artifacts to assess teaching efforts. In: 2018 IEEE Frontiers in Education Conference (FIE), pp. 1–9. IEEE (2018)Google Scholar
  34. 34.
    Mesquida, A.-L., Jovanovic, M., Mas, A.: Process improving by playing: implementing best practices through business games. In: Kreiner, C., O’Connor, R.V., Poth, A., Messnarz, R. (eds.) EuroSPI 2016. CCIS, vol. 633, pp. 225–233. Springer, Cham (2016). Scholar
  35. 35.
    Mesquida, A.-L., Karać, J., Jovanović, M., Mas, A.: A game toolbox for process improvement in agile teams. In: Stolfa, J., Stolfa, S., O’Connor, R.V., Messnarz, R. (eds.) EuroSPI 2017. CCIS, vol. 748, pp. 302–309. Springer, Cham (2017). Scholar
  36. 36.
    Northwood, C.: Planning Your Work, pp. 11–46. Apress, Berkeley (2018)Google Scholar
  37. 37.
    Pries-Heje, J., Johansen, J.: SPI Manifesto. European system & software process improvement and innovation (2010)Google Scholar
  38. 38.
    Remarczyk, M.: “Guess Who?” (2015). Accessed: 16 Jan 2019
  39. 39.
    Rubin, K.S.: Essential Scrum: A Practical Guide to the Most Popular Agile Process. Addison-Wesley, Boston (2012)Google Scholar
  40. 40.
    Schwaber, K.: Agile Project Management with Scrum. Microsoft Press, Redmond (2004)zbMATHGoogle Scholar
  41. 41.
    Schwaber, K., Sutherland, J.: The Scrum Guide - The Definitive Guide to Scrum: The Rules of the Game. Technical report (2017)Google Scholar
  42. 42.
    Scrum Alliance: The State of Scrum Report 2017 / 2018. Technical report (2018)Google Scholar
  43. 43.
    Todorov, M.: Story Oscars (2019). Accessed 16 Jan 2019
  44. 44.
    VersionOne Inc.: The 12th Annual State of Agile Report. Technical report (2018)Google Scholar
  45. 45.
    Wiki Contributors: Statistics (2019). Accessed 31 Jan 2019
  46. 46.
    Wilson, C.E.: Brainstorming pitfalls and best practices. ACM Interact. 13(5), 50 (2006)CrossRefGoogle Scholar

Copyright information

© Springer Nature Switzerland AG 2019

Authors and Affiliations

  1. 1.Hasso Plattner InstituteUniversity of PotsdamPotsdamGermany

Personalised recommendations