Three Case Studies in Adopting Agile

Moreira, Mario E.

doi:10.1007/978-1-4302-5840-7_24

Cited by 1 publication

(4 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Furthermore, we find two basic procedures (step by step [eg, Smits and Rilliet] or big bang [eg, Roman et al]). Most of the papers present case studies or experience reports (eg, Fry and Greene, Lifshitz et al, Maples, Moreira, and Papadopoulos). In this section, we present three approaches in more detail.…”

Section: Resultsmentioning

confidence: 99%

“…If a team is not satisfied with the process, it can—and should—improve it at any time. This is a specific characteristic of agile software development . Living these aspects is part of the cultural change that cannot and must not be enforced.…”

Section: Resultsmentioning

confidence: 99%

“…These approaches coincide in some aspects but differ in many others. [58][59][60][61][62] ). In this section, we present three approaches in more detail.…”

Section: Agile Transformation Approachesmentioning

confidence: 99%

“…This is a specific characteristic of agile software development. 12,61,81,94,97 Living these aspects is part of the cultural change 65,83,87 that cannot and must not be enforced. It does not suffice to implement the agile practices; internalizing the agile mind-set is the road to a successful agile company.…”

Section: Tasks On Organizational Levelmentioning

confidence: 99%

See 3 more Smart Citations

Transformation towards agile software product line engineering in large companies: A literature review

Klünder

Hohl

Prenner

et al. 2019

J Software Evolu Process

View full text Add to dashboard Cite

Almost all companies struggle with software systems that are getting increasingly complex. Therefore, in particular large companies often use software product lines, which provide an efficient way to manage software reuse as well as the high complexity. However, software product lines seem to be too slow to react to changes. Agile development approaches promise to meet this demand. At the same time, integrating an agile approach is not always easy. Consequently, there is a need for a transformation model that supports the agile transformation without harming the benefits of software product lines. In this paper, we present the results of a literature review regarding agile transformation in large software companies. Our results summarize the insights from 85 papers and present a list of 20 tasks and tasks that are recommended by several researchers to be considered during the transformation. On the basis of these results, we create an agile transformation model—the so‐called “agile hamburger”—that contains these tasks and preserves software product lines. Since the model is rather coarse grained and generic, we also support the adaption to different teams by presenting an assessment model tailored to the demands of the automotive domain.

show abstract

Section: Resultsmentioning

confidence: 99%

Section: Resultsmentioning

confidence: 99%

“…These approaches coincide in some aspects but differ in many others. [58][59][60][61][62] ). In this section, we present three approaches in more detail.…”

Section: Agile Transformation Approachesmentioning

confidence: 99%