Interface Problems of Agile in a Non-agile Environment

Theobald, Sven; Diebold, Philipp

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

Cited by 12 publications

(11 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…More interfaces not explicitly addressed by SAFe exist, e.g., synchronizing agile development with a product line approach [ 18 ]. An initial overview of the dependencies of agile teams on their environment is provided by [ 2 ]. A possible next step for research would be to refine this classification of interfaces to understand what concrete dependencies exist in order to be able to find solutions.…”

Section: Discussion and Related Workmentioning

confidence: 99%

“…Challenges mentioned at the workshop A-Teams in 2019 [ 5 ] were that teams have “too many dependencies to others”, a “lack of organizational support”, and “part-time resources”, which are all “interface problems” [ 2 ]. In the 2018 A-teams workshop [ 6 ], concerns like “coordination”, “organizational context supporting autonomy”, or “leadership” also address interface problems and were rated as having the highest priority.…”

Section: Motivation and Research Approachmentioning

confidence: 99%

“…Therefore, agile software development teams have to collaborate with many different parties. In addition, teams need the support of different organizational functions like marketing, sales, or the human resources department [ 2 ]. Especially in established large companies, it is difficult to change the existing hierarchical structures, silo knowledge, and traditional mindset.…”

Section: Introductionmentioning

confidence: 99%

“…For the development of safety-critical products like cars, traditional systems engineering processes are still in use and define a framework for the underlying agile, hybrid, or traditional subprojects [ 3 ]. This gap between the agile way of working of development teams and the traditional approach of the surrounding organization leads to problems regarding the collaboration between an agile team and its environment, so-called interface problems [ 2 ]. Since the environment is important in order to allow agile teams to thrive [ 4 ], efficient collaboration between agile teams and the environment on which they depend is important.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Dependencies of Agile Teams – An Analysis of the Scaled Agile Framework

Theobald

Schmitt

2020

Lecture Notes in Business Information Processing

Self Cite

View full text Add to dashboard Cite

Context: Agile teams are small teams with 3 to 9 members. In complex development endeavors such as systems engineering, an agile team has many dependencies, since it is not possible to incorporate all specialist skills into one team. Frameworks like the Scaled Agile Framework (SAFe) describe how agile teams operate in a larger setting. Objective: The aim of this study is to analyze how agile teams collaborate with their organizational environment. Method: We analyzed SAFe to investigate how much guidance it provides concerning the collaboration between agile teams and their environment. Results: The results show that many different organizational parts exist with which agile teams have to collaborate. SAFe mentions concepts like shared services, system teams, or business teams, but there is no further guidance on collaboration with the agile team. Conclusion: We motivate future research into guidelines for efficient collaboration of agile teams with their organizational environment.

show abstract

Section: Discussion and Related Workmentioning

confidence: 99%

Section: Motivation and Research Approachmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Dependencies of Agile Teams – An Analysis of the Scaled Agile Framework

Theobald

Schmitt

2020

Lecture Notes in Business Information Processing

Self Cite

View full text Add to dashboard Cite

show abstract

“…Theobald and Diebold 29 and Kusters et al 30 investigate the problems at the interfaces between agile and traditional processes, yet only here a parallel existence of both processes is considered. Theobald et al 29 identified in the context of a workshop problems on the interfaces between the team and the project, the project and the organization, to the customer, to subcontractors, and to regulatory authorities. Kusters et al 30 conducted a systematic literature review, shown in Table 1.…”

Section: Background and Related Workmentioning

confidence: 99%

Goals and challenges in hybrid software development approaches

Prenner

Unger‐Windeler

Schneider

2021

J Software Evolu Process

View full text Add to dashboard Cite

The number of companies that use agile methods increases steadily. However, these companies often do not implement a pure agile approach but combine agile and plan‐based methods to so‐called hybrid development approaches. However, the development of these approaches is rather difficult for the companies, since agile and plan‐based approaches often follow opposite concepts. To benefit from agile and plan‐based approaches at the same time, the companies have to identify and address the conflicts between agile and plan‐based methods. The conflicts depend on the goals that are pursued with the implementation of agile and plan‐based methods. However, there is no overview of the exact goals that are pursued in hybrid approaches and which challenges and conflicts arise with them. Therefore, we conducted a systematic mapping study to gather and analyze the goals and challenges in hybrid development approaches. The mapping study is focused on literature that presents the actual needs and goals of companies and projects. Based on our results, we present the influence factors that cause conflicts in hybrid approaches and discuss how these conflicts can be addressed.

show abstract

CDTC: Automatically establishing the trace links between class diagrams in design phase and source code

Chen,

Zhang,

Lian

2023

Softw Pract Exp

View full text Add to dashboard Cite

ContextThe UML class diagram is commonly used to model functional structures and software code structures in both the preliminary and detailed design stages. And the abstraction level of UML class diagrams is usually higher than that of source code. Usually, there is a lack of trace links between these class diagrams and the source code, which may cause difficulties in understanding the source code, and affect the software evolution and maintenance.ObjectiveThe main goal of this article is to establish the trace links between highly abstracted UML class diagrams in the design phase and source code, and eventually help practitioners better understand source code.MethodWe propose an approach for the automated trace link establishment between UML class diagrams in the design phase and source code. To address the problem of abstraction level gap between them, we extend the UML class diagram by mining the synonymous phrases of class names and deducing the latent missing relationships between classes from multiple design documents. Then we build the trace links with a two‐phase approach including initial construction with fuzzy matching and further optimization by class relationship inference.ResultsExperiments on five open‐source projects show that the recalls of our approach are over 94%, and the F2‐scores are over 88%, with the gains of 30% to 60% than the four baselines.ConclusionOur work can be a reference for establishing the initial trace links between highly‐abstracted UML class diagrams and source code. Towards the higher abstraction of design diagrams, we extend UML class diagrams with the statistical analysis on multiple design documents. To guarantee the quality of trace links, we design a two‐phase approach by obtaining the “full but not good enough” trace links and filtering the “probably wrong” links. Experiments show that the main techniques of our approach behave as important role for tracing between high‐level class diagrams and source code.

show abstract

Interface Problems of Agile in a Non-agile Environment

Cited by 12 publications

References 8 publications

Dependencies of Agile Teams – An Analysis of the Scaled Agile Framework

Dependencies of Agile Teams – An Analysis of the Scaled Agile Framework

Goals and challenges in hybrid software development approaches

CDTC: Automatically establishing the trace links between class diagrams in design phase and source code

Contact Info

Product

Resources

About