Applying the Squad Health Check Model to agile times at a financial institution
DOI:
https://doi.org/10.33448/rsd-v9i2.2212Keywords:
Health check; Software development; Agile; Scrum; Maturity.Abstract
In this work were discussed through a qualitative approach, instruments to measure maturity in software development using Scrum applied to 17 teams of a mixed economy financial institution. The practice of maturity measurement is already present even in teams that use traditional method of development, using models such as CMMI - Capability Maturity Model Integration and ISO / IEC 15504 among others, but which are quite linear in their levels. Thus, the analyzed company chose to experiment with the use of a more informal and lighter model to holistically obtain the perception of its teams regarding four dimensions: culture, organizational, technical challenges and insights received from customers and users, to highlight improvement needs and subsequent proposition of action plans. The objective of this paper is to analyze the application of Squad Health Check Model (SHCM) in a large financial institution that uses the Scrum method for agile development of digital products. This article discusses the nature of SHCM, its steps, and its application in a specific context. The results presented are based on the compilation of perceptions of the 17 agile teams that applied the Spotify Squad Health Check Model, which allowed us to verify that the use of the model proposed by Spotify analysts can be adapted to the reality of Brazilian companies because it presented assertive results. Failures and structural difficulties were evidenced by the model that could be found by analyzing the internal processes of the institution.
References
Ahmed, F., & Capretz, L. F. (2011). An architecture process maturity model of software product line engineering. Innovations in Systems and Software Engineering, 7(3), 191.
Cauchick-Miguel, P. A., et al. (2018). Metodologia de Pesquisa em Engenharia de Produção e Gestão de Operações. São Paulo: Elsevier.
Fontana, R. M., Fontana, I. M., da Rosa Garbuio, P. A., Reinehr, S., & Malucelli, A. (2014). Processes versus people: How should agile software development maturity be defined?. Journal of Systems and Software, 97, 140-155.
Gill, M., & VanBoskirk, S. (2016). The Digital Maturity Model 4.0. Benchmarks: Digital business transformation playbook. rapport de recherche de la firme Forrester, 22 janvier 2016.
Kerzazi, N. (2015, October). Conceptual alignment between SPEM-based processes and CMMI. In 2015 10th International Conference on Intelligent Systems: Theories and Applications (SITA) (pp. 1-9). IEEE.
Kniberg, H. (2014). Spotify Engineering Culture part 1. Spotify Labs, 27. Retirado de < https://labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/>.
Kniberg, H. (2014). Squad Health Check model–visualizing what to improve. Retirado de .
Pane, E. S., & Sarno, R. (2015). Capability maturity model integration (CMMI) for optimizing object-oriented analysis and design (OOAD). Procedia Computer Science, 72, 40-48.
Remane, G., Hanelt, A., Wiesboeck, F., & Kolbe, L. (2017). Digital Maturity in Traditional Industries–An Exploratory Analysis. Research Papers, Retirado de <https://aisel.aisnet.org/ecis2017_rp/10>.
Schwaber, K. & Sutherland, J. (2017). The Scrum Guide - The Definitive Guide To Scrum: The Rules Of The Game. Scrum.org, Nov-2017. Retirado de < https://www.scrum.org/resources/scrum-guide>
Team, C. P. (2010). CMMI® for Development, Version 1.3, Improving processes for developing better products and services. no. CMU/SEI-2010-TR-033. Software Engineering Institute. Retirado de <https://resources.sei.cmu.edu/asset_files/TechnicalReport/2010_005_ 001_15287.pdf>
Downloads
Published
How to Cite
Issue
Section
License
Authors who publish with this journal agree to the following terms:
1) Authors retain copyright and grant the journal right of first publication with the work simultaneously licensed under a Creative Commons Attribution License that allows others to share the work with an acknowledgement of the work's authorship and initial publication in this journal.
2) Authors are able to enter into separate, additional contractual arrangements for the non-exclusive distribution of the journal's published version of the work (e.g., post it to an institutional repository or publish it in a book), with an acknowledgement of its initial publication in this journal.
3) Authors are permitted and encouraged to post their work online (e.g., in institutional repositories or on their website) prior to and during the submission process, as it can lead to productive exchanges, as well as earlier and greater citation of published work.