To read this content please select one of the options below:

How do knowledge cycles happen in software development methodologies?

Andrea Raymundo Balle (School of Business, Pontifical Catholic University of Rio Grande do Sul, Rio Grande do Sul, Brazil)
Mírian Oliveira (School of Business, Pontifical Catholic University of Rio Grande do Sul, Rio Grande do Sul, Brazil)
Carla Curado (Department of Management, ISEG, Universidade de Lisboa, Lisbon, Portugal)
Felipe Nodari (School of Business, Pontifical Catholic University of Rio Grande do Sul, Rio Grande do Sul, Brazil)

Industrial and Commercial Training

ISSN: 0019-7858

Article publication date: 5 September 2018

Issue publication date: 5 November 2018

1037

Abstract

Purpose

The purpose of this paper is to illustrate how knowledge takes effect in different software development methodologies by relating them to different knowledge cycles.

Design/methodology/approach

The results were find by conducing a general review about the topics of knowledge cycles and software development methodologies.

Findings

All software development methodologies have knowledge cycles. In Waterfall methodology, the cycle followed is I-Space. For “code and fix,” there is a parallel with March’s cycle. Scrum shows a parallel with SECI cycle. Among the methodological options, results show there an increase in hierarchy, documentation, processes and explicit knowledge.

Research limitations/implications

Identified parallels of each methodology with knowledge cycles; established which Scrum artifacts are performed at each stage of SECI, which Waterfall steps correspond to I-Space phases and which activities in “code and fix” deal with exploration and exploitation of knowledge; and features shown increase or decrease according to the adoption of each methodology.

Practical implications

Results help knowledge sharing implementations and foster inter-team knowledge sharing, with the identification of the correct methodology-cycle match and the personalization of the strategy for each team based on the adopted methodology. Training for knowledge initiatives can be improved by determining how knowledge-sharing activities are incorporated on the determined series of actions established by the methodologies adopted on the firm.

Originality/value

The identification of how knowledge is generated and shared among teams in each methodology, the optimum pairing of the methodology and the parallels with the other, and the differences that emerge from the adopted knowledge cycle show that software projects are embedded in a knowledge cycle.

Keywords

Acknowledgements

The authors are grateful for the support provided by CAPES (Coordenação de Aperfeiçoamento de Pessoal de Nível Superior – Brasil, bolsista Andrea Raymundo Balle/Programa de Doutorado-sanduíche no Exterior/Processo no. 88881.132892/2016-01), CNPq (Conselho Nacional de Desenvolvimento Científico e Tecnológico – Brazil) and FCT (Fundação para a Ciência e Tecnologia - Portugal) under the project UID/SOC/04521/2013.

Citation

Balle, A.R., Oliveira, M., Curado, C. and Nodari, F. (2018), "How do knowledge cycles happen in software development methodologies?", Industrial and Commercial Training, Vol. 50 No. 7/8, pp. 380-392. https://doi.org/10.1108/ICT-04-2018-0037

Publisher

:

Emerald Publishing Limited

Copyright © 2018, Emerald Publishing Limited

Related articles