Best Practices for Software Maturity Improvement: A GÉANT Case Study

Walter, Bartosz; Marović, Branko; Garnizov, Ivan; Wolski, Marcin; Todosijevic, Andrijana

doi:10.1007/978-3-030-56441-4_3

Cited by 7 publications

(10 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Walter et al [68] proposed a maturity model designed for the software development teams of GÉANT, a large organization with around 30 software projects and around 20 development teams. Such a model addresses issues related to the geographic distribution of the team, percentage of the dispersed workforce, and parallel involvement in other project priorities.…”

Section: Géantmentioning

confidence: 99%

Maturity Models for Managing People in Software Development Teams: A Systematic Literature Review

2022

RHSS

View full text Add to dashboard Cite

Human factors are fundamental to software development, hence the need to understand people-oriented maturity models in development teams. This article aims to identify the maturity models for people management in software development teams cited in the literature, in order to identify evidence about their use, benefits and limitations, and the human aspects involved. A systematic literature review (SLR) was carried out, where automatic searches were done in four search engines, congresses in the area of human factors within software engineering, in addition to a manual search. Evidence indicates that there are numerous models aimed at developing people in development teams, but few are applied. Models based on observation and informal discussion were found, as well as non-validated models, indicating the scarcity of models applicable to people in software engineering. However, complete but complex models were also found, indicating that a more transparent, dynamic and simple process is needed for people's development. In the observed human factors, emphasis is placed on communication, collaboration, knowledge, learning, self-management, motivation and skills in general.

show abstract

Section: Géantmentioning

confidence: 99%

Maturity Models for Managing People in Software Development Teams: A Systematic Literature Review

2022

RHSS

View full text Add to dashboard Cite

show abstract

“…In response to that, work on Common Best Practices (CBPs) 1 and G ÉANT Software Maturity Model (SMM) 2 has started in 2018. The preliminary versions of both frameworks have been reviewed by selected software teams, which resulted in revisions that are currently implemented in practice [4,6].…”

Section: Contextmentioning

confidence: 99%

“…The CBPs for G ÉANT software teams provide directional guidance and recommendations on how to achieve specific goals defined in the SMM [5], but they need to be customized and adapted by the teams to the local context. As a result, the generality of recommendations included in a practice appears to be a balanced trade-off between delivering actionable procedures on one hand and ensuring the necessary generality on the other [6]. A catalogue of Software Best Practices presented in Table 1 covers all relevant aspects of software development that have been identified in G ÉANT in response to the recognized needs and objectives [13] and is one of the tools contributing to software governance.…”

Section: Contextmentioning

confidence: 99%

“…In previous papers [4,5,6] we presented earlier stages of developing an SPI process in G ÉANT, a pan-European project that originated from networking, but it currently includes also an important component of network-based services supported by software-intensive systems. G ÉANT software teams are diverse in terms of language, nationality and work culture.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Monitoring the adoption of SPI-related best practices. An experience report

Walter,

Marovic,

Garnizov

et al. 2021

Preprint

Self Cite

View full text Add to dashboard Cite

Software Process Improvement requires significant effort related not only to the identification of relevant issues and providing an adequate response to them but also to the implementation and adoption of the changes. Best practices provide recommendations to software teams on how to address the identified objectives in practice, based on aggregated experience and knowledge. In the paper, we present the G ÉANT experience and observations from the process of adopting the best practices, and present the setting we have been using.

show abstract

“…In previous papers, we have presented various aspects of the SPI-related challenges, approaches and results of developing and operating an SPI process in G ÉANT, a distributed multi-national European project focused on innovation and exploration of new research directions within networking and software [4,5,6]. It faces specific challenges, which needs to be reflected in the SPI process.…”

Section: Introductionmentioning

confidence: 99%