Supporting Large-Scale Agile Development with Domain-Driven Design

Uludağ, Ömer; Hauder, Matheus; Kleehaus, Martin; Schimpfle, Christina; Matthes, Florian

doi:10.1007/978-3-319-91602-6_16

Cited by 19 publications

(18 citation statements)

References 14 publications

(30 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…[7], [20]) or they study the overall methods in a collective, aggregated manner that does not allow researchers or practitioners to compare and contrast these methods (e.g. [6], [8], [9], [18], [21], [22], [23]). This study is also the first to include custom-built methods (RQ1).…”

Section: Contributions Of the Studymentioning

confidence: 99%

“…After removing duplicates, the titles and abstracts of the remaining articles were read. We identified 19 relevant systematic literature reviews in this area ( [4], [6], [7], [9], [17], [20], [21], [22], [23], [33], [34], [35], [36], [37], [38], [39], [40], [41], [42]). By reading the titles of articles that cite these reviews, we identified three more relevant articles ( [18], [43], [44]).…”

Section: Related Workmentioning

confidence: 99%

“…challenges, barriers, or success factors were reported in an aggregated manner and did not provide method-specific information. This is also the case of the agile and SPL studies [33], [37] or Lean [36], [44] Ten reviews on large-scale agile development were considered most relevant to this study ( [6], [7], [8], [9], [18], [20], [21], [22], [23], [43]). In terms of the review method, only five out of ten reviews were guided by well-known literature review approaches ( [6], [7], [21], [22], [23]).…”

Section: Related Workmentioning

confidence: 99%

See 2 more Smart Citations

Comparing Methods for Large-Scale Agile Software Development: A Systematic Literature Review

Edison

Wang

Conboy

2022

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

Following the highly pervasive and effective use of agile methods at the team level, many software organisations now wish to replicate this success at the organisational level, adopting large-scale agile methods such as SAFe, Scrum-at-Scale, and others. However, this has proven significantly challenging. An analysis of the extant literature reveals a disparate set of studies across each individual method, with no cross-method comparison based on empirical evidence. This systematic literature review compares the main large-scale agile methods, namely SAFe, LeSS, Scrum-at-Scale, DAD, and the Spotify model. It is the first study to analyse and compare each of the method's principles, practices, tools, and metrics in a standardised manner. For each method, it presents not just the original method specifications but also all extensions and modifications to each method proposed by subsequent empirical research. It includes in this comparison not just commercial large-scale methods but also those that have been custom-built in organisations such as Nokia, Ericsson, and others. Based on the findings reported in this study, practitioners can make a more informed decision as to which commercial method or method component or, indeed, custom-built method is better suited to their needs. Our study reveals a number of theoretical and practical issues in the current literature, such as an emphasis on the practices of commercial frameworks at the expense of their underlying principles, or indeed any of the custom method. A set of challenges and success factors associated with the use of large-scale agile methods are identified. The study also identifies a number of research gaps to be addressed across methods.

show abstract

Section: Contributions Of the Studymentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Comparing Methods for Large-Scale Agile Software Development: A Systematic Literature Review

Edison

Wang

Conboy

2022

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

show abstract

“…These factors often result in coordination challenges and additional coordination efforts [9,27]. For instance, an overarching figure or role, as well as appropriate methods, are required to coordinate the teams and address team-crossing challenges [11]. However, inter-team coordination in software ecosystems rises additional complications as the teams are distributed over several organizations who rarely share common goals or strategies nor a centralized control figure who coordinates them.…”

Section: Related Workmentioning

confidence: 99%

“…The application of scaled agile methods has already been investigated to a great extent, e.g. in [3,[6][7][8][9][10], and [11]. The focus, however, lies mostly on large-scale projects or multiteams within one organization.…”

Section: Introductionmentioning

confidence: 99%

Scaling Agile Beyond Organizational Boundaries: Coordination Challenges in Software Ecosystems

Figalist

Elsner

Bosch

et al. 2019

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

The shift from sequential to agile software development originates from relatively small and co-located teams but soon gained prominence in larger organizations. How to apply and scale agile practices to fit the needs of larger projects has been studied to quite an extent in previous research. However, scaling agile beyond organizational boundaries, for instance in a software ecosystem context, raises additional challenges that existing studies and approaches do not yet investigate or address in great detail. For that reason, we conducted a case study in two software ecosystems that comprise several agile actors from different organizations and, thereby, scale development across organizational boundaries, in order to elaborate and understand their coordination challenges. Our results indicate that most of the identified challenges are caused by long communication paths and a lack of established processes to facilitate these paths. As a result, the participants in our study, among others, experience insufficient responsivity, insufficient communication of prioritizations and deliverables, and alterations or loss of information. As a consequence, agile practices need to be extended to fit the identified needs.

show abstract

DOMICO: Checking conformance between domain models and implementations

Zhong,

Zhang,

Huang

et al. 2023

Softw Pract Exp

View full text Add to dashboard Cite

As a predominant design method for microsservices architecture (MSA), domain‐driven design (DDD) utilizes a series of standard patterns in both models and implementations to effectively support the design of architectural elements. However, an implementation may deviate from its original domain model that uses certain patterns. The deviation between a domain model and its implementation is a type of architectural drift, which needs to be detected promptly. This paper proposes an approach, namely DOMICO, to check the conformance between the domain model and its implementation, by which the conformance is formalized by defining eight common structural patterns of domain modeling and their representations in both models and the corresponding source code. Based on the formalization, our approach can not only identify the discrepancies (e.g., divergence, absence, and modification) with respect to pattern elements, but also detect possible violations of 24 compliance rules imposed by the patterns. To validate DOMICO, we performed a case study to investigate its use in a supply chain project and its performance. The results show that DOMICO can accurately identify 100% inconsistency issues in the cases examined. As the first conformance checking approach for DDD, DOMICO can be integrated into the regular domain modeling process and help ensure the conformity of microservice implementations to models.

show abstract

Supporting Large-Scale Agile Development with Domain-Driven Design

Cited by 19 publications

References 14 publications

Comparing Methods for Large-Scale Agile Software Development: A Systematic Literature Review

Comparing Methods for Large-Scale Agile Software Development: A Systematic Literature Review

Scaling Agile Beyond Organizational Boundaries: Coordination Challenges in Software Ecosystems

DOMICO: Checking conformance between domain models and implementations

Contact Info

Product

Resources

About