Preparation and Facilitation of Retrospective Meeting in Scrum process
Abstract
Agile methods have become very popular in software development. They emphasise importance of collaboration and communication in successful product development. Scrum is one of the most popular agile methods and it involves a number of artefacts and practices. The retrospective is one of the practices. It is an activity that serves a purpose as a team meeting to improve development processes. It is a time-boxed event, which should be planned and facilitated in order to obtain the best outcome. The paper aims at identifying appropriate practices for organising and running successful retrospectives. The practices are identified in the paper along with their attributes and usage suggestions.
Keywords: |
Agile; retrospective; Scrum; sprint retrospective
|
Full Text: |
References
VersionOne, “The 11th Annual State of AgileTM Report,” Tech. Report, 2017.
J. Werewka and A. Spiechowicz, “Enterprise Architecture Approach to SCRUM Processes, Sprint Retrospective Example,” Proceedings of the 2017 Federated Conference on Computer Science and Information Systems, Sep. 2017. https://doi.org/10.15439/2017F96
M.-W. Chung and B. Drummond, “Agile at Yahoo! From the Trenches,” 2009
P. Diebold, J.-P. Ostberg, S. Wagner, and U. Zendler, “What Do Practitioners Vary in Using Scrum?,” Agile Processes in Software Engineering and Extreme Programming, Lecture Notes in Business Information Processing, vol. 212, pp. 40–51, Springer, 2015. https://doi.org/10.1007/978-3-319-18612-2_4
K. Schwaber, and J. Sutherland, Scrum Guide. OOPSLA, 2018.
O. McHugh, K. Conboy, and M. Lang, “Agile Practices: The Impact on rust in Software Project Teams,” IEEE Software, vol. 29, no. 3, pp. 71– 76, 2012. https://doi.org/10.1109/MS.2011.118
M. Cagatayli and E. Celebi, “Is BIG-5 personality feature set convenient for movie recommender systems,” 25th Signal Processing and Communications Applications Conference (SIU), May 2017. https://doi.org/10.1109/SIU.2017.7960343
A. Przybylek, and D. Kotecka, “Making agile retrospectives more awesome”, Computed Science and Information Systems (FedCSIS) 2017 Conference, Prague, Czech Republic, Sept. 3–6, 2017. https://doi.org/10.15439/2017f423
M. Maham, “Planning and Facilitating Release Retrospectives”, AGILE’08. Conference, Toronto, ON, Canada, Aug. 4–8, 2008.
M. Beedle et. al., “Manifesto for Agile Software Development,” 2001. [Online]. Available: http://agilemanifesto.org/authors.html
Scrum Framework: Chapter 2. [Online]. Available: https://innolution.com/essential-scrum
[Accessed: September 26, 2018].
E. Derby, and D. Larsen, Agile Retrospectives: Making Good Teams Great. Raleigh, North Carolina: The Pragmatic Bookshelf, 2006, pp. 157.
F. Kinoshita, “Practices of an Agile Team,” Agile 2008 Conference, 2008. https://doi.org/10.1109/Agile.2008.26
A. Meier, M. Kropp, G. Perellano, “Experience Report of Teaching Agile Collaboration and Values: Agile Software Development in Large Student Teams,” in IEEE 29th Conf. on Software Engineering Education and Training (CSEET), Dallas, TX, USA, April 5–6, 2016. https://doi.org/10.1109/CSEET.2016.30
M. Erder and P. Pureur, “What Type of People Are Software Architects?,” IEEE Software, vol. 34, no. 4, pp. 20–22, 2017. https://doi.org/10.1109/MS.2017.103
A. Morin, “Psychologists Say There Are Only 5 Kinds of People in the World. Which One Are You?,” Inc., 2016. [Online]. Available: https://www.inc.com/amy-morin/psychologists-say-there-are-5-personality-types-heres-how-to-tell-which-one-you-.html
[Accessed: May 5, 2018].
V.-P. Eloranta, K. Koskimies, and T. Mikkonen, “Exploring ScrumBut—An empirical study of Scrum anti-patterns,” Information and Software Technology, vol. 74, pp. 194–203, Jun. 2016. https://doi.org/10.1016/j.infsof.2015.12.003
Fun Retrospectives [Online]. Available: http://www.funretrospectives.com [Accessed: May 9, 2018].
DOI: 10.7250/itms-2018-0009
Refbacks
- There are currently no refbacks.
Copyright (c) 2018 Pēteris Ozoliņš
This work is licensed under a Creative Commons Attribution 4.0 International License.