Agile methods are increasingly being used in automotive development. This research delves into the current state of agile transformation in the automotive industry regarding benefits, challenges, organizational adaptations, and successful measures to establish the agile approach. The results of an online survey reveal that benefits are already evident after 6 months and that challenges are mainly organizational in nature and organizational structures need to be adapted. Main drivers of success are pilot projects on a small scale and top management support as well as training managers.

Empirical studies show that adaptations of existing agile methods are necessary for developing physical products creating obstacles and challenges. This paper aggregates the gathered findings from several cross-sectional industry surveys and establishes a relationship between the extent of utilization of individual agile elements based on Scrum and the need to adapt these elements in applying agile procedural models. The emphasis of examination resides in the purpose perspective of agile elements with the aim of facilitating context-specific adaptations more effectively.

Unlocking additive manufacturing's (AM) potential requires designer expertise. Design for additive manufacturing (DfAM) addresses this need but faces barriers, such as uncertainty in scope of integration, design support selection, result validation or time investment for incorporating design support. This paper proposes a framework aligning SCRUM (agile framework) to aid designers in overcoming those barriers. The goal is to pave the way for a better exchange between academia and industry and fostering iterative development of DfAM support tailored to designer needs.

One of the obstacles to the ability of research to make an impact on industry resides on the research process itself. Today, there is a need to accelerate the means for research to support industrial transformation. At the same time, there is the need to maintain scientific rigorousness, which often requires time. To solve this trade-off, this paper evaluates existing research approaches through the lenses of agile development. The analysis is based on a simulation of research process architectures, and on observations made over several research projects with industry. The results of this analysis highlight five light-but-sufficient rules of research project behavior to keep momentum, motivation and trust when doing research with industry. The paper demonstrates the use of these five rules in a “research sprint” conducted iwith two automotive OEMs.

Business process management (BPM) has been the main driver behind company optimization and operational efficiency. However, the digitization era we live in necessitates that organizations be agile and adaptable. Delivering unprecedented rates of automation-fueled agility is necessary to be a part of this digital revolution. On the other hand, BPM automation cannot be done only by concentrating on procedure space and traditional planning methodologies. With the introduction of BPM, where the deployment of BPM with cloud computing has undergone enormous development lately, cloud computing has been considered a particularly active topic of study. Cloud computing points to the provision of dependable computing environments based on improved infrastructure availability and service quality without imposing a significant cost load. This research aims to discover the relationship between technical factors, financial factors, environmental factors, security of the cloud-based information systems, and the agile development of industrial BPM (IBPM). The present study aims to fill this gap and show how partial least squares structural equation modeling (SEM) can be employed in this field. Importance–performance map analysis (IPMA) evaluated the importance and performance of factors in the SEM. IPMA enables the identification of factors with relatively low performance but relatively high importance in shaping dependent variables. The empirical findings showed that four key factors (technical, financial, environmental, and security) positively influence the agile development of IBPM.

This paper adapts the agile scrum sprint, typically used in software development, to a prototyping sprint for mechatronic product design. The Design by Prototyping framework describes how the prototyping sprint can be used to manage the prototyping process in design projects through an agile-stage-gate hybrid model. A comparison of 18 student projects using either prototyping sprints or a traditional iterative prototyping approach shows that prototyping sprints helped students make more deliberate, strategic decisions about their use of prototypes.

As the complexity of products and their development processes increases, a trend emerged where companies try to manage the complexity through implementing agile practices on all or on some levels of the development process. It is not yet clear if an agile approach is the solution or under which circumstances it can be most effective in the development of physical products. This paper aims to compile the information from existing empirical and meta-studies to give an overview of the strengths and weaknesses of conventional, agile and hybrid paradigms.

Agile has its roots in software, improving the pace and quality of development projects. The application of Agile to hardware is less mature, and anecdotal evidence suggests there are specific challenges in this space. Based upon qualitative interviews with organizations working simultaneously across hardware and software applications, this paper presents three key challenges we identified. We also document several useful adjustments to Agile practice which provide a toolset that teams can use to more successfully apply Agile to hardware projects.

Agile approaches are increasingly being used in appropriate use cases for the development of mechatronic systems.In the process of implementing agile elements in the development processes, the question of the success of the transformation often arises. In order to support the agile transition in measuring process improvement, a framework was developed that evaluates the success of the implementation process by means of interviews at 4 maturity levels in the transformation. The method was evaluated in 3 use cases. On this basis, continuous adaptations can be made to the implementation process.

The use of agile methods can also be advantageous in the development of physical products, as pilot projects have shown so far. However, the transfer of agile methods to the entire organisation is difficult, due to the different, prevailing circumstances of the various development activities. We have therefore defined a new approach subdividing product development into agile technology-driven and traditional product-oriented development. This model considers the methodological characteristics and thus enables the combination of the benefits of both agile and traditional development methods..

A case study during pandemic revealed the major drawbacks of the traditional product development process for MedTech industry. Disruption of conventional manufacturing, urgent need for accelerated design and production, faster regulatory approval have challenged the industry. In this paper the conventional medical product development process is explored based on the intramuscular injector case study. The study revealed core areas for improvement of the medical devices development process. The paper proposes the Lean-Agile methodology with the incorporated elements of Concurrent Engineering.

Neglecting challenges of distributed collaboration can lead to significant efficiency and effectiveness losses in agile, distributed development teams. The EDiT method provides support for improving distributed collaboration of development teams. To ensure acceptance, applicability, and contribution to success in industrial development practice, it is necessary to validate the EDiT method. The goal of this contribution is the development of a process model for early and incremental validation of the EDiT method in the field finally leading to a validation of the EDiT method itself.

As the benefits and potentials of agile approaches become increasingly clearer, also hardware product development seeks to apply those methods and procedures. However, mechatronic hardware products are often subject to stricter safety regulations so that a consequent risk management is essential. This paper presents a risk management method suitable for agile product development projects. The method together with an adapted agile procedure were applied and evaluated in a successful industrial case study. This lead to the extended application of agile approaches in other parts of the company.

We study a DevOps software development process for a Product-Service System (PSS) using a design structure matrix (DSM) representation. We find unique features such as nested, planned iterations at differing rates which are not evident in conventional engineering development projects. We describe the impact of integrating ongoing operations into a development process and identify some of the enablers that lead to adoption of a DevOps process. We conclude by discussing the implications of our findings and raise questions for further research.