Catching up with Method and Process Practice: An Industry-Informed Baseline for Researchers

Software development methods are usually not applied by the book.companies are under pressure to continuously deploy software products that meet market needs and stakeholders\u27 requests. To implement efficient and effective development processes, companies utilize multiple frameworks, methods and practices, and combine these into hybrid methods. A common combination contains a rich management framework to organize and steer projects complemented with a number of smaller practices providing the development teams with tools to complete their tasks. In this paper, based on 732 data points collected through an international survey, we study the software development process use in practice. Our results show that 76.8% of the companies implement hybrid methods.company size as well as the strategy in devising and evolving hybrid methods affect the suitability of the chosen process to reach company or project goals. Our findings show that companies that combine planned improvement programs with process evolution can increase their process\u27 suitability by up to 5%

Threat analysis in practice - Systematically deriving security requirements

With the growing number of incidents, the topic security gains more and more attention across all domains. Organizations realize their lack of state-of-the-art security practices, however, they struggle to improve their software lifecycle in terms of security. In this talk, we introduce the concept of security by design that implements security practices within the whole software lifecycle. Based on our practical experience from industry projects in the regulated industrial automation and unregulated classical IT domain, we explain how to perform a threat analysis and how to integrate it into the software lifecycle

Towards understanding the motivation of german organizations to apply certain software development methods

The motivation to apply and to integrate agile methods into established development processes can be seen all over the world. However, the motivation for applying agile methods is not well understood as different objectives are possible: some organizations address the constantly changing market and customer demands, others are doing “agile” as the presumed best practice. This publication aims towards a better understanding of the motivation to apply the chosen development methods in Germany. We present preliminary results based on the data collection of the “Hybrid dEveLopmENt Approaches in software systems development” (HELENA) study. Further, we exemplary look at the role of criticality for choosing agile or traditional development methods. The results indicate that the six development methods applied most in Germany are Scrum, Kanban, DevOps, Waterfall, V-Model, and Iterative Development. However, a particular method is not necessarily chosen due to a specific goal. This indicates that as future work other influencing factors, e.g., the criticality of the final product, need to be identified and taken into account for analysis