Time filter

Source Type

Dortmund, Germany

Grapenthin S.,University of Duisburg - Essen | Poggel S.,adesso AG | Book M.,University of Iceland | Gruhn V.,University of Duisburg - Essen
Information and Software Technology

Context: The planning, estimation and controlling mechanisms of agile process models rely significantly on a fixed set of tasks being established for each sprint. These tasks are created as refinements of product backlog items at the beginning of each sprint. However, a project team's understanding of the backlog items' business implications and dependencies may often not be deep enough to identify all necessary tasks this early, so in addition to the tasks defined in the beginning of the sprint, more necessary tasks might be discovered as the sprint progresses, making any attempt at progress estimation or risk management difficult. Objective: We strive to enable software teams to achieve a deeper understanding of product backlog items, which should help them to identify a sprint's tasks more reliably and comprehensively, and avoid discovering the need for extra tasks during sprint execution. Method: We introduced a project team in a medium-sized software development company to the Interaction Room method, which encourages interdisciplinary communication about key system design aspects among all stakeholders. We observed the team's conduct in the sprint planning meetings, and tracked early- vs. late-identified tasks across several sprints. Results: Before the introduction of our method, the team used to discover on average 26% of a sprint's tasks not at the beginning of the sprint, but later during the course of the sprint. Using the Interaction Room in two separate projects, this ratio dropped to an average of 5% late-discovered tasks. Conclusion: Our observations from these projects suggest that increased communication among all stakeholders of a project leads to a more reliable identification of the tasks to be performed in a sprint, and that an Interaction Room can provide appropriate guidance to conduct this team communication in a focused and pragmatic way. © 2015 Elsevier B.V. Source

Lauenroth K.,adesso AG | Kamsties E.,FH Dortmund
Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)

[Context and motivation] Requirements engineering (RE) has a history of nearly 40 years and has developed several methods, techniques, and tools to support RE activities in various project situations. [Question/problem] This paper argues that RE research and practice is people agnostic and therefore has a blind spot: it ignores the capabilities of the people involved in RE. [Principal ideas/results] This paper presents several arguments from the related work that show that people’s capabilities may have a significant impact on their performance of RE related activities. [Contribution] Based on the presented arguments, this paper formulates the hypothesis that people’s capabilities have a higher impact on RE performance than the project situation and the methods applied. Based on this hypothesis, this paper presents possible further research activities. © Springer International Publishing Switzerland 2016. Source

Grapenthin S.,University of Duisburg - Essen | Poggel S.,adesso AG | Book M.,University of Duisburg - Essen | Gruhn V.,University of Duisburg - Essen
Proceedings - 40th Euromicro Conference Series on Software Engineering and Advanced Applications, SEAA 2014

In a large industry project that followed an agile approach based on the Scrum method, we found that the team often struggled with breaking coarse product backlog items down into the detailed tasks that had to be completed in a sprint. The team's understanding of the backlog items' business and technical implications and dependencies seemed not deep enough to identify all necessary tasks, so in addition to the tasks defined in the sprint planning meeting prescribed by Scrum, an average of 26% of additional tasks was identified later over the course of each sprint, making any attempt at progress estimation or risk management very difficult. To counter this effect and support the team's understanding of backlog items right from the beginning of each sprint, we introduced a pragmatic method to analyze backlog items more comprehensively and thus support a more complete and reliable task breakdown. We consequently found that the effectiveness and precision of task breakdowns has improved significantly in the project. © 2014 IEEE. Source

Heiden K.,adesso AG | Sinha M.,FH Dortmund | Bockmann B.,FH Dortmund
Studies in Health Technology and Informatics

An interdisciplinary and intersectoral coordinated therapy management along Clinical Practice Guidelines can ensure that all patients receive adequate diagnostic, treatment, and supportive services that lead most likely to optimal outcomes. Within the research project 'Virtual Oncological Networks', guideline-compliant pathways are defined and enacted within a Health Care Management Platform to support treatment planning and ongoing care of oncological diseases. © 2015 IMIA and IOS Press. Source

Heuer A.,University of Duisburg - Essen | Stricker V.,University of Duisburg - Essen | Budnik C.J.,Siemens AG | Lauenroth K.,adesso AG | Pohl K.,University of Duisburg - Essen
Science of Computer Programming

Control flow models, such as UML activity diagrams or Petri nets, are widely accepted modeling languages used to support quality assurance activities in single system engineering as well as software product line (SPL) engineering. Quality assurance in product line engineering is a challenging task since a defect in a domain artifact may affect several products of the product line. Thus, proper quality assurance approaches need to pay special attention to the product line variability. Automation is essential to support quality assurance approaches. A prerequisite for automation is a profound formalization of the underlying control flow models and, in the context of SPLs, of the variability therein. In this paper, we propose a formal syntax and semantics for defining variability in Petri nets. We use these extended Petri nets as a foundation to formally define variability in UML activity diagrams; UML activity diagrams serve as a basis for several testing techniques in product line engineering. We illustrate the contribution of such a formalization to assurance activities in product line engineering by describing its usage in three application examples. © 2012 Elsevier B.V. All rights reserved. Source

Discover hidden collaborations