Agile Adoption Strategies in the Context of Agile in the Large: FLEXI Agile Adoption Industrial Inventory

Rohunen, Anna; Rodríguez, Pilar; Kuvaja, Pasi; Krzanik, Lech; Markkula, Jouni; Turhan, Burak

doi:10.1007/978-3-642-13054-0_50

Cited by 3 publications

(3 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…8) Agility: Agility clearly relates to the use, level of, and confidence around agile methods [35]. The adoption of agile methods is an established fact in software engineering literature [36]; however, the factors that lead to successful or failing attempts at harnessing agile methods are still left largely to speculation. In the scope of our topic modelling exercise, the following terms were reported: self*, user*, value*, pressure*, pair*, test*, and human*; 9) User-centric design: Finally, in the scope of topics relating to people, internal software characteristics, as well as best practices, we reported several factors and recurrent keywords relating to user-centric design [37], that is, the framework of engineering where usability goals, user characteristics, environment, and workflows are given attention at each stage of the (software) design process.…”

Section: B Success and Failure Distilled: Topic Modeling Resultsmentioning

confidence: 99%

Success and Failure in Software Engineering: A Followup Systematic Literature Review

Tamburri

Palomba

Kazman

2021

IEEE Trans. Eng. Manage.

View full text Add to dashboard Cite

Success and failure in software engineering are still among the least understood phenomena in the discipline. In a recent special journal issue on the topic, Mäntylä et al. started discussing these topics from different angles; the authors focused their contributions on offering a general overview of both topics without deeper detail. Recognizing the importance and impact of the topic, in this article we have executed a followup, more in-depth systematic literature review with additional analyses beyond what was previously provided. These new analyses offer: a grounded-theory of success and failure factors, harvesting over 500+ factors from the literature; 14 manually validated clusters of factors that provide relevant areas for success-and failure-specific measurement and risk-analysis; a quality model composed of previously unmeasured organizational structure quantities which are germane to software product, process, and community quality. We show that the topics of success and failure deserve further study as well as further automated tool support, e.g., monitoring tools and metrics able to track the factors and patterns emerging from this article. This article provides managers with risks as well as a more fine-grained analysis of the parameters that can be appraised to anticipate the risks.

show abstract

Section: B Success and Failure Distilled: Topic Modeling Resultsmentioning

confidence: 99%

Success and Failure in Software Engineering: A Followup Systematic Literature Review

Tamburri

Palomba

Kazman

2021

IEEE Trans. Eng. Manage.

View full text Add to dashboard Cite

show abstract

“…The adoption of agile methods is an established fact in software engineering literature [36]; however, the factors that lead to successful or failing attempts at harnessing agile methods are still left largely to speculation. In the scope of our topic modelling exercise, the following terms were reported: self*, user*, value*, pressure*, pair*, test*, human*; 9) User-Centric Design.…”

Section: Domainmentioning

confidence: 99%

Success and Failure in Software Engineering: a Followup Systematic Literature Review

Tamburri¹,

Member-at-Large²,

Palomba³

et al. 2020

Preprint

View full text Add to dashboard Cite

Success and failure in software engineering are still among the least understood phenomena in the discipline. In a recent special journal issue on the topic, M äntyl ä et al. started discussing these topics from different angles; the authors focused their contributions on offering a general overview of both topics without deeper detail. Recognising the importance and impact of the topic, we have executed a followup, more in-depth systematic literature review with additional analyses beyond what was previously provided. These new analyses offer: (a) a grounded-theory of success and failure factors, harvesting over 500+ factors from the literature; (b) 14 manually-validated clusters of factors that provide relevant areas for successand failure-specific measurement and risk-analysis; (c) a quality model composed of previously unmeasured organizational structure quantities which are germane to software product, process, and community quality. We show that the topics of success and failure deserve further study as well as further automated tool support, e.g., monitoring tools and metrics able to track the factors and patterns emerging from our study. This paper provides managers with risks as well as a more fine-grained analysis of the parameters that can be appraised to anticipate the risks.

show abstract

“…To investigate the aforementioned questions, we conduct an exploratory industrial study aimed at understanding organisational structures and their efficacy with a goal of offering practical insights into such structures and their operational parameters. We focus our study on a specific kind of organisation-software teams-that have adopted agile methods, given the aforementioned great penetration of agile in industry and their reliance on high functioning organisational structures [76]. At the same time, much literature [44], [32], [4], [11] and debate [33], [86] has focused on the mapping between organizational and software structures without clearly providing guidelines that practitioners can use to influence these structures in their own organizations.…”

Section: Introductionmentioning

confidence: 99%

On the Relationship Between Organizational Structure Patterns and Architecture in Agile Teams

Tamburri

Kazman²,

Fahimi³

2023

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

Forming members of an organisation into coherent groups or teams is an important issue in any large-scale software engineering endeavour, especially so in agile software development where teams rely heavily on self-organisation and organisational flexibility. But is there a recurrent organisational structure pattern in agile software engineering teams? and if so what does that pattern imply, in terms of software architecture quality? We address these questions using mixed-methods research in industry featuring interviews, surveys, and Delphi studies of real agile teams. In our study of 30 agile software teams we found that, out of seven organisational structure patterns that recur across our dataset, a single organisational pattern occurs over 37% of the time. This pattern: (a) reflects young communities (1-12 months old); (b) disappears in established ones (13+ months); and (c) reflects the highest number of architecture smells reported. Finally, we observe a negative correlation between a proposed organisational measure and architecture smells. On the one hand, these insights may serve to aid architects in designing not only their architectures but also their communities to best support their co-evolution. On the other hand, we observe that organisational structures in software engineering influence much more than simply software architectures, and we expect our results to lay the foundations of more structured and rigorous approaches to organisational structure studies and use in software engineering research and practice.

show abstract

Agile Adoption Strategies in the Context of Agile in the Large: FLEXI Agile Adoption Industrial Inventory

Cited by 3 publications

References 3 publications

Success and Failure in Software Engineering: A Followup Systematic Literature Review

Success and Failure in Software Engineering: A Followup Systematic Literature Review

Success and Failure in Software Engineering: a Followup Systematic Literature Review

On the Relationship Between Organizational Structure Patterns and Architecture in Agile Teams

Contact Info

Product

Resources

About