Making agile retrospectives more awesome

36Citations
Citations of this article
62Readers
Mendeley users who have this article in their library.

Abstract

According to the textbook [23], Scrum exists only in its entirety, where every component is essential to Scrum's success. However, in many organizational environments some of the components are omitted or modified in a way that is not aligned with the Scrum guidelines. Usually, such deviations result in missing the full benefits of Scrum [24]. Thereby, a Scrum process should be frequently inspected and any deviations should be corrected [23]. In this paper, we report on an Action Research project conducted in Intel Technology Poland to revise the work practices related to the Retrospective. During the focus group discussion in the company, retrospectives were generally judged ineffective because 'the same things are discussed over and over'. To cope with this challenge, we revitalized retrospectives by adopting collaborative games. The feedback received from three Scrum teams indicates that our approach improved participants' creativity, involvement, and communication, and produced better results than the standard retrospective.

Cite

CITATION STYLE

APA

Przybylek, A., & Kotecka, D. (2017). Making agile retrospectives more awesome. In Proceedings of the 2017 Federated Conference on Computer Science and Information Systems, FedCSIS 2017 (pp. 1211–1216). Institute of Electrical and Electronics Engineers Inc. https://doi.org/10.15439/2017F423

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free