5 results
Filters
Settings
Now showing1 - 5 of 5
- Some of the metrics are blocked by yourconsent settings
Item type:Publication, Access status: without files , Managing systems of objectives in the agile development of mechatronic systems by ASD - Agile Systems Design(The Design Society, 2018-08); ; ; ; In the development of mechatronic systems and the associated product services and business models, the system of objectives contains all relevant objectives of various stakeholders, as well as requirements, boundary conditions and interdependencies between objectives. It serves as basis to define the solution area for the technical implementation of products and provides the foundation to validate resulting virtual and physical objects in the process of product development. In particular, the objectives of potential customers and users regarding the product change with an increasing dynamic, which leads to a lack of transparency. Accordingly, the product development process is characterized by constant uncertainties. To be able to counteract these uncertainties, companies are increasingly using agile approaches in order to identify potentially changed objectives at an early stage and to adapt the product along the product development process accordingly. An early validation of prototypes with low functionalities is also carried out under consistent customer integration to identify further objectives early on. As a result, the overall process gains in robustness. One approach that supports the developer throughout the entire development process of mechatronic systems is ASD - Agile Systems Design. It consists of principles, methods and processes of the PGE - Product Generation Engineering and contains a constellation of structuring and flexible elements that can be adapted to the respective development context. To support the process of product development, it is imperative to understand the behavior of systems of objectives in order to be able to derive resulting recommendations for the development. Based on a real development project that has been completed according to ASD, the paper introduces an approach to identify the development of the maturity of the systems of objectives. On this basis, a methodology is presented which supports the agile management of systems of objectives to meet the associated requirements. Thus, a handling of systems of objectives in connection with prototypes generated during the process is presented, which leads to a robust safeguarding of the development direction.Publicationtype: Conference Paper41 - Some of the metrics are blocked by yourconsent settings
Item type:Publication, Access status: without files , Development methods for 2030: An interpretation of scenarios in the application of methods(The Design Society, 2018-08); ; ; ; Using the scenario analysis, context scenarios of the application of methods were derived, for the strategic orientation of development method research. The scenarios of the application of methods are interpreted in this article. For this purpose, a multi-level concept was developed, in which in a first step an expert study with alumni and employees of the IPEK - Institute of Product Engineering of the Karlsruhe Institute of Technology (KIT) was carried out with 32 participants. The participants of the study were presented with concise short videos that illustrate the application of development methods in the respective scenario. The respondents' task was to evaluate the scenarios with regard to the actual situation, desired image and probability of occurrence as well as to identify the opportunities, risks and relevant research priorities of the scenarios. The results of the studies were then consolidated step-by-step in the expert team into a total of seven research clusters and linked with a network analysis. After a brief description of the scenarios of the application of methods, these are discussed in the results of this article with the aim of addressing specific short, medium and long-term research incentives.Publicationtype: Conference Paper67 - Some of the metrics are blocked by yourconsent settings
Item type:Publication, Access status: without files , Development methods for 2030: An interpretation of the scenarios of the method applicationUsing the scenario analysis, context scenarios of the application of methods were derived, for the strategic orientation of development method research. The scenarios of the application of methods are interpreted in this article. For this purpose, a multi-level concept was developed, in which in a first step an expert study with alumni and employees of the IPEK -Institute of Product Engineering of the Karlsruhe Institute of Technology (KIT) was carried out with 32 participants. The participants of the study were presented with concise short videos that illustrate the application of development methods in the respective scenario. The respondents' task was to evaluate the scenarios with regard to the actual situation, desired image and probability of occurrence as well as to identify the opportunities, risks and relevant research priorities of the scenarios. The results of the studies were then consolidated step-by-step in the expert team into a total of seven research clusters and linked with a network analysis. After a brief description of the scenarios of the application of methods, these are discussed in the results of this article with the aim of addressing specific short, medium and long-term research incentivesPublicationtype: Conference Paper14 - Some of the metrics are blocked by yourconsent settings
Item type:Publication, Access status: without files , Scaling agile practices on different time scopes for complex problem-solving(The Design Society, 2018-08); ; ; ; There can be no innovation without time and space for ideation and courage to endeavor new terrain. Approaching this terrain in a structured way whilst managing the risks linked to the uncertainty of the novel is a major advantage of agile process models such as Scrum. On the other hand, most companies in mechatronic product development organize their activities in Stage-Gate-Processes for good reasons. This paper thus aims at combining the benefits of traditional and agile process models. The core assumption is, that even in overall complex projects, only a certain amount of tasks really benefits from agile practices. In order to identify these project elements, a differentiated view on project complexity is necessary. This differentiation is then integrated into a tool for analyzing task entropy as a measure of unknowingness and thus potential for agile approaches. These agile approaches are considered to be timebound episodes of concentrated problem solving with restricted ressources. Thus, theories about human problem solving and multitasking serve as a fundament for the conceptualization of short-term agile workshops. By restricting the duration of these workshops to two to five days, the barrier of practicing agile methods in arbitrary process landscapes is significantly lowered. The question arising is how proven agile practices can be scaled to these small time scopes while retaining the valuable, structuring elements such as fixed sprints and regular meetings. On the fundament of ASD - Agile Systems Design, this paper presents guidelines for implementation of agile workshops on smaller time scopes based on three pillars: 1) using a structured agile process, 2) using methods and tools in an agile way and 3) providing an agile moderator. Subsequently, an exemplary implementation of the concept is shown. This paper thus contributes to actually creating innovation by describing a systematic way to generate results whilst containing risks under conditions of limited ressources.Publicationtype: Conference Paper32 - Some of the metrics are blocked by yourconsent settings
Item type:Publication, Access status: without files , Influencing factors and methods for knowledge transfer situations in Product Generation Engineering based on the SECI model(2018-08); ; ; ; Products are developed in teams and based on knowledge gained in previous development projects. This makes knowledge transfer a key factor for the success of product development. In addition is the development time a crucial factor. Increasing the speed of knowledge transfer is hence of great importance for product development. The SECI model describes knowledge transfer with four types of knowledge conversion and is used as a basis for a project which aims at increasing the speed of knowledge transfer in product development. This contribution describes the design and results of a workshop with experts as a descriptive study. The workshop was used to collect influencing factors for knowledge transfer as well as important transfer situations and estimate their relevance to align further investigations. Furthermore a generic framework is presented as a prescriptive study. The framework shows how transfer situations and conversion methods can be characterized and how measures for increasing the speed of knowledge transfer can be derived.Publicationtype: Conference Paper17